Skip to main content

Direct Payment API 🧶

You've chosen to own every part of the payment experience — here's what that gives you.

The Direct Payments API puts you in complete control — backend-driven, with no client-side SDK required, so you handle tokenization, SCA/redirect flows, consent logic, and state transitions yourself. You build a fully customised payment form, with direct access to every API response and payment event along the way.

How does it work? 🛎️​

You send everything through one endpoint — the Direct Payment API initiates and manages payments across all flows (credit card, A2A, wallets) and use cases (initial, recurring, deferred), so you don't juggle separate integrations per method. This page covers flow-agnostic patterns that apply across all of them; for method-specific details, see the corresponding guides.

Under the hood, it's a server-to-server JSON integration: POST /api/direct/payments creates a payment, and every follow-up operation uses a sub-path on that payment's ID.

See it in action 🧶​

The diagram below shows one example flow — a payment that goes through a pending/redirect state before reaching an outcome.

Where to go next 🛎️​

  • Follow the Quickstart to confirm your merchant account provisioning, integrator setup, and permissions are in place.
  • Review Authentication & Environments to get your API keys and confirm your sandbox and production URLs.
  • Work through the guides to build out the full flow, and check the API Reference for the specific endpoints each guide uses.
  • Run through the Go Live checklist before switching to production.