Key Points
- The Authorization API secures the specified amount on the customer’s payment method, but the funds are not transferred until a capture is performed.
- Capture: Finalizes the transaction by transferring the authorized funds from the customer’s account.
- Void: Cancels the authorization, releasing the held funds back to the customer.
- Use cases for this API include scenarios where the exact final amount may vary, such as hotel bookings, car rentals, or pre-order situations.
Flow diagram
Api Parameters
Authorizations
API Key for Authorization. Format: 'Basic YOUR_API_KEY_HERE'
API Key specific to x-api-key.
Body
The request payload to authorize a payment transaction.
The amount of the transaction.
"1000"
The abbreviation of the processing currency of the product (e.g., JPY).
3
"JPY"
A JSON object containing the Card Details.
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 URL. (This field is mandatory for 3DS transactions.)
A JSON object containing the shipping address of the cardholder (optional).
A JSON object containing details about the browser used by the cardholder (optional).
The country time zone of the transaction.
128
"Asia/Kuala_Lumpur"
Response
Payment authorized 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., PRE_AUTH).
"PRE_AUTH"
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.