Skip to main content

Authentication

Transaction Management​

To provide integrators with maximum flexibility when using the axept® Checkout v3 solution several transaction functions can be requested after the transaction has been completed. These functions do not rely on the consumer being present as all consumer interaction has been completed at this point.

Other than the Authentication Request all functions require an “id” to be present as a minimum.

Authentication​

Authentication with the Transaction Management API is the same as covered in Authentication of this document but with the scope set to webapi.

MethodPOST
Request Body Formatform-data
URL

https://test-oauth.dnapayments.com/oauth2/token

Example Request and Response​

Example Authentication Request
Scope=webapi
client_id=Test Merchant
client_secret=PoF84JqIG8Smv5VpES9bcU31kmfSqLk8Jdo7
grant_type=client_credentials
Example Authentication Response
{
    "access_token": "Ez.FCzTxL98J9_weYJBXR5$Ly*bUZg=ScLgh2A4YC5FXeH8RVV2n7EQvA4UXnv7O",
    "expires_in": "604800",
    "refresh_token": "vNL5bsOusdx.Un-gnlPp9DdseKZW1vI*9mLld=*0P4lYp-IhQZsDFJjKJBo7VXCB",
    "scope": "webapi",
    "token_type": "Bearer"
}