JWT authentication
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 list of tokens to be associated with the JWT, only Mastercard and Visa tokens allowed, all the tokens must belong to the same merchant
["COFTG-MS-ce464906-cf39-4990-b4a8-c160e67c603a","COFTG-V-fe464806-sd39-1290-a4t8-f160e37c602b"]Scope used for the access token generation
Access token successfully generated
Access token generated for WEB SDK calls, JWT content:
- exp
- iss
- iat
- aud
- sub
- trId
- scope
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...Bad request - Not Retryable
Unauthorized - Not Retryable
Not Found - Not Retryable
Too Many Requests - Retryable
Internal Server Error - Not Retryable
Service Unavailable - Retryable
最終更新
役に立ちましたか?