Issue cards your customers control
Run debit and prepaid card programmes with controls in the customer's hands, authorisation on the real-time ledger and card data kept out of your apps.
Separate PCI card vaultFreeze and limits in-appDisputes workflow
A complete card programme
Issuing
Physical and virtual debit and prepaid cards linked to accounts.
Controls & limits
Freeze, channel controls and spending limits set by the customer.
Authorisation
Real-time authorisation against available balance and limits.
Clearing
Settlement files matched to authorisations and posted to the ledger.
Disputes
Chargebacks and dispute cases with deadlines and evidence.
PCI card vault
Card numbers live in a separate vault; apps show them only in a secure frame.
A card, from issue to dispute
Issue
Request a card in the app or at the branch.
Control
The customer sets limits and freezes in the app.
Spend
Authorisations check the live balance.
Resolve
Disputes tracked to resolution with the network.
Connected to the rest of your bank
- Accounts — cards spend from real accounts
- Product Factory — card programmes, fees and limits
- Customer web — card controls for customers
- Integrations — processors and networks
Release status
- Card issuing and controls
- ◷ Phase 2
- Disputes and chargebacks
- ◷ Phase 2
Dates follow the public roadmap and may change.
Cards questions
Which networks and processors?
Verve, Visa, Mastercard and AfriGo through processors such as Interswitch and others; see Integrations for status.
Do our apps ever handle card numbers?
No. Card data stays in the card vault, in its own PCI scope; the apps never receive full card numbers.
Plan your card programme
Talk to us about networks, processors and timelines.