Authorizations
Headers
Specifies the version of the API to use. This must be set to 2.4
.
"2.4"
Body
Your reference for the payment.
1 - 256
The 3-letter currency code in ISO 4217 format.
e.g. use USD
for US dollars.
AED
, AFN
, ALL
, AMD
, ANG
, AOA
, ARS
, AUD
, AWG
, AZN
, BAM
, BBD
, BDT
, BGN
, BHD
, BIF
, BMD
, BND
, BOB
, BOV
, BRL
, BSD
, BTN
, BWP
, BYR
, BYN
, BZD
, CAD
, CDF
, CHE
, CHF
, CHW
, CLP
, CNY
, COP
, COU
, CRC
, CUC
, CUP
, CVE
, CZK
, DJF
, DKK
, DOP
, DZD
, EGP
, ERN
, ETB
, EUR
, FJD
, FKP
, GBP
, GEL
, GHS
, GIP
, GMD
, GNF
, GTQ
, GYD
, HKD
, HNL
, HRK
, HTG
, HUF
, IDR
, ILS
, INR
, IQD
, IRR
, ISK
, JMD
, JOD
, JPY
, KES
, KGS
, KHR
, KMF
, KPW
, KRW
, KWD
, KYD
, KZT
, LAK
, LBP
, LKR
, LRD
, LSL
, LYD
, MAD
, MDL
, MKD
, MMK
, MNT
, MOP
, MRO
, MUR
, MVR
, MWK
, MXN
, MXV
, MYR
, MZN
, NAD
, NGN
, NIO
, NOK
, NPR
, NZD
, OMR
, PAB
, PEN
, PGK
, PHP
, PKR
, PLN
, PYG
, QAR
, RON
, RSD
, RUB
, RWF
, SAR
, SBD
, SCR
, SDG
, SEK
, SGD
, SHP
, SOS
, SRD
, SSP
, SVC
, SYP
, SZL
, THB
, TJS
, TMT
, TND
, TOP
, TRY
, TTD
, TWD
, TZS
, UAH
, UGX
, USD
, UYU
, UZS
, VND
, VUV
, WST
, XAF
, XAG
, XAU
, XBA
, XBB
, XBC
, XBD
, XCD
, XDR
, XFU
, XOF
, XPD
, XPF
, XPT
, XSU
, XTS
, XUA
, YER
, ZAR
, ZMW
, ZWL
The amount you would like to charge the customer, in minor units. e.g. for $7, use 700
.
Some currencies, such as Japanese Yen, do not have minor units. In this case you should use the value as it is, without any formatting. For example for ¥100, use 100
.
If the amount is provided on this level, it would override any amount calculated from the provided line items, shipping and other amounts.
x >= 0
More information associated with the order.
A unique identifier for your customer.
Create a client session token with a customerId
to enable the client-side SDK to retrieve and manage your customer's saved payment methods. A client session token also enables saving payment methods against this customer id.
1 - 256
More information associated with the customer.
Additional data to be used throughout the payment lifecycle.
A dictionary of key-value pairs where the values can only be strings or integers.
e.g. {"productId": 1001, "merchantId": "a13bsd62s"}
Enable certain options associated with the payment method.
Response
Successful Response
Client token used to initialize the SDK on all platforms.
Expiration date & time of the client token (UTC with no timezoneinfo).
Your reference for the payment.
The 3-letter currency code in ISO 4217 format.
e.g. use USD
for US dollars.
The amount you would like to charge the customer, in minor units. e.g. for $7, use 700
.
Some currencies, such as Japanese Yen, do not have minor units. In this case you should use the value as it is, without any formatting. For example for ¥100, use 100
.
If the amount is provided on this level, it would override any amount calculated from the provided line items, shipping and other amounts.
x >= 0
More information associated with the order.
A unique identifier for your customer.
More information associated with the customer.
Additional data to be used throughout the payment lifecycle.
Enable certain options associated with the payment methods.
Warning messages to indicate missing information that are required for payment methods, checkout modules and other features; or when third-party services are unavailable.