Integrations / developer route

Connect once. Keep every state observable.

Choose the player-facing integration pattern, connect payment and risk services, consume an explicit webhook model, and prove edge cases before commercial activation.

Request gateway accessReview integration paths
Hosted cashier

Faster control boundary

A gateway-hosted or embedded payment surface can reduce raw payment-data exposure and centralize method availability. Branding, redirect behavior, accessibility, and return states remain part of product QA.

API-led cashier

Greater experience control

The operator owns more of the interface while the gateway provides tokenization, payment intents, route decisions, and events. PCI and security responsibilities must be mapped for the actual implementation.

Hybrid path

Control where it matters

Combine gateway-managed payment entry with operator-managed cashier navigation, account context, risk decisions, and payment history.

Illustrative event contract

Design for duplicate, delayed, and reordered events.

This example is conceptual, not live documentation. Final fields and endpoints are provided with the selected service configuration.

{
  "event": "payout.reviewed",
  "event_id": "evt_example",
  "payment_id": "pay_example",
  "state": "approved",
  "route": "configured-payout-route",
  "occurred_at": "ISO-8601 timestamp"
}

Integration gates

Technical readiness is not provider approval.

Track both. A sandbox can be complete while commercial, compliance, or method activation is still pending.

  1. 1

    Architecture review

    Cashier, account context, tokenization, routes, risk services, ledgers, reporting, and data boundaries.

  2. 2

    Sandbox build

    Payment intents, webhooks, idempotency, retries, timeout handling, and operational tooling.

  3. 3

    Edge-case proof

    Reversals, delayed confirmation, duplicate events, partial failure, disputes, payout holds, and reconciliation breaks.

  4. 4

    Commercial activation

    Operator and method approvals, production credentials, route limits, monitoring, ownership, and rollback plan.

Migration

Change gateways without changing every state at once.

Inventory current payment objects and events, reproduce reporting and finance outputs, map provider-specific fields, test the new route, introduce controlled traffic, compare outcomes, and preserve rollback until the new stack is stable.

Scope a migration

Make the event model a product decision, not an afterthought.

Share your operating model, markets, methods, and payout needs. We will use them to scope eligibility and the technical route.

Request gateway access