Example: bachelor of science

TitlePage CyberSource Payer Authentication

CyberSource Corporation HQ | Box 8999 | San Francisco, CA 94128-8999 | Phone: 800-530-9095 Title PageCyberSource Payer AuthenticationUsing the Simple Order APIJuly 20182 CyberSource Contact InformationFor general information about our company, products, and services, go to sales questions about any CyberSource Service, email or call 650-432-7350 or 888-330-2300 (toll free in the United States).For support information about any CyberSource Service, visit the Support Center at 2018 CyberSource Corporation. All rights reserved.

Payer Authentication Using the Simple Order API |July 2018 5 Contents Appendix C Request and Reply Examples 142 Standard Integration Examples 142 Check Enrollment Request Example 142

Tags:

  Standards, Authentication, Payer, Cybersource, Cybersource payer authentication

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Transcription of TitlePage CyberSource Payer Authentication

1 CyberSource Corporation HQ | Box 8999 | San Francisco, CA 94128-8999 | Phone: 800-530-9095 Title PageCyberSource Payer AuthenticationUsing the Simple Order APIJuly 20182 CyberSource Contact InformationFor general information about our company, products, and services, go to sales questions about any CyberSource Service, email or call 650-432-7350 or 888-330-2300 (toll free in the United States).For support information about any CyberSource Service, visit the Support Center at 2018 CyberSource Corporation. All rights reserved.

2 CyberSource Corporation (" CyberSource ") furnishes this document and the software described in this document under the applicable agreement between the reader of this document ("You") and CyberSource ("Agreement"). You may use this document and/or software only in accordance with the terms of the Agreement. Except as expressly set forth in the Agreement, the information contained in this document is subject to change without notice and therefore should not be interpreted in any way as a guarantee or warranty by CyberSource .

3 CyberSource assumes no responsibility or liability for any errors that may appear in this document. The copyrighted software that accompanies this document is licensed to You for use only in strict accordance with the Agreement. You should read the Agreement carefully before using the software. Except as permitted by the Agreement, You may not reproduce any part of this document, store this document in a retrieval system, or transmit this document, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written consent of Rights LegendsFor Government or defense agencies.

4 Use, duplication, or disclosure by the Government or defense agencies is subject to restrictions as set forth the Rights in Technical Data and Computer Software clause at DFARS and in similar clauses in the FAR and NASA FAR civilian agencies. Use, reproduction, or disclosure is subject to restrictions set forth in subparagraphs (a) through (d) of the Commercial Computer Software Restricted Rights clause at and the limitations set forth in CyberSource Corporation's standard commercial agreement for this software.

5 Unpublished rights reserved under the copyright laws of the United , , and The Power of Payment are registered trademarks of CyberSource Corporation. CyberSource , CyberSource Payment Manager, CyberSource Risk Manager, CyberSource Decision Manager, and CyberSource Connect are trademarks and/or service marks of CyberSource Corporation. All other brands and product names are trademarks or registered trademarks of their respective Authentication Using the Simple Order API|July 20183 CONTENTSC ontentsRecent Revisions to This Document7 About This Guide9 Audience and Purpose9 Scope9 Conventions10 Note, Important, and Warning Statements10 Text and Command Conventions10 Related Documents11 Customer Support11 Chapter 1 Introducing Payer Authentication12 Overview of Chargeback Protection123D Secure Authentication Process (Standard)

6 13 Prerequisites for Implementing Payer Authentication14 Required Merchant Information14 Chapter 2 Integrating Payer Authentication into Your Business15 Process Overview15 Implementing Payer Authentication16 Before You Begin16 Credentials/API Keys16 Integration16 Create the JWT16 Add the JavaScript17 BIN Detection17 Implementing Standard Payer Authentication17 Starting Authentication17 Requesting the Check Enrollment Service (Standard)19 Payer Authentication Using the Simple Order API|July 20184 ContentsImplementing Hybrid Payer Authentication21 Requesting the Check Enrollment Service (Hybrid)

7 21 Authenticating Enrolled Cards22 Requesting the Validation Service23 Implementing Payer Authentication with an SDK25 Chapter 3 Testing Payer Authentication Services26 Testing Process26 Enrollment Check26 Authentication Validation29 Expected Results30 Test Cases32 Verified by Visa32 Mastercard SecureCode41 Maestro SecureCode50 American Express SafeKey55 JCB J/Secure61 Diners Club ProtectBuy67 Discover ProtectBuy73 Test Cases for 3D Secure by Visa 79 Mastercard SecureCode87 American Express SafeKey95 Discover ProtectBuy103 Appendix AAPI Fields111 Formatting Restrictions111 Data Type Definitions111 Numbered Elements112 Request Fields113 Reply Fields129 Appendix BReason Codes141 Payer Authentication Using the Simple Order API|July 20185 ContentsAppendix CRequest and Reply Examples142 Standard Integration Examples142 Check Enrollment Request Example142 Check Enrollment Reply Examples 143 Hybrid Integration Examples144 Check Enrollment Request Example144 Check Enrollment Reply Example145 Validate Authentication Request

8 Example146 Validate Authentication Reply Example147 Appendix DWeb Site Modification Reference148 Web Site Modification Checklist1483D Secure Services Logos149 Informational Message Examples150 Appendix EPayer Authentication Transaction Details in the Business Center151 Searching for Payer Authentication Details151 Enrolled Card151 Enrollment Check151 Authentication Validation157 Card Not Enrolled158 Payer Authentication Details158 Transaction Details160 Payer Authentication Search161 Storing Payer Authentication Data162 Payer Authentication Using the Simple Order API|July 20186 ContentsAppendix FPayer Authentication Reports163 Payer Authentication Summary Report163 Downloading the Report164 Matching the Report to the Transaction Search Results165 Interpreting the Report166 Comparing Payer Authentication and Payment Reports167 Payer Authentication Detail Report168 Report169<Result>169<PayerAuthDetail>169<ProofXML>171<VEReq>172<VERes>173<PAReq>174<PARes>175<AuthInfo>177 Examples178 Failed Enrollment Check178 Successful

9 Authentication179 Appendix GRules-Based Payer Authentication180 Available Rules180 API Replies181 Bypassed Authentication Transactions181 Risk-Based Bank Transactions182 Glossary183 Index190 Payer Authentication Using the Simple Order API|July 20187 REVISIONSR ecent Revisions to This DocumentReleaseChangesJuly 2018 Removed obsolete businessRules_ignoreValidateResult request field and references. June 2018 Updated required API fields for 3D Secure See Appendix A, "API Fields," on page 2018 Updated the ECI from 1 to 0 in Figure 4, Authentication Path for Mastercard and Maestro, for instances where VERes Enrolled or PAResStatus equals U or N.

10 See "Expected Results," page 30. Updated the e-commerce indicator in Table 9, "Possible Values for Mastercard and Maestro SecureCode Reply Fields," for Failure result from spa to internet. See "Verified by Visa," page 32. Updated ucafCollectionIndicator in Table 9, "Possible Values for Mastercard and Maestro SecureCode Reply Fields," for Authentication not completed result from 1 to 0. Added result for recorded attempt to authenticate to Table 9, "Possible Values for Mastercard and Maestro SecureCode Reply Fields." Updated the e-commerce indicator for Test Case 19, Mastercard SecureCode Card Enrolled: Incomplete Authentication , from spa to internet.


Related search queries