Collections

Collections let you take payment from customers in supported currencies. After a successful payment, funds are credited according to your product and wallet setup.

Integration pattern

Hosted checkout follows this flow:

Initialize payment — Create a session using the initialize API (see ).
Keep references — Store your reference and the returned transactionRef for support and reconciliation.
Webhook — Listen for status updates on the URL you configure for your API key ().
Verify (optional) — Poll or query status if you need a server-side check beyond webhooks ().

For flows where you need payment instructions in API responses instead of redirecting to a hosted page, use the path together with as documented there (create → accept).

Collection methods

Method	Description	Currencies (examples)
	Cards with 3-D Secure where required	NGN, USD, and others as enabled
	Mobile money across supported markets	GHS, KES, UGX, TZS, and others as enabled
	Stablecoin on-chain collection	USD-equivalent stablecoins as enabled

Availability depends on your account and environment. Use the discovery endpoints below instead of hardcoding rails or currency lists in your app.

Discovering what is available

Corridors and methods can change with configuration and rollout. Before you build UI or validation:

GET /api/v1/client/currencies — active currencies and related metadata.
GET /api/v1/client/banks?currency=<CODE> — bank or network identifiers for that currency, where applicable.

For API-first deposit flows, the documentation and describe how to request and accept deposit quotes.

Authentication

Collection routes use business API keys and signed requests. Follow for headers and signing—do not embed secrets in mobile or browser clients.