Home / Payouts
For Payments Ops & Marketplace Ops
Run payouts at scale—with built-in controls.
Payout workflows are compliance-gated and idempotent by design, with a clear audit trail from request to completion (or failure/retry).
Payout runs fail in predictable ways.
Duplicate disbursement risk, missing compliance checks, and inconsistent approvals create operational stress and hard-to-audit outcomes.
Duplicate payout attempts
Idempotency should treat second clicks as replays—not new disbursements.
Compliance gating gaps
Eligibility checks must block payouts until requirements are satisfied.
Status ambiguity
A payout needs a traceable timeline through processing to completion or recovery.
Built for reliability: gated, idempotent, traceable.
Payout eligibility is gated by compliance state (KYC/KYB) and policy limits. Every payout is traceable to a request, a beneficiary, provider references, and ledger postings.
- Create payouts with explicit idempotency keys
- Surface provider failures with actionable reasons
- Prefer replay/reconciliation over manual status edits
Failure modes & recovery (UI checklist)
- Provider rejects payout: show reason and allow re-attempt only when policy allows
- Duplicate attempt: return original payout snapshot
- Stuck processing: verify webhook ingestion and reconcile
From payout request to completion in four steps.
Create or import beneficiaries
Validate payout methods and collect required metadata.
Apply eligibility + limits
Gate payout initiation based on compliance state and policy.
Initiate payouts idempotently
Prevent duplicates on retries and persist provider references.
Track status + export
Surface lifecycle updates and export records for reconciliation.
Integrations: APIs, webhooks, and exports.
Keep payout state consistent across your systems. Use webhooks for lifecycle updates and exports for reconciliation workflows.
Example event topics
payout.initiated payout.processing payout.completed payout.failed
Names are illustrative. Use normalized lifecycle events and explicit recovery states for ops workflows.
Reconciliation packs finance can trust.
Export payout runs with the fields your team needs for month-end close: provider references, timestamps, statuses, and beneficiary identifiers.
Example export columns
| Field | Why it matters |
|---|---|
| payout_id | Stable identifier for downstream systems. |
| beneficiary_id | Links payouts to payee and payout method. |
| provider_reference | Required for bank/provider reconciliation. |
| status + timestamps | Audit trail for lifecycle and recovery states. |
Keep exports consistent so audits don’t require spreadsheet reconstruction.
Payout methods that match your program.
Configure payout methods and eligibility rules to match your risk posture and operational needs.
Availability can vary by market and compliance requirements.
Frequently Asked Questions
Which countries can I send payouts to?+
How do you handle currency conversion?+
Is there an approval workflow?+
What about compliance checks?+
Ready to Work Without Borders?
Global clients, clear contracts, compliant payments.