A POST request sent to generate a token to view a card's PAN.
WARNING: The card's PAN is a PCI sensitive field that should only be viewed on the client
device and never logged or stored in any form.
The response includes a callback URL and a token ID. The token is good for one use only.
Using the response object, the user should perform a POST request to the callback URL with a body of
{
tokenId: tokenId
}
to view the card's PAN.
Once the token is used in the POST request to the callback URL, a response similar to the following will be returned:
{
"creationTime": 1547573554173,
"modifiedTime": 1547573554173,
"id": "8202C315D8960020534E4D9E0C5509BE-1000057006",
"cardNumber": "2554663244155607944",
"panFirst6": "123409",
"panLast4": "8065",
"type": "phy",
"state": "created",
"sequenceNumber": 1,
"cardProfileName": "e6-personalized-card",
"shippingNumber": "shipping-number-22",
"pinFailCount": 0,
"reissue": true,
"expiry": "202706",
"customerNumber": "10000170010738",
"embossedName": "SIX/JOE",
"pan": "1234098745678065",
"cvv2": "290"
}
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.
The user has sent too many requests in a given amount of time ("rate limiting").
The server has encountered a situation it does not know how to handle.