Mikaty · BCEAO instant payment · XOF · Senegal
Orange Money, Wave, Yas, cards, dedicated-IBAN transfers and BCEAO instant payment — one integration, one webhook, one ledger. Your BCEAO screening and reporting obligations are handled by the platform that moves the money, and every decision stays attributable.
Supervision & compliance
Supervision is held by the platform that executes the payments: no export to a second system, no reconciliation between two vendors.
Every collection and every payout is evaluated before it moves.
The ledger is never rewritten; it is appended to.
Sensitive decisions are taken by two people, and stay attributable.
The registers the regulator expects, produced by the system that executes.
A flagged operation waits, funds kept; a payout can never exceed the balance.
Thresholds, limits and screening apply to every operation without intervention; people decide only the flagged cases.
BCEAO bench, Performance module: 0 deviations across 80 scenarios, no 5xx response.
10-year regulatory retention, 72 h incident register, safeguarded funds recomputed daily.
Who it is for
From institutions centralising regulated flows to merchants collecting online: same rails, same ledger, same API.
Lotteries and betting, large collection networks: all your operators and all your rails on one platform, supervised where the money passes.
Collect for your sellers, split, pay out — without ever splitting more than was collected.
A hosted checkout in your colours, payment links, invoices, subscriptions — and refunds always capped at the collection.
Centralisation
Mobile money, bank transfer, instant payment: every payment method lands in the same API, the same webhook and the same ledger.
BCEAO instant payment
Production-entry tests closed. The Union's instant payment, integrated into your flows — as a neo-pays merchant.
Dedicated IBAN
Available on requestA collection account in your name, with a partner bank of the marketplace. Each incoming transfer is detected by notification and reconciled automatically; outbound wires leave from the same IBAN.
Controls
Every collection and every payout is evaluated before it moves: per-business and per-rail limits, amount thresholds, regulatory thresholds. A flagged operation is not silently refused — it is held, funds kept, and an operator decides. Thresholds can only be loosened under four-eyes approval.
Scalability
Performance module 100% (0 deviations across 80 scenarios), no 5xx response. Every service scales horizontally, independently of the others.
Getting started
Test keys traverse the same code as production, with no money moving.
Create your account. It stays inactive until your file is validated.
RCCM or NINEA, legal representative, beneficial owners — verified before approval.
sk_test_ or sk_live_, shown once; restricted to your IP addresses if you wish.
One call, one signed webhook: your first collection is in the ledger.
Developers
A REST API, amounts as strings, built-in idempotency, signed webhooks and a public OpenAPI specification.
curl https://api.neo-pays.com/v1/payments \
-H "Authorization: Bearer $NEOPAYS_SECRET_KEY" \
-H "Idempotency-Key: commande-1042" \
-H "Content-Type: application/json" \
-d '{
"amount": "10000",
"currency": "XOF",
"platform_id": "<platform_id>",
"merchant_reference": "commande-1042"
}'
HTTP/1.1 201 CreatedPOST /webhooks/neo-pays
X-NeoPays-Signature: t=1723651200,v1=9f2c…d41a
Content-Type: application/json
v1 == HMAC-SHA256(secret, t + "." + body)
|now − t| ≤ 300 sContact
Pricing per business, by rails and volumes. Write to us, or open a test account under real conditions.
A test account under real conditions, or a conversation with the team.