The Platform | Spendl

Choose your route

Start where your customers are.

Both routes run on the same ledger, the same payment rails and the same Aegis event layer. The difference is who owns the screen.

White-Label Wallet

Your customer experience, already plugged into the payment systems.

A branded progressive web app, cards and an operating console for your team. You own the relationship; we carry the regulated infrastructure underneath it.

Branded web app that installs to the home screen, admin console and cards
Every deposit and payout rail: card, PayShap, RTC, EFT, Pay@, Zapper and cross-border
Every customer flow: send, request, bill split, spend, remittance
You operate under Spendl's regulated status, not your own licence
Features switched on programme by programme as you roll out

Best when You want a consumer product under your name, and you'd rather not build a wallet to get one.

Public API

Your product up front, with one API doing the work behind it.

A single REST API for onboarding, money movement, cards and KYC, with 80+ documented endpoints and the same contracts that run in production.

Onboard single users or ingest batches
Move money: balances, transfers, deposits, withdrawals, top-ups
Cross-border remittance to 37 African destinations
KYC document uploads, wallets, cards, vouchers, webhooks
Same regulated stack, no branded consumer surface

Best when You already have the front end and the customers. You need a ledger, rails and compliance you don't have to build.

See it in detail

Wallet and console

A wallet for your customers and a console for your team.

Launch the customer experience and the operational layer together, with features switched on programme by programme as your rollout grows. Your team has the tools to run each feature before it reaches your customers.

Explore every wallet flow

Two mobile phones showing differently branded versions of the Spendl wallet — Customer walletBranded to each tenant

Spendl administration console showing flow of funds and product health on two monitors — Admin consoleOperations in one view

Which route is mine

Not sure which one you need?

Most people can tell within a minute. And if the answer is both, that's fine: one business can run a branded wallet and an API integration on the same ledger.

You want a consumer product under your brand
You already have a front end and just need the rails
You need cards and a console your ops team can run
You need a ledger, KYC and payouts behind your own UI
You hold no licence of your own: Either works, because you operate under ours.
You want both a branded wallet and a back-office integration: Both, on the same account and ledger.

Signed event feed

Aegis runs underneath both.

Aegis isn't an optional extra. It sits under both the White-Label Wallet and the Public API and turns every ledger entry into a signed, versioned event, so regulators, auditors and your own team can see exactly where the money went.

Evidence you can hand over

Every transaction is timestamped, attributed and signed at the moment it posts. When a regulator, banking partner or auditor asks, the record is already there, and nobody has to piece it together.

Your fraud tooling, without the lag

Ledger postings reach your fraud and compliance tooling as they happen, so you can spot patterns while the context is still fresh.

One stream, not five exports

Card, wallet and crypto activity arrive on a single feed, so the tools you already use see the whole picture.

Signed, separated events

Each event is versioned and signed, and every business has its own data store and event stream, so one business's data never mixes with another's.

Bring us the model you need to run.

FSP 53757 · FIC 74993

Keep reading

Keep the next rand you move.

See a branded wallet, cross-border and the Public API running on your own numbers. Onboarding is hands-on, whatever the size of your team.

or email support@spendl.money

Two ways to plug in.