WIXLIB

Title PageAuthorizations withPayment Network TokensUsing the Simple Order APISupplement to Credit Card ServicesUsing the Simple Order API

Cybersource Contact InformationFor general information about our company, products, and services, go to http://www.cybersource.com.For sales questions about any Cybersource service, email sales@cybersource.com or call 650-432-7350 or 888330-2300 (toll free in the United States).For support information about any Cybersource service, visit the Support Center: http://www.cybersource.com/supportCopyright 2021. Cybersource Corporation. All rights reserved. Cybersource Corporation ("Cybersource") furnishes thisdocument and the software described in this document under the applicable agreement between the reader ofthis document ("You") and Cybersource ("Agreement"). You may use this document and/or software only inaccordance with the terms of the Agreement. Except as expressly set forth in the Agreement, the informationcontained in this document is subject to change without notice and therefore should not be interpreted in any wayas a guarantee or warranty by Cybersource. Cybersource assumes no responsibility or liability for any errors thatmay appear in this document. The copyrighted software that accompanies this document is licensed to You foruse only in strict accordance with the Agreement. You should read the Agreement carefully before using thesoftware. Except as permitted by the Agreement, You may not reproduce any part of this document, store thisdocument 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 Cybersource.Restricted Rights LegendsFor Government or defense agencies: Use, duplication, or disclosure by the Government or defense agenciesis subject to restrictions as set forth the Rights in Technical Data and Computer Software clause at DFARS252.227-7013 and in similar clauses in the FAR and NASA FAR Supplement.For 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 52.227-19 and the limitations setforth in Cybersource Corporation's standard commercial agreement for this software. Unpublished rightsreserved under the copyright laws of the United States.TrademarksAuthorize.Net, eCheck.Net, and The Power of Payment are registered trademarks of Cybersource Corporation.Cybersource, Cybersource Payment Manager, Cybersource Risk Manager, Cybersource Decision Manager, andCybersource Connect are trademarks and/or service marks of Cybersource Corporation. Visa, Visa International,Cybersource, the Visa logo, and the Cybersource logo are the registered trademarks of Visa International in theUnited States and other countries. All other trademarks, service marks, registered marks, or registered servicemarks are the property of their respective owners.Revision: 21.022

CONTENTSContentsRecent Revisions to This DocumentAbout This Guide6Audience and PurposeConventions66Related DocumentsCustomer SupportChapter 177Authorizations with Payment Network TokensSupported Processors and Card TypesIn-App TransactionsChapter 2589Optional Features12Merchant-Initiated Transactions12Multiple Partial Captures 13Special Request Fields for Multiple Partial CapturesMultiple Partial Captures on Streamline 14Recurring Payments81415Relaxed Requirements for Address Data and Expiration DateSplit Shipments17Subsequent Authorizations 18Requesting a Subsequent AuthorizationAppendix A API Fields1819Formatting RestrictionsData Type DefinitionsNumbered ElementsRequest FieldsReply Fields171919202131Authorizations with Payment Network Tokens Using the Simple Order API 3

ContentsAppendix B Examples37Name-Value Pair ExamplesXML Examples3739Authorizations with Payment Network Tokens Using the Simple Order API 4

ReleaseChanges21.02Visa Platform Connect: updated "In-App Transactions," page 9, and the request fieldpaymentNetworkToken requestorID, page 26.21.01Added support for the processor HSBC. See Table 2, "Processors and Card Types," on page 8,Table 3, "Processors That Support Merchant-Initiated Transactions," on page 12, Table 4,"Processors That Support Multiple Partial Captures," on page 13, and Table 5, "ProcessorsThat Support Recurring Payments," on page 15.REVISIONSRecent Revisions to ThisDocumentUpdated the card type field. See card cardType, page 22.Changed the name of Cybersource through VisaNet to Visa Platform Connect.Moneris: added support for China UnionPay cards.20.05Added support for the processor Cielo 3.0. See Table 2, "Processors and Card Types," onpage 8.20.04Updated information about recurring payments. See "Recurring Payments," page 15.20.03Added the following request fields. See "Request Fields," page 21.20.02 subsequentAuth subsequentAuthFirst subsequentAuthOriginalAmount subsequentAuthReason subsequentAuthStoredCredential subsequentAuthTransactionIDUpdated support for the processor Moneris. See Table 2, "Processors and Card Types," onpage 8, Table 3, "Processors That Support Merchant-Initiated Transactions," on page 12, andTable 5, "Processors That Support Recurring Payments," on page 15.Authorizations with Payment Network Tokens Using the Simple Order API 5

ABOUT GUIDEAbout This GuideAudience and PurposeThis document is written for application developers who want to use payment networktokens in an order management system that already uses Cybersource credit cardservices. This document assumes that you are already familiar with the Cybersourcecredit card services as described in Credit Card Services Using the Simple Order API.Updating the Cybersource credit card services requires software development skills. Youmust write code that uses the API request and reply fields to integrate authorizations withpayment network tokens into your existing order management system.ConventionsThe following special statement is used in this document:An Important statement contains information essential to successfullycompleting a task or learning a concept.The following text conventions are used in this document:Table 1Text ConventionsConventionMeaningboldField and service names in text; for example:Include the ccAuthService run field.Screen text XML elements. Code examples. Values for API fields; for example:Set the ccAuthService run field to true.Authorizations with Payment Network Tokens Using the Simple Order API 6

About This GuideRelated Documents Apple Pay Using the Simple Order API (PDF HTML) Card-Present Processing Using the Simple Order API (PDF HTML) Credit Card Services Using the Simple Order API (PDF HTML) Getting Started with Cybersource Advanced for the Simple Order API (PDF HTML) Google Pay Using the Simple Order API (PDF HTML) Samsung Pay Using the Simple Order API (PDF HTML)Refer to the Support Center for complete Cybersource technical documentation:http://www.cybersource.com/support center/support documentationCustomer SupportFor support information about any Cybersource service, visit the Support tions with Payment Network Tokens Using the Simple Order API 7

CHAPTERAuthorizations with PaymentNetwork Tokens1This guide explains how to request an authorization with a token instead of a primaryaccount number (PAN).This document describes how to integrate the pass-through processing of tokens into yourorder management system. It does not describe the process of substituting a PAN with atoken, also known as token provisioning. For information about token provisioning, contactyour token service provider.For an incremental authorization, you do not need to include any payment networktokenization fields in the authorization request because Cybersource obtains the paymentnetwork tokenization information from the original authorization request.Supported Processors and Card TypesTable 2Processors and Card TypesProcessorCard TypesAmerican Express DirectAmerican ExpressBarclaysVisa, Mastercard, JCB, Maestro (International),Maestro (UK Domestic)Note If you support Maestro (UK Domestic), youmust also support Maestro (International), and youmust support Mastercard Identity Check for bothcard types.Chase Paymentech SolutionsVisa, Mastercard, American Express, Discover,Diners Club, JCB, Carte Blanche, Maestro(International)Cielo 3.0Visa, Mastercard, EloCredit Mutuel-CICVisa, Mastercard, Cartes BancairesElavon AmericasVisa, Mastercard, American Express, JCB, DinersClub, Discover, China UnionPayFDC CompassVisa, Mastercard, American Express, Discover,Diners Club, JCBAuthorizations with Payment Network Tokens Using the Simple Order API 8

Chapter 1Table 2Authorizations with Payment Network TokensProcessors and Card Types (Continued)ProcessorCard TypesFDC Nashville GlobalVisa, Mastercard, American Express, Discover,Diners Club, JCB, China UnionPayGPNVisa, Mastercard, American Express, Discover,Diners Club, JCBHSBCHSBC is the Cybersource name forHSBC U.K.Visa, Mastercard, Maestro (UK Domestic), Maestro(International), Visa Electron,JCN GatewayJCBMonerisVisa, Mastercard, American Express, ChinaUnionPayOmniPay DirectVisa, Mastercard, Discover, Diners Club, Maestro(UK Domestic), Maestro (International)SIXVisa, MastercardImportant SIX is supported only for card-presentprocessing.StreamlineVisa, MastercardTSYS Acquiring SolutionsVisa, Mastercard, American ExpressVisa Platform ConnectVisa, Mastercard, American Express, Discover,JCB, Diners ClubWorldpay VAPWorldpay VAP was previously calledLitle. Litle was purchased by Vantiv,which was then purchased by WorldpayVAP. If you have any questions about thissituation, contact your account managerat Worldpay VAP.Visa, MastercardIn-App TransactionsFor in-app transactions, include the following required fields in the authorization request: billTo city billTo country billTo email billTo firstName billTo lastName billTo postalCode—required only for transactions in the U.S. and Canada.Authorizations with Payment Network Tokens Using the Simple Order API 9

Chapter 1Authorizations with Payment Network Tokens billTo state—required only for transactions in the U.S. and Canada. billTo street1 card accountNumber—set to the token value that you received from the token serviceprovider. card cardType—Cybersource strongly recommends that you send the card type evenif it is optional for your processor. Omitting the card type can cause the transaction tobe processed with the wrong card type. card expirationMonth—set to the token expiration month that you received from thetoken service provider. card expirationYear—set to the token expiration year that you received from the tokenservice provider. ccAuthService cavv—for 3D Secure in-app transactions, set to the 3D Securecryptogram. Otherwise, set to the network token cryptogram. ccAuthService commerceIndicator ccAuthService networkTokenCryptogram ccAuthService run—set to true. merchantID merchantReferenceCode purchaseTotals currency purchaseTotals grandTotalAmount or item # unitPrice paymentNetworkToken transactionType paymentNetworkToken requestorID—required on Visa Platform Connect.Include 3D Secure data in the following fields: For Visa requests, include the ccAuthService cavv field set to the Visa Securecryptogram. For Mastercard requests, include: ucaf authenticationData—set to the Identity Check cryptogram. ucaf collectionIndicator—set to 2.For JCB requests, include the ccAuthService cavv field set to the J/Securecryptogram.See Appendix A, "API Fields," on page 19 for: Detailed descriptions of these required request fieldsAuthorizations with Payment Network Tokens Using the Simple Order API 10

Chapter 1 Optional request fields Reply fieldsAuthorizations with Payment Network TokensAfter a successful authorization request, the rest of the credit card processing proceeds asdescribed in Credit Card Services Using the Simple Order API (PDF HTML).Authorizations with Payment Network Tokens Using the Simple Order API 11