Skip to main content

Operations

Operation Types​

operationMeaningTypical use case
purchaseStandard sale (one-step); funds captured immediatelyE-commerce checkout
debitCharge a customer for a previously agreed service (no linked Checkout purchase)Post-paid services, back-office charges
creditPayout / push funds to the customerPayouts, refunds, rewards
transferMove funds between two parties using the Checkout formP2P, marketplace payouts

[!NOTE] Use purchase unless your business explicitly requires one of the others. recurring_init, vat_calc, and the > methods array are valid only for purchase.

Purchase​

operation: purchase

Description: Initiates a standard sale (purchase) operation. The customer is charged immediately for the specified amount.

Typical use cases:

  1. One-time e‑commerce payments
  2. Standard online purchases where funds are captured right away

Debit​

operation: debit

Description: Initiates a debit operation, where funds are taken from the customer’s payment instrument (e.g. card or account) without a linked prior purchase via Checkout.

Typical use cases:

  1. Charging a customer based on a previously agreed service (e.g. post‑paid services)
  2. Manual debits initiated by the merchant’s back‑office or CRM flow

Credit​

operation: credit

Description: Initiates a credit operation, where funds are sent to the customer instead of being charged from them. This is effectively a payout/credit to the customer’s card or account.

Typical use cases:

  1. Payouts to customers (cash‑out, winnings, rewards, etc.)
  2. Manual adjustments or balance top‑ups in favor of the customer

Transfer​

operation: transfer

Description: Initiates a transfer between two parties/accounts using the Checkout form. Funds are moved from the source side to the destination side according to your business logic.

Typical use cases:

  1. Internal transfers between customer wallets/accounts
  2. Marketplace or platform flows where funds are moved from one participant to another

Post-payment operations​

Post-payment actions (capture, refund, void, recurring, retry, status lookup) act on a payment that has already been initiated through /api/v1/session. See the Payment Checkout API for request parameters and examples.

API requests​

Request parameters, field definitions, and curl examples for all Checkout operations live in the API requests section, not on this page.