Payment Credentials API
This section contains the information you need to retrieve the full payment credentials collected by the
Unified Checkout
tool using the payment credentials API. The payment information is returned in a redundantly signed and encrypted payment object. It uses the JSON Web Tokens (JWTs) as the data standard for communicating this sensitive data.IMPORTANT
Payment information returned by the
payment-credentials
endpoint will contain Personal Identifiable Information (PII). Retrieving this sensitive information requires your system to comply with PCI security standards. For more information on PCI security standards, see: https://www.pcisecuritystandards.org/The response is returned using a JWE data object that is encrypted with your public key created during the
Unified Checkout
tool's integration. For more information, see Upload Your Encryption Key.To decrypt the JWE response, use your private key created during the
Unified Checkout
tool's integration. The decrypted content is a JWS data object containing a JSON payload. This payload can be validated with the Unified Checkout
public signature key.IMPORTANT
When integrating with
Cybersource
APIs, Cybersource
recommends that you dynamically
parse the response for the fields that you are looking for. Additional fields may be added
in the future. You must ensure that your integration can handle new fields that are
returned in the response. While the underlying data structures will not change, you must
also ensure that your integration can handle changes to the order in which the data is
returned.
Cybersource
uses semantic versioning practices, which enables
you to retain backwards compatibility as new fields are introduced in minor version
updates.Returned Credentials
A payment account number (PAN) or network token is returned on your request depending on
your payment method and
When you retrieve PAN information from the Payment Credentials API, the response
includes the PAN, card expiration date, and the card verification value (CVV). When you
retrieve network token information, the response includes the network token and network
token cryptogram.
Click to Pay
account status:
Click to Pay Account Status | American Express | Mastercard | Visa |
---|---|---|---|
New card not saved in Click to Pay | PAN | PAN | PAN |
New card saved in Click to Pay | PAN | Network Token | Network Token |
Existing card stored in Click to Pay | PAN | Network Token | Network Token |
IMPORTANT
Visa and Mastercard always attempt to provision a network token.
When a network token is not provisioned, the default payment method is the PAN. When there
is a PAN transaction, the PAN is not stored in the consumers wallet and it is treated as a
single transaction.
Click to Pay
token requestor ID (TRID). When tokenization is successful, Visa
attempts to complete authentication during the Click to Pay
experience.
For information on authentication, see Customer Authentication.You must meet these requirements for tokenization to be successfully configured for your
merchant ID (MID):
- Click to Payis enabled as a digital payment in theBusiness Center.
- The transacting MID is configured for tokenization withClick to Pay. Contact your Implementation Consultant or Technical Account Manager to configure tokenization withClick to Pay.
- TheallowedPaymentTypesfield value is set toCLICKTOPAYin the capture context. For information on the capture context, see Capture Context API.
Endpoint
Production:
GET
https://api.cybersource.com
/flex/v2/payment-credentials/{ReferenceID}
Test:
GET
https://apitest.cybersource.com
/flex/v2/payment-credentials/{ReferenceID}
The
is the reference ID returned in the
{ReferenceID}
id
field when you created the
payment credentials.