Platform Payouts New
Send local payouts across Southeast Asia with one API.
Create reusable or one-time beneficiaries, fund a balance per environment, and send local payouts that settle on local rails across Southeast Asia. Every call is idempotent. Every status is authoritative.
Fund once. Then it is one call per payout.
Fund
Prefund a balance scoped to each environment. Sandbox and production never share money, and a payout can only draw on funds that are already there.
Create
POST /v1/payouts with an Idempotency-Key and a beneficiary. Amounts are quoted as int64 strings, never floats. Retries are safe by construction.
Track
A payout moves from created to processing to completed. Read the API for the authoritative state, or verify a signed webhook. Acceptance is not delivery, and the API never pretends otherwise.
What you get
Reusable or inline beneficiaries
Save a beneficiary once and pay them by id, or pass the details inline for a one-time payout. Both go through the same screening.
Idempotent payout creation
Send the same key twice and you get the same payout, not two. Timeouts and retries stop being a reconciliation problem.
Authoritative status tracking
created, processing, completed, failed and reversed. The API read is the source of truth; webhooks are a signed copy of it.
Signed payout webhooks
Every state change arrives signed, so your backend can verify it came from Zennopay before acting on it.
Live today
Platform Payouts settles on these rails now. More markets activate through the year.
See every market, including the roadmap →
Built for
Banks and neobanks
Add local payouts across Southeast Asia inside products your customers already use.
FX and remittance
Route payouts directly onto local rails instead of through a correspondent chain.
Global businesses
Pay out on local rails across Southeast Asia through one API rather than one banking relationship per country.