Local payouts fit when…
Your destination is supported, you can prefund the payout currency, and you want a shared API across local markets.
Explore Platform PayoutsChoose your payout route
A clearer path
to local payouts.
Compare the integration behind a payout, from funding through reconciliation.
Two routes. Different operating models.
Correspondent banking
- Your platform
- Banking partner
- Correspondent bank(s)
- Receiving bank
Illustrative route. The number of intermediaries varies by corridor and banking relationship.
Zennopay local payouts
- Your backend
- Zennopay
- Licensed local partner
- Local rail & beneficiary
One API coordinates supported local routes. Regulated payment activity runs through licensed partners.
What changes for your team.
| Consideration | Correspondent banking | Zennopay |
|---|---|---|
| Integration | Use your banking partner’s portal, file connection or API. Requirements depend on the provider. | One payout API for supported local routes, with a consistent beneficiary and status model. |
| Funding | Fund or settle under the terms agreed with your banking partner. | Prefund your payout currency. The available balance must cover the payout reservation. |
| Tracking | Services such as Swift GPI offer payment tracking. Access and event formats depend on your banking partner. | Read the current payout state through the API and receive signed status webhooks. |
| Retries | Duplicate handling depends on your provider’s interface and contract. | Reuse the same idempotency key and input to retrieve the original payout. Changed input returns a conflict. |
| Reconciliation | Reconcile using the statements, references and payment data your provider supplies. | Use payout IDs, your reference, recipient amount, fee details and authoritative status reads. |
| Coverage | Useful when your destination, currency or payment type requires a broader banking relationship. | Start with the live routes published in our coverage directory. Roadmap markets require activation. |
Choose for the corridor you need.
A banking route may fit when…
You need an unsupported destination, different funding terms, or a payment type outside Zennopay’s enabled routes.
Check coverageCompare the contract, too.
Pricing, limits, eligibility and delivery timelines depend on the route and your commercial agreement. No universal cost or speed advantage is claimed here.
Sources: Swift corporate tracking · Zennopay payout contract · Funding
Build on the rails your customers use.
Explore the integration in sandbox. Talk to us about your production corridor.