Click To Pay
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.
Identifier of the merchant provided by Thales at on-boarding.
The unique transaction identifier.
Created
The payment credentials data encrypted in a JWE structure (see security section in the documentation).
Once decrypted, the JWE plaintext contains the following JSON object:
| JSON field parameter name | description | MOC | Length |
|---|---|---|---|
| dpan | The token PAN value provided for network token. | C | Up to 19 |
| exp | The token expiry date in the format MMYY provided for network token. | C | 4 |
| cryptogram | The payment cryptogram to use with the token for a payment. Presence of the cryptogram depends on the transaction type and the scheme. | C | Up to 256 |
| fpan | The funding card PAN value. Only provided for PCI token. | C | Up to 19 |
| fpanExp | The funding card expiry date in the format MMYY. Only provided for PCI token. | C | 4 |
Example: {"dpan:"9580981500100002", "exp":"1222", "cryptogram": "45f8grzty7f4f5gs5s2c"}
Bad request - Not Retryable
Unauthorized - Not Retryable
Not Found - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.
Identifier of the merchant provided by Thales at on-boarding.
The unique transaction identifier.
Accepted
No content
Bad request - Not Retryable
Unauthorized - Not Retryable
Not Found - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
No content
The unique merchant identifier.
Technical identifier pre-defined at on-boarding that identifies the API
consumer.
Format shall be the string 'APIKEY' followed by a space and the
api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b
Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.
Legal name of the merchant.
^[A-Za-z0-9-_. ]+$Merchant website URL.
http://www.mymerchant.comPattern: ^[A-Za-z0-9-_.:/]+$Merchant country in ISO-3166-1 alpha-2 two-letter country code.
USAccepted
No content
Bad request - Not Retryable
Unauthorized - Not Retryable
Not Found - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
No content
Last updated
Was this helpful?