Using your app credentials, send a request to create a bearer access token that can be used to execute subsequent API actions. The actions that the token can execute are determined by the permissions the app has.
Format of the message body.
The version of the API to execute the request.
The id of the app that was used to create the token.
A unique random value used to create the secret. The integrator must ensure this is unique and different for every request to create an access token.
A unique string created using the nonce and app-key. This value is used to further authenticate the request. Created as follows - SHA512(NONCEAPP-KEY
This is an Oauth specific field that must be set to client_credentials. This indicates to the platform to give access to the apps own resources.
client_credentialsThe time in seconds that the access token will expire and can no longer be used.
Masks the account, merchant and app details that is returned in the response to a tokenisation request.
YES - A restricted access token will be created. Restricted access token is used when integrating with Drop-in UI or Hosted Fields to create a single-use payment token.NO - A restricted access token will not be created.The time interval set for when the token will expire.
WEEKDAY12_HOURS6_HOURS3_HOURS1_HOUR30_MINUTES10_MINUTES5_MINUTESAll of the permissions or activites that may be performed by the account.