Cancel your payment token.
Cancel Payment Token
{
"payment_token_id": "pt-1402feb0-bb79-47ae-9d1e-e69394d3949c",
"business_id": "5f27a14a9bf05c73dd040bc8",
"reference_id": "90392f42-d98a-49ef-a7f3-abcezas123",
"customer_id": "cust-b98d6f63-d240-44ec-9bd5-aa42954c4f48",
"country": "ID",
"currency": "IDR",
"channel_code": "OVO",
"channel_properties": {
"failure_return_url": "https://xendit.co/failure",
"success_return_url": "https://xendit.co/success"
},
"actions": [
{
"type": "REDIRECT_CUSTOMER",
"descriptor": "WEB_URL",
"value": "https://xendit.co/"
}
],
"status": "CANCELED",
"token_details": {
"account_name": "John Doe",
"account_balance": "1000001",
"account_point_balance": "50000"
},
"metadata": {
"metametadata": "metametametadata"
},
"created": "2029-12-31T23:59:59Z",
"updated": "2029-12-31T23:59:59Z"
}Payment Token object
Xendit unique Payment Token ID generated as reference for reusable payment details of the end user.
Channel code used to select the payment method provider. Use routing payment channels mapping for full list of channel codes.
ISO 3166-1 alpha-2 two-letter country code for the country of transaction.
Xendit-generated identifier for the business that owns the transaction
Xendit unique Capture ID generated as reference for the end user
A Reference ID from merchants to identify their request.
ISO 4217 three-letter currency code for the payment.
Data required to initiate transaction with payment method provider. Use routing payment channels mapping for full list of data required.
Actions object contains possible next steps merchants can take to proceed with payment collection from end user
The type of action that merchant system will need to handle to complete payment.
The type of action that merchant system will need to handle to complete payment.
The specific value that will be used by merchant to complete the action
Status of the payment token.
Account information provided by the payment method provider. Fields returned are dependent on what is made available by the provider.
Specific to cards transaction only. Details about the card authorization processing.
Authorization approval code from the scheme. 6 alphanumeric characters.
Whether CVN input matches with the issuer's data.
Whether the end user's address input matches with the issuer's data.
Receipt reference number communicated to the end user by their card issuer for this specific payment. This a commonly used reference number for the end users to raise tickets.
The response code returned by the scheme (Visa, Mastercard, JCB, China Unionpay or Amex).
Description of the response code.
Transaction ID received from the card scheme. Only available for merchants on switcher model.
Acquirer's record of the MID that was used to process this transaction. Only available for merchants on switcher model.
Acquirer's transaction record of the payment on their settlement statement. Only available for merchants on switcher model.
Specific to cards transaction only. Details about the card authentication.
Indicates the flow that was used for the 3DS authentication.
Details about the card authentication response from the 3DS server.
Payment system-specific value provided by the ACS or DS to indicate the results of the attempt to authenticate the Cardholder.
The 3DS protocol version which has been used to perform 3DS.
The result value from the 3DS transaction received from the ACS. This value is no longer present on responses after 45 days have passed after the authentication. Note that Mastercard and Visa use a different underlying format.
Universally unique transaction identifier assigned by the DS to identify a single transaction.
Name of the owner of the account bound to the token.
Balance of the account bound to the token.
Point balance of the account bound to the token.
Account number bound to the token.
Failure codes for payment tokens.
Key-value entries for your custom data. You can specify up to 50 keys, with key names up to 40 characters and values up to 500 characters. This is for your convenience. Xendit will not use this data for any processing.
A custom description for the Payment Request.
ISO 8601 date-time format.
ISO 8601 date-time format.
Bad request
Payment request is already inactive.
Fields or values in the payment request does not comply with our API specification. Check the specific error message for debugging.
Requested feature is unavailable during this timing.
Feature is not allowed for the payment request because of its current status. Check the specific error message for debugging.
Not found
ID specified in request cannot be found.
Internal server error
An unexpected error occured, our team has been notified and will troubleshoot the issue
Service unavailable
The channel requested is currently experiencing unexpected issues. The provider will be notified to resolve this issue.