Embed financial services into healthcare workflows.
Collection, payouts, wallets and an immutable ledger, through one API, in the markets we serve. This is the module that is in production.
What is in production today.
- Available
Mobile money collection
Collect from mobile money accounts across operators, with the same request shape whatever the operator behind it.
In production today.
Executed by licensed payment institutions and mobile money operators
- Available
Payouts
Send money to mobile money accounts and bank rails, with a status that moves once whatever the provider does.
In production today.
Executed by licensed payment institutions and mobile money operators
- Available
Payment links
Collect without an integration when you need to: a link, a hosted payment page, the same webhooks as the API.
In production today.
Executed by licensed payment institutions and mobile money operators
- Available
Transfers and beneficiaries
Registered beneficiaries, repeat transfers, and one audit trail per movement.
In production today.
Executed by licensed payment institutions and mobile money operators
- Available
Top-ups and bank withdrawals
Fund a wallet, withdraw to a bank account, under the same ledger guarantees as every other movement.
In production today.
Executed by licensed payment institutions and mobile money operators
- Available
Wallets and immutable ledger
Balances derive from an append-only double-entry ledger. Every entry carries a deterministic idempotency key and a chained checksum, so a balance can always be re-derived from the entries rather than trusted.
In production today.
- Available
Multi-currency and explicit FX
One wallet, one currency. A cross-currency movement requires an explicit FX pair — there is no implicit conversion anywhere in the platform.
In production today.
- Available
Signed webhooks
HMAC-SHA512-signed callbacks, retried on a bounded schedule, with a per-attempt log you can read back and a resend you can trigger yourself.
In production today.
- Available
Scoped API keys and 2FA
Keys carry only the scopes you grant them. Dashboard access is protected by two-factor authentication.
In production today.
- Available
Real-time event stream
Server-sent events, for systems that would rather listen than poll.
In production today.
The life of one collection.
You create it
One request, with an `order_id` you choose. It must be unique within your organization — that is the whole idempotency contract, and there is no header to add.
The customer approves
The operator prompts them on their phone. Nothing in your code has to wait for it.
The status moves once
Provider callbacks are deduplicated by an atomic status transition: the first one to move the status wins, the others change nothing. Duplicate callbacks are normal, and harmless.
Your system is told
A signed webhook reaches your endpoint, retried on a bounded schedule, with every attempt logged and a resend you can trigger.
The ledger records it
A double-entry pair is written with a deterministic idempotency key and a chained checksum. The balance is a consequence of the entries, never a field someone edited.
Ten operators and payment providers. Four currencies.
Integrated providers and operators
Hub2 · AvadaPay · PawaPay · DalaPay · Paydunya · CinetPay · Wave · Intouch · Prymo · MVOLA
Currencies
XOF · XAF · CDF · USDC
One request shape, whichever provider is behind it. Adding a market means adding a provider on our side, not a code path on yours.
What has gone through it.
- Transactions processed
- 130K+
- Unique financial services users
- 90K+
What AZ54 is, in regulatory terms.
AZ54 is a software company. AZ54 does not hold funds and does not operate financial flows. Collections, payouts and transfers are executed by licensed mobile money operators and payment institutions, under their own regulatory responsibility.
In practice: we never take custody of your customers' money, we do not net, hold or settle it, and we hold no payment institution licence. What we operate is the software that instructs, records and reconciles those movements.
Questions integrators actually ask
Does AZ54 hold my customers' funds?
No. Collections, payouts and transfers are executed by licensed mobile money operators and payment institutions, under their own regulatory responsibility. AZ54 is the software layer.
Which markets and currencies?
The markets listed on this page, in XOF, XAF, CDF and USDC. Anything else is a conversation about a new provider integration, not a switch we flip.
How do you prevent a double charge?
A pay-in or pay-out is identified by the `order_id` you choose, unique within your organization. Provider callbacks are deduplicated by atomic status transition, so a repeated callback applies nothing.
What if my server misses a webhook?
Attempts are retried on a bounded schedule and each one is logged. You can read the attempts back through the API and trigger a resend yourself.
Do you provide KYC or KYB?
No. AZ54 provides no identity verification product, and nothing on this site should be read as one.
Is any of this certified?
We claim no certification of any kind — no GDPR, HIPAA, ISO, medical device or data residency claim appears anywhere on this site, because none would be true today.
Move money inside your product.
Tell us the market and the flow. We will tell you which provider carries it and what it takes.