Guides

Payment Flows

Follow the current invoice payment-link flow for merchant integrations.

Use this page to follow the current first integration path. It is a routing guide, not a replacement for the API reference.

Current first path

Start with server-created invoices and the returned payment link:

  1. Create an API key in the dashboard.
  2. Create an invoice from your server with an idempotency key.
  3. Send the payer to the invoice checkout_url payment link.
  4. Confirm fulfillment from a verified webhook or a server-side invoice status check.
  5. Reconcile credited funds with balances and the ledger.
  6. Create payouts from trusted server-side code when funds are ready to move.

This keeps API keys server-side and keeps fulfillment decisions on your backend.

Where each surface fits

SurfaceWhat it doesMerchant actionWhere to continue
API keysAuthenticate server-side merchant API callsCreate a test key, keep live keys on your backendAuthentication
InvoicesCreate one payment request and get a payment linkSend the payer to checkout_url, then check status server-sideGet Started, Invoices
Balances and ledgerShow spendable funds and audit historyReconcile credits, fees, payouts, reversals, and late depositsBalances and Ledger
PayoutsMove funds from merchant balancesCreate payout requests from trusted server-side codePayouts
Static addressesReusable deposit rails that auto-create invoicesUse for deposits, account top-ups, or repeated depositsStatic Addresses

Static addresses are deposit rails

Static addresses auto-create invoices after deposits arrive, so use invoice status checks and balance events before crediting a user account. They are useful for repeat deposits, not for replacing the invoice payment-link path for a specific order.

Main integration path