Skip to main content
POST
Authorize a Payment
Notice: Authorization API (v1) is scheduled for deprecation. Use v2 for future integrations.

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

Flow diagram image

Api Parameters

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 authorize a payment transaction.

amount
string
required

The amount of the transaction.

Example:

"1000"

currency
string
required

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

Maximum string length: 3
Example:

"JPY"

card
object
required

A JSON object containing the Card Details.

merchant_id
string
required

The merchant ID (DASMID).

Maximum string length: 128
Example:

"< Merchant ID >"

billing_address
object
required

A JSON object containing the billing address of the cardholder.

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 URL. (This field is mandatory for 3DS transactions.)

shipping_address
object

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

browser_info
object

A JSON object containing details about the browser used by 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 authorized 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., PRE_AUTH).

Example:

"PRE_AUTH"

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.