Changelog
This page tracks capability changes rather than every documentation edit. The authoritative
machine-readable view is GET /v1/capabilities; channel availability is reported
by GET /v1/channels.
Live now
Section titled “Live now”| Surface | Endpoints |
|---|---|
| Contact verification | POST /v1/verifications, POST /v1/verifications/:reference/check, GET /v1/verifications/:reference |
| Collections | POST /v1/collections, GET /v1/collections/:id |
| Reserved accounts | POST /v1/reserved-accounts, GET /v1/reserved-accounts, GET /v1/reserved-accounts/:id |
| Deposits | POST /v1/deposits for collection_va and reserved_va |
| Payouts | POST /v1/transfers, POST /v1/withdrawals |
| Bank lookup | GET /v1/banks, POST /v1/banks/resolve |
| Beneficiaries | GET /v1/beneficiaries, POST /v1/beneficiaries |
| Balances and ledger | GET /v1/balances, GET /v1/transactions, GET /v1/recipients |
| Channels and capabilities | GET /v1/channels, GET /v1/capabilities |
| Outbound webhooks | verification.*, collection.*, reserved_account.created, ping |
| API conventions | Envelope, request ids, scoped API keys, idempotency, rate limiting |
Coming soon
Section titled “Coming soon”| Surface | Current behaviour |
|---|---|
| Cards | POST /v1/cards returns 501 coming_soon; cards is coming_soon in the capability map |
| Card deposits | POST /v1/deposits with channel: "card" returns 400 invalid_request and Card deposits are not available yet. No card provider is configured. |
| Open banking | The channel defaults to coming_soon; even when enabled, it only returns a redirect URL if one is configured for the deployment. Otherwise 400 invalid_request |
Currency availability is separate from endpoint availability. The wallet catalog marks NGN as live,
EUR and GBP as sandbox, and USD, USDT, and JPY as coming_soon; a payout in a coming_soon currency
fails with 501 rather than executing.
Versioning
Section titled “Versioning”The public surface is versioned in the path (/v1). Additive changes — new endpoints, new optional
response fields, new event types — may ship without a version bump. Clients should ignore unknown
fields and unknown event names. Breaking changes will arrive under a new path version.