Key Points
- Once a card token is generated, it can be used to execute Purchase or Authorization transactions.
- The card token replaces the need for actual card details, ensuring that sensitive data is never exposed during the transaction.
- This method is commonly used for: One-click payments, Recurring transactions (e.g., subscriptions), Stored customer payment details.
Flow diagram
Api Parameters
Card Token
Use thestored_payment_method_id (generated during token creation) in the payload to complete the transaction.
stored_payment_method_id is the token generated from the card tokenization process and is used to securely complete subsequent transactions.Authorizations
API Key for Authorization. Format: 'Basic YOUR_API_KEY_HERE'
API Key specific to x-api-key.
Body
The request payload to process a payment transaction.
The amount of the transaction.
"1000"
The abbreviation of the processing currency (e.g., JPY).
3"JPY"
A JSON object containing the payment method.
The merchant ID (DASMID).
128"< Merchant ID >"
A JSON object containing the billing address of the cardholder.
The merchant transaction reference ID.
45"qwe"
The IP address of the cardholder.
45"127.0.0.1"
A JSON object containing the return URLs. (This field is mandatory for 3DS transactions.)
A JSON object containing the shipping address of the cardholder (optional).
The country time zone of the transaction.
128"Asia/Kuala_Lumpur"
Response
Payment processed successfully
True on successful transaction, false on failure.
true
The status code of the transaction.
201
True if live transaction, false if test transaction.
false
The transaction type (e.g., CAPTURE).
"CAPTURE"
A JSON object containing the response from the gateway.
A JSON object containing the details of the merchant.
A JSON object containing the payment details.
A JSON object containing details of the transaction.
A JSON object containing details of risk.