Live in 5 marketsProduction-ready24/7 automated

Your clients already hold the money. We connect it to your cashier.

AbePay is payments infrastructure for African markets. It appears as a method inside your own cashier. The client taps Deposit, picks AbePay, pays from the mobile wallet, bank account or stablecoin they already hold, and their balance moves the moment the funds are verified. Withdrawals run the same path in reverse. No new account, no second onboarding, and no identity checks of ours.

Read the integration spec Use the live product

Instant

Credited on verified funds

Zero

Identity checks performed by us

African markets live today

24/7

Weekends and holidays included

Overview

What AbePay is

The problem

In our markets a retail trader holds their money in a mobile wallet, a domestic bank account reachable only by instant transfer, or in stablecoin. Very few hold a card usable for cross-border spend. Those clients open a cashier and find nothing in it they can actually pay with.

What we are

One line item in that cashier that resolves to whatever the client's own market supports: mobile money, instant bank transfer or stablecoin, on infrastructure we operate ourselves.

What changes for you

A funding method that works for clients you are already approved to serve, in markets you already operate in, with settlement netted and reconciled daily, and no operational load on your side when a payment network has a bad afternoon.

Product

A cashier payment method for deposits and withdrawals

Operator

AbePay. Payments infrastructure for African markets.

Placement

Inside the broker's own cashier. The client never leaves the broker's site.

Client onboarding

None. Your existing client, with your existing verification.

Credit timing

Instant, on a signed notification issued only after the payment is independently verified

Live markets

Kenya · Uganda · Tanzania · Nigeria · South Africa, plus stablecoin everywhere

Settlement

Net and periodic. Daily, weekly or on threshold, against a daily reconciliation file

Integration

Five endpoints and four signed webhooks, or we build to your existing cashier spec

Availability

24/7/365, fully automated

Status

Production-ready. Sandbox within one business day of a technical call.

Client experience

What your client sees

Four taps, inside your interface, start to finish. The client never leaves your site and never creates an account with us.

9:41▪▪▪ ▮

Deposit · choose a method

Card

Visa · Mastercard

›

AbePay

Instant · local methods & crypto

›

Bank wire

2–5 business days

›

₮

Crypto

Network fees apply

›

Step 01AbePay appears as a method

9:41▪▪▪ ▮

Amount to deposit

$100.00

You payEGP 4,900

Rate49.00

FeesNone

Pay with

InstaPay

From your bank app

✓

Mobile wallet

•••• 350

›

₮

USDT

TRC-20

›

Continue

Step 02Amount and method, priced up front

9:41▪▪▪ ▮

Approve in your bank app

We have sent an InstaPay request to your bank app. Approve it to complete.

AmountEGP 4,900

Credits$100.00

ReferenceABE-7Q2F8K

Waiting for confirmation…

Cancel

Step 03Authorised on the client’s own handset

9:41▪▪▪ ▮

✓

$100.00 deposited

Credited to your trading account
in 38 seconds

PaidEGP 4,900

Received$100.00

ReferenceABE-7Q2F8K

ReceiptIPN-4471902

Back to trading

Step 04Balance updated, receipt issued

Illustrative rendering of the client journey, shown here for a client in Egypt. The screens are a design mock-up rather than a capture of any live interface, amounts and rates are indicative, and the cashier chrome would follow your own design system. The point is the placement: AbePay is one row in a list the client is already looking at, and the four steps above are the entire experience. The method list adapts to the client’s own market, so a client in Morocco or Tunisia sees their domestic options in the same position. Withdrawals reverse the same path.

Mechanics

How it works inside your cashier

From the client's side it is four taps: Deposit, AbePay, amount, confirm. Underneath, two rules govern everything. A rail confirmation is never taken at face value. We verify every payment independently before we tell you anything. And on withdrawals we are only ever instructed after you have verified and debited your own client, so a payout cannot exist without a matching debit.

Deposit

Steps 10 and 11 are the ones that matter. A rail confirmation is never taken at face value: AbePay re-verifies the payment independently, and only a verified payment produces the notification that makes Deriv credit the client.

Withdrawal

The client is verified and debited by Deriv before AbePay is ever instructed, so no payout can be triggered without a matching debit. Step 03 carries an idempotency key: a retried instruction pays once.

Where the client experiences the wait. On a deposit, the only step with human latency is the client entering their own PIN or sending the transfer. Everything after that is machine-to-machine and completes in seconds. On a withdrawal there is no human step on our side at all.

Responsibilities

What we do, and what we do not

A payment method is easiest to approve when the responsibilities are unambiguous. Ours are drawn narrowly on purpose.

We perform no KYC

You identify, verify and onboard the client. We receive an opaque client reference and never build an identity record of our own. Every instrument we accept has already been verified by its issuer before it can transact.

We hold no client relationship

No AbePay account, no separate login, no marketing to your clients, and no support relationship we can be confused for. A client who contacts us about anything other than a payment in flight is returned to you.

We hold no client funds

Funds move through the platform to settlement on the agreed cycle. No stored value, no wallet, and nowhere for a client to leave a balance. A conduit with a short, fully auditable dwell time.

We do not decide who may trade

Eligibility, jurisdiction restrictions and product suitability are entirely yours. Where you do not accept clients, no AbePay method appears. The list is resolved from your client record, not ours.

We do run AML on the payment leg

Velocity and value ceilings per client, structuring detection, sanctions screening on payout destinations, instant suspension, and real-time alerting. Transaction monitoring that complements your client-level controls rather than duplicating them.

We do own the payment outcome

Reconciliation, exceptions, stuck payments, reversals and rail-side disputes are ours to resolve. You get one authoritative status per transaction and a daily settlement file, and never have to chase a payment network.

Coverage

Where the method appears

Wherever you operate. Local methods where we hold direct rail connectivity, and stablecoin everywhere else, from day one, with no market-specific work required. Your cashier asks us which methods a given client can use and we answer from live configuration, keyed on their country and currency. Adding a market is a configuration change on our side, not an integration change on yours.

Market	Methods shown to the client	Currency	Status
Kenya	M-Pesa · Airtel Money · crypto	KES	Live
Uganda	MTN MoMo · Airtel Money · crypto	UGX	Live
Tanzania	M-Pesa · Mixx · Airtel Money · crypto	TZS	Live
Nigeria	Instant bank transfer · crypto	NGN	Live
South Africa	Instant EFT · bank transfer · crypto	ZAR	Live
Every other market	USDT (TRC-20 / BEP-20) · USDC	USD	Live
North Africa	Domestic wallets and bank transfer, enabled per market on approval; stablecoin available immediately	EGP · MAD · DZD · TND	On approval

Why crypto matters here

Stablecoin is not a fallback in these markets. For a large share of clients it is already the primary way they hold and move dollars. It also makes the method genuinely universal: a client in a market where we hold no local connectivity still sees AbePay in your cashier and can still fund and withdraw instantly. Deposits credit on confirmations, withdrawals pay to the client's own address, and there is no settlement float or FX leg to arrange in advance.

Money

How funds actually move

The client's balance movement and the movement of real funds are separated. You credit or debit your client instantly on our signed notification; the money between us settles net, on the cycle you prefer.

Deriv credits and debits its client instantly on our signed notification. The movement of actual funds between AbePay and Deriv move net and periodically: withdrawals offset deposits, and only the balance settles on the agreed cycle.

Collection and credit

Funds clear into AbePay settlement accounts in-market. You credit your client on our signed notification, which is issued only after the payment has been independently verified.

Netting and settlement

Withdrawals we fund offset deposits we collect, so in a two-way market the flows largely cancel and only the balance moves. The net position settles on the agreed cycle against a daily reconciliation file listing every transaction with its rail reference.

Disputes and reversals

Reversals, failed payouts and rail-side disputes are carried by us and disclosed in the same file. You are never exposed to a payment network's dispute process.

Or run it the other way

If you would rather pre-fund a float and have us draw against it, or settle gross rather than net, both are supported without change to the integration. The flow above is a recommendation, not a condition.

Trust

Security and controls

Payment integrity

Inbound rail notifications are validated against published source ranges, browser-originated callbacks are rejected outright, and every payment is independently re-verified before we notify you. Distributed locks and idempotency keys make double-processing impossible in both directions.

Message integrity

HMAC-SHA256 over the raw body with a timestamp and nonce on every request and every webhook, so an altered, replayed or late message is rejected. Per-environment keys, rotatable without downtime. Mutual TLS and IP allow-listing available on request.

Ordering guarantees

We never notify a deposit we have not verified, and we never disburse before you confirm the debit. Both rules are enforced in code rather than by procedure, which is what removes the forged-callback and double-spend classes of risk.

Crypto controls

Deposits are credited on confirmations, not on broadcast. Payout addresses are screened before disbursement, with sanctioned and high-risk addresses refused, and withdrawals pay only to an address the client supplied through your cashier.

Data protection

We ask for an opaque client reference, an amount and a country, not names, documents or dates of birth, which we reject if sent. Transaction records are retained for the statutory financial record-keeping period. Kenya's Data Protection Act 2019 governs our handling.

Platform

TLS throughout on an edge-hosted platform, secrets in an encrypted store, administrative access behind a TOTP second factor and a bot challenge, privileged actions logged. Card data is never handled, placing us outside PCI scope.

Reliability

How we run it

Continuous reconciliation

Every non-terminal transaction is re-checked each minute, with an exception sweep every five. Nothing sits in limbo waiting for a client to complain.

Live health checks

An automated probe walks the payment path every two minutes. Failures page the operations team instantly, and a settlement report closes each day.

Graceful degradation

A rail outage removes only that method. The cashier keeps offering the others for that market, and stablecoin is always available. One network's bad afternoon never takes AbePay offline.

Incidents reach engineering

Payment incidents go straight to the people who can resolve them, not to a support tier that cannot. One named contact owns the relationship, with a shared channel to your operations team.

Deploys never drop a payment

Inbound rail notifications and reconciliation keep running through maintenance, so a payment in flight during a deploy still completes.

Full audit trail

Every transaction stores the rail reference, the amount, the instrument, the full status history and the timestamps, available per transaction and in the daily file.

Next steps

Talk to us

The next step is a thirty-minute technical call to agree whether we build to your cashier specification or you review ours. Everything else follows from that. We are equally ready to complete a due-diligence questionnaire and to start with a capped pilot in a single market.

Partnerships

support@abepayy.com

+254 793 789 350

Live application

app.abepayy.com

Integration spec

app.abepayy.com/developers