Skip to main content
POST
cURL

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

Flow diagram image

Api Parameters

Card Token

Use the stored_payment_method_id (generated during token creation) in the payload to complete the transaction.
Request Example
The stored_payment_method_id is the token generated from the card tokenization process and is used to securely complete subsequent transactions.

Authorizations

Authorization
string
header
required

API Key for Authorization. Format: 'Basic YOUR_API_KEY_HERE'

x-api-key
string
header
required

API Key specific to x-api-key.

Body

application/json

The request payload to process a payment transaction.

amount
string
required

The amount of the transaction.

Example:

"1000"

currency
string
required

The abbreviation of the processing currency (e.g., JPY).

Maximum string length: 3
Example:

"JPY"

payment_method
object
required

A JSON object containing the payment method.

merchant_id
string
required

The merchant ID (DASMID).

Maximum string length: 128
Example:

"< Merchant ID >"

merchant_txn_ref
string

The merchant transaction reference ID.

Maximum string length: 45
Example:

"qwe"

customer_ip
string

The IP address of the cardholder.

Maximum string length: 45
Example:

"127.0.0.1"

return_url
object

A JSON object containing the return URLs. (This field is mandatory for 3DS transactions.)

billing_address
object

A JSON object containing the billing address of the cardholder.

shipping_address
object

A JSON object containing the shipping address of the cardholder (optional).

time_zone
string

The country time zone of the transaction.

Maximum string length: 128
Example:

"Asia/Kuala_Lumpur"

Response

201 - application/json

Payment processed successfully

success
boolean

True on successful transaction, false on failure.

Example:

true

status_code
integer

The status code of the transaction.

Example:

201

is_live
boolean

True if live transaction, false if test transaction.

Example:

false

transaction_type
string

The transaction type (e.g., CAPTURE).

Example:

"CAPTURE"

gateway_response
object

A JSON object containing the response from the gateway.

merchant_details
object

A JSON object containing the details of the merchant.

payment_details
object

A JSON object containing the payment details.

transaction_details
object

A JSON object containing details of the transaction.

risk-details
object

A JSON object containing details of risk.