Skip to main content
POST
cURL

Authorizations

Authorization
string
header
required

Enter your API token

Headers

User-Agent
string

Body

application/json
amount
integer
required

Payment amount in the smallest currency unit (e.g., cents).

Example:

12997

currency
string
required

Three-letter ISO 4217 currency code (e.g., USD, EUR).

Pattern: ^[A-Z]{3}$
Example:

"USD"

paymentMethod
object
required

The chosen payment method details (e.g., card).

merchantReference
string
required

Merchant's unique identifier for this payment.

Example:

"PAYMENT-12345"

goodsType
enum<string>
required

Type of goods being purchased: PHYSICAL = tangible items, DIGITAL = non-physical items, MIXED = combination of both.

Available options:
PHYSICAL,
DIGITAL,
MIXED
Example:

"MIXED"

source
object
required

Details related to where the payment originated.

captureNow
boolean

Determines how the payment is processed. Default: false → Authorization only (funds reserved, must capture later). If true → Sale (authorize and capture in one step).

Example:

true

descriptor
string

Text shown on the customer's bank statement (e.g., merchant or product name).

Example:

"MyStore Online"

productItems
object[]

List of product or service items included in this payment.

Example:
consumer
object

Consumer details such as name, email, phone.

billing
object

Billing address information.

shipping
object

Shipping address and recipient details.

previousFailures
object[]

Array of previous failed payment attempts with other providers.

Example:

Response

OK

paymentId
string

Unique identifier for the payment generated by the system.

Maximum string length: 32
Example:

"pay_1234567890abcdef"

merchantReference
string

Reference passed in by the merchant for correlation.

Example:

"ORDER-12345"

amount
integer

Amount processed in the smallest currency unit.

Example:

12997

currency
string

ISO 4217 currency code used in the payment.

Example:

"USD"

status
enum<string>

Current state of the payment.

Available options:
PENDING,
AUTHORIZED,
CAPTURED,
REFUNDED,
VOIDED,
FAILED
Example:

"CAPTURED"

paymentMethod
object

The chosen payment method details (e.g., card). Sensitive fields are masked in responses.

captureNow
boolean

Determines how the payment is processed. Default: false → Authorization only (funds reserved, must capture later). If true → Sale (authorize and capture in one step).

Example:

true

descriptor
string

Text shown on the customer's bank statement (e.g., merchant or product name).

Example:

"MyStore Online"

goodsType
enum<string>

Type of goods being purchased: PHYSICAL = tangible items, DIGITAL = non-physical items, MIXED = combination of both.

Available options:
PHYSICAL,
DIGITAL,
MIXED
Example:

"MIXED"

productItems
object[]

List of product or service items included in this payment.

Example:
consumer
object

Consumer details such as name, email, phone.

billing
object

Billing address information.

shipping
object

Shipping address and recipient details.

createdAt
string<date-time>

Timestamp when the payment was created.

Example:

"2024-01-15T10:30:00Z"

updatedAt
string<date-time>

Timestamp when the payment was last updated.

Example:

"2024-01-15T11:00:00Z"

transactions
object[]

Array of transaction attempts made for this payment.

Example:
source
object

Details related to where the payment originated.