On This Page
Authorizations with Payment Network Tokens
This section shows you how to successfully process an authorization with payment network
tokens.
IMPORTANT
Due to mandates from the Reserve Bank of India, Indian merchants cannot
store personal account numbers (PAN). Use network tokens instead. For more information
on network tokens, see Network Tokenization in
the .
Token Management Service
Developer GuideMerchant Category Codes
When your business onboards with
Cybersource
, Cybersource
assigns your account a merchant category code (MCC) based on
your primary business type. Cybersource
sends this MCC to the card
networks with every transaction you process. If you process a transaction that is
unrelated to your usual goods or services, include the merchantInformation.categoryCode
field and set it to the relevant MCC. Cybersource
and FDC Nashville Global
do not validate the MCC you
send. Using an incorrect MCC can result in increased decline rates, interchange
downgrades, or fines. To verify the correct MCC, contact your Cybersource
account manager.Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/paymentsTest:
POST
https://apitest.cybersource.com
/pts/v2/paymentsRequired Fields for Authorizations with Payment Network Tokens
Use these required fields for processing an authorization with payment network tokens.
IMPORTANT
When relaxed requirements for address data and the expiration date are being used, not all fields
in this list are required. It is your responsibility to determine whether your
account is enabled to use this feature and which fields are required. For details
about relaxed requirements, see Relaxed Requirements for Address Data and Expiration Date in Payment Transactions.
- orderInformation.amountDetails.currency
- orderInformation.amountDetails.totalAmount
- orderInformation.billTo.address1
- orderInformation.billTo.email
- orderInformation.billTo.firstName
- orderInformation.billTo.lastName
- paymentinformation.tokenizedCard.cryptogram
- paymentinformation.tokenizedCard.expirationMonth
- paymentinformation.tokenizedCard.expirationYear
Related Information
Optional Fields for Authorizations with Payment Network Tokens
You can use these optional fields to include additional information when processing
an authorization with a payment network token.
- clientReferenceInformation.code
- consumerAuthenticationInformation.cavv
- For 3-D Secure in-app transactions for Visaand JCB, set this field to the 3-D Secure cryptogram. Otherwise, set to the network token cryptogram.
- consumerAuthenticationInformation.ucafAuthenticationData
- For Mastercard requests using 3-D Secure, set this field to the Identity Check cryptogram.
- consumerAuthenticationInformation.ucafCollectionIndicator
- For Mastercard requests using 3-D Secure, set the value to2.
- orderInformation.amountDetails.currency
- orderInformation.amountDetails.totalAmount
- orderInformation.billTo.address1
- orderInformation.billTo.country
- orderInformation.billTo.email
- orderInformation.billTo.firstName
- orderInformation.billTo.lastName
- orderInformation.billTo.locality
- orderInformation.billTo.postalCode
- Required only for transactions in the US and Canada.
- orderInformation.billTo.administrativeArea
- Required only for transactions in the US and Canada.
- processingInformation.commerceIndicator
- paymentInformation.tokenizedCard.cardType
- It is strongly recommended that you send the card type even if it is optional for your processor. Omitting the card type can cause the transaction to be processed with the wrong card type.
- paymentInformation.tokenizedCard.cryptogram
- paymentInformation.tokenizedCard.expirationMonth
- Set to the token expiration month that you received from the token service provider.
- paymentInformation.tokenizedCard.expirationYear
- Set to the token expiration year that you received from the token service provider.
- paymentInformation.tokenizedCard.number
- Set to the token value that you received from the token service provider.
- paymentInformation.tokenizedCard.requestorId
- paymentInformation.tokenizedCard.transactionType
Related Information
REST Example: Authorizations with Payment Network Tokens
Request
{ "orderInformation" : { "billTo": { "country": "US", "lastName": "Kim", "address1": "201 S. Division St.", "postalCode": "48104-2201", "locality": "Ann Arbor", "administrativeArea": "MI", "firstName": "Kyong-Jin", "email": "test@cybs.com" }, "amountDetails" : { "totalAmount" : "100", "currency" : "USD" } }, "paymentInformation" : { "tokenizedCard" : { "expirationYear" : "2031", "number" : "4111111111111111", "expirationMonth" : "12", "transactionType" : "1", "cryptogram" : "qE5juRwDzAUFBAkEHuWW9PiBkWv=" } } }
Response to a Successful Request
{ "_links": { "authReversal": { "method": "POST", "href": "/pts/v2/payments/6838294805206235603954/reversals" }, "self": { "method": "GET", "href": "/pts/v2/payments/6838294805206235603954" }, "capture": { "method": "POST", "href": "/pts/v2/payments/6838294805206235603954/captures" } }, "clientReferenceInformation": { "code": "1683829480593" }, "id": "6838294805206235603954", "orderInformation": { "amountDetails": { "authorizedAmount": "100.00", "currency": "USD" } }, "paymentAccountInformation": { "card": { "type": "001" } }, "paymentInformation": { "tokenizedCard": { "type": "001" }, "card": { "type": "001" } }, "pointOfSaleInformation": { "terminalId": "111111" }, "processorInformation": { "approvalCode": "888888", "networkTransactionId": "123456789619999", "transactionId": "123456789619999", "responseCode": "100", "avs": { "code": "1" } }, "reconciliationId": "60332034UHI9PRJ0", "status": "AUTHORIZED", "submitTimeUtc": "2023-05-11T18:24:40Z" }