Example: Transient Token Format

Transient Token Payload
{ "iss": "Flex/00", "exp": 1706910242, "type": "gda-0.9.0", "iat": 1706909347, "jti": "1D1I2O2CSTMW3UIXOKEQFI4OQX1L7CMSKDE3LJ8B5DVZ6WBJGKLQ65BD6222D426", "metadata": { "consumerPreference": { "saveCard": true }, "tokenizedCard": { "card": { "maskedValue": "XXXXXXXXXXXX9876", "prefix": "123456", "expirationMonth": "MM", "expirationYear": "YYYY" } } }, "content": { "orderInformation": { "billTo" : { // Empty fields present within this node indicate which fields were captured by // the application without exposing you to personally identifiable information // directly. }, "amountDetails" : { // Empty fields present within this node indicate which fields were captured by // the application without exposing you to personally identifiable information // directly. }, "shipTo" : { // Empty fields present within this node indicate which fields were captured by // the application without exposing you to personally identifiable information // directly. } }, "paymentInformation": { "card": { "expirationYear": { "value": "2028" }, "number": { "maskedValue": "XXXXXXXXXXXX1111", "bin": "411111" }, "securityCode": {}, "expirationMonth": { "value": "06" }, "type": { "value": "001" } } } } }
PAN BIN in
metadata
Object
The
cardDetails
object, including the PAN BIN, is included in the transient token
metadata
when a
Click to Pay
network token is used as a payment method. This allows you to display information about the card on invoices and see the BIN details that are linked to the underlying card.
"metadata": { "cardDetails": { "suffix": "9876", "prefix": "123456", "expirationMonth": "MM", "expirationYear": "YYYY" } }
Authentication Status in
metadata
Object
The
authenticationStatus
object is included in the
metadata
and enables you to determine if the payload is fully authenticated. When
authenticationStatus
is set to
true
, the payload is fully authenticated. When
authenticationStatus
is set to
false
, the transaction is not authenticated.
If you are using
Unified Checkout
with the complete API and you include
consumerAuthentication
in the complete mandate request, then
Payer Authentication
is called automatically if it is available for the selected payment method and card network. In this case, there is no action required on your part.
"metadata": { "authenticationStatus": "true" } }