01
Alternative payment methods
Bank transfer, mobile money, wallets and local schemes, selected per corridor rather than bolted on as an afterthought.
- Per-corridor method sets
- Local currency presentment
- Method-level success monitoring
Payment infrastructure
Money in. Money out. Both hard.
Taking a deposit is the easy half. Paying customers out reliably, across corridors where card rails barely function, is what separates a platform that grows from one that stalls at its first payout queue.
- Settlement
- T+1
- Method types
- Cards + local APMs
- Payouts
- Automated
- Reconciliation
- Continuous
Success rate
98.4%
Settlement
T+1
Volume today
$2.31M
Payouts pending
18
Transactions
LiveRefMethodCorridorAmountStatus
TX-88410Bank transferNG → NG₦480,000Settled
TX-88411Mobile moneyKE → KEKSh 62,400Settled
TX-88412CardAE → AEAED 3,150Settled
TX-88413WalletID → IDRp 4,820,000Retrying
TX-88414Bank transferBR → BRR$ 9,140Settled
TX-88415Instant transferIN → IN₹1,24,500Settled
Provider routing
Provider A97%
West Africa
Provider B94%
East Africa
Provider C99%
South Asia
Provider D71%
SE AsiaFailed over
Rails
Local methods, because local is how people pay.
In most of the markets worth entering, the dominant payment method is not a card. A platform that only speaks card rails does not fail slowly — it fails at signup.
02
Intelligent routing
Traffic routed across providers by corridor, method and live success rate, with automatic failover when a provider degrades.
- Success-rate-aware routing
- Automatic failover
- Per-provider kill switch
- Retry policy per method
03
Payouts
Automated withdrawal processing with approval thresholds, batching and full audit — the half of payments most vendors under-build.
- Approval thresholds by amount
- Batch and scheduled runs
- Per-payout audit trail
04
Card issuing
Branded physical and virtual cards so balances get spent rather than withdrawn.
- Virtual issue on approval
- Physical fulfilment
- Spend controls per card
- Per-transaction economics
05
Reconciliation
Provider settlement files matched against the ledger continuously, with breaks aged and surfaced rather than discovered at month end.
- Automated file ingestion
- Break ageing
- Fee and FX attribution
Corridors
Where the volume actually is.
Africa, South and South-East Asia, the Gulf and Latin America. Markets where the incumbent processors settle slowly, freeze without warning, and price as though there were no alternative.
Corridor availability differs by method and by the licence you hold. We will tell you what works in your market before you sign, not after.
Corridors we route across
LATAM → AFRICAMobile money over cards
Corridor availability differs by method and by the licence you hold. Illustrative — we confirm what works in your market before you sign.
Virtual cards
Issued in seconds, spendable immediately.
A virtual card exists the moment an account is approved — no plastic, no post, no waiting. Cardholders control it from the app you ship.
- Instant issue on approval
- Freeze and unfreeze in-app
- Per-card spend limits
- Online-payment toggle
- Live transaction feed
Move to tilt · click to turn over
Card operations
Physical cards, your brand on them.
Programme administration for the whole card estate: issue, freeze, replace and reconcile, with interchange economics visible rather than buried.
- Physical fulfilment
- Estate-wide administration
- Status and lifecycle controls
- Interchange and spend reporting
Move to tilt · click to turn over
Local methods
People pay how they pay.
In most markets worth entering, the dominant method is not a card. A platform that only speaks card rails fails at signup, not slowly.
- Per-corridor method sets
- Local currency presentment
- Method-level success monitoring
Intelligent routing
Failover before you notice.
Traffic routed by corridor, method and live success rate, with automatic failover when a provider degrades and a kill switch when it does not recover.
- Success-rate-aware routing
- Automatic failover
- Per-provider kill switch
- Retry policy per method
Reconciliation
Breaks surfaced, not discovered.
Settlement files matched against the ledger continuously, with breaks aged and attributed rather than found at month end.
- Automated file ingestion
- Break ageing
- Fee and FX attribution
Corridors & licensing
The part most gateway vendors leave out of the pitch.
Integration is the easy half. In most of these markets you cannot process at all without an authorisation or a sponsoring institution behind you — a path measured in months, with a capital requirement attached. Discovering that after signing costs a quarter. So here it is before.
Supervisor
Central Bank of Nigeria
Authorisation
Payment solution service provider authorisation
Practical route
Sponsoring bank partnership, own licence later once volume justifies it
Typical lead timeMonths, not weeks
Indicative market information for planning, gathered from public sources and subject to change. It is not legal or regulatory advice, and Krexum does not provide either. Confirm your position with counsel in each market — the authorisation you need depends on what you do, not only on where you do it.
How we operate the rails
The complaints merchants have about gateways, answered as terms.
Next-day settlement as the standard
Settlement timing is written into the agreement rather than left to a support article that can change. Where a corridor cannot support it, we say which one and why before you sign.
Notice before any restriction
If compliance requires us to restrict an account, you get advance notice and a reason, except where the law forbids us to give it. Freezing a merchant without warning is the single most common complaint about gateways in these markets, and it is avoidable.
One integration, many corridors
Adding a market is configuration on our side, not a second integration on yours. The API surface, webhook contract and reconciliation format do not change per corridor.
Routing you can see
Per-corridor authorisation rates, provider mix and cost are reported to you, including when a provider is failing. A gateway that hides its decline reasons is hiding the reason to leave it.
Reconciliation against settlement files
Every movement produces a ledger entry, reconciled against the provider settlement file, with breaks surfaced in an exception queue rather than absorbed silently.
Your PCI scope stays small
Card data is handled so that it does not land in your environment, which keeps your compliance burden proportionate to what you actually do.
Indicative for evaluation. The settlement timing, notice period and reporting that bind us are those written into your agreement.
Edge cases
Every vendor demos the happy path. Ask about the bad day.
These are the failures that decide whether a platform survives its first year in production. We list them because we have had to build for them.
Common outcome
Failures accumulate until someone notices the success-rate graph, usually after the support queue does.
What we do
Routing watches live success rate per corridor and method, fails over automatically, and holds the provider out until it recovers. The kill switch is also manual if you want it.
Specification
Payments questions worth asking early.
- Settlement timing
- T+1 on supported corridors. Where a corridor cannot support it, we say so rather than quoting a best case.
- Account restrictions
- Notice before any restriction, with a stated reason. Silent freezes are the single most common complaint about incumbent processors and we treat avoiding them as a product requirement.
- Provider relationships
- Multi-provider by design. You are never dependent on one acquirer for one corridor.
- Chargebacks
- Case management with evidence assembly and deadline tracking inside the console.
- FX
- Rates and margins shown per transaction and attributed in reconciliation, not buried in a blended monthly figure.
- Compliance
- Transaction monitoring and reporting configured to the regime you operate under.