What it takes to launch a digital wallet without becoming a bank
Fintechs, telcos, retailers, and PSPs are building wallets without becoming banks. Here is the infrastructure that has to sit underneath one to work: real-time balances, tokenized issuing, funds movement, and fraud controls.
A digital wallet is a stored balance a customer holds and spends through an app, tied to a payment credential that can receive, hold, and send funds. A non-bank issuer, whether a fintech, a telecom operator, a retailer, or a payment service provider, can launch one without becoming a bank. What it needs instead is the infrastructure a bank would normally run underneath a wallet: tokenized card issuing, a ledger that reflects the true balance the moment it changes, rails that move money in and out, and fraud and compliance checks built into the same decision path as the transaction. The wallet is the non-bank's to build and own. The infrastructure underneath it is a separate question entirely.
Why non-bank issuers are building wallets now
Companies that already hold a customer relationship, a retailer with a loyalty programme, a telecom operator with a prepaid base, a marketplace with sellers waiting on payouts, are under pressure to keep more of that relationship inside their own app rather than handing the customer off to a bank card at checkout. A wallet lets them hold balances, pay out to vendors, or issue spend instruments under their own brand, closing a loop that used to end the moment a payment left their app for someone else's.
The same companies are watching fintechs and payment providers shrink the distance between earning money and spending it. A payout that used to take days to land in a bank account can now sit in a wallet the moment it is earned, ready to spend immediately. That expectation has moved from a nice-to-have to a baseline, and a non-bank that cannot offer it starts to look like it is missing something its own customers already expect elsewhere.
None of this requires becoming a bank. A wallet is a stored-value instrument the company issues and controls, not a deposit account held by a licensed institution. What it requires instead is infrastructure that performs the same real-time functions a bank's issuing and ledger systems perform: a balance that is always accurate, a credential that can spend it, and controls that catch fraud and financial crime before money moves, not after.
What a wallet needs to work underneath the app
A wallet's balance has to be correct the moment a customer looks at it. If the ledger updates in batches, overnight or on a delay, the number on screen can be wrong at the exact moment a customer tries to spend it, send a transfer, or check whether a payout has landed. The infrastructure underneath a wallet needs a ledger that updates the moment a transaction happens, not one that catches up after a settlement cycle.
The wallet needs a way to spend the balance, which means card issuing, and increasingly that means tokenized and virtual cards rather than only plastic. A customer should be able to fund the wallet and provision a spendable credential inside the app that same session, add it to a mobile wallet on their phone, and use it at checkout, without waiting for a physical card to arrive in the mail.
Money has to move in and out of the wallet from somewhere. Funding, top-ups, payroll deposits, and marketplace settlements have to land in the balance, while spend, payouts, transfers, and withdrawals have to leave it, across whatever rails the company's customers actually use. A wallet that can only take money in one way, or send it out through a single rail, will not hold up once the company wants to add new use cases.
None of that can run safely without fraud and compliance controls sitting inside the same decision as the transaction, not bolted on afterward. A customer's identity has to be verified at onboarding, transfers and top-ups need to be screened for sanctions exposure as they happen, and spend patterns need monitoring for fraud in the moment rather than in a review the next day. A wallet that gets the balance and the rails right but treats compliance as a separate system invites exactly the kind of gap that regulators and card networks watch for.
How NymCard's infrastructure fits underneath a wallet
A wallet needs something to spend from, and that is where Cards comes in. NymCard issues tokenized and virtual cards on native processing, with real-time controls, so a wallet's backing credential can be provisioned digitally rather than waiting on a physical card, and every authorisation runs against a live balance instead of a periodic sync.
Getting funds in and out falls to Money Movement, which moves funds across cards, accounts, wallets, and cash networks, with connectivity into Visa Direct, Mastercard Cross-Border, Western Union, and MoneyGram. A wallet built on it can support more than one way to fund and more than one way to pay out as new use cases get added, including cross-border transfers and FX.
Financial Crime is what keeps the first two safe: identity verification and onboarding, fraud monitoring, sanctions screening, and 3D Secure authentication, applied inside the same authorisation path as the transaction rather than as a separate review afterward.
What connects the three is nCore, NymCard's full-stack payments infrastructure platform, built on a real-time data core. Cards, Money Movement, and Financial Crime all read from and write to that same data core, so a wallet built on nCore is not three vendors stitched together behind one app icon. It runs as one platform, with a single view of the customer that every capability shares, underneath a wallet the non-bank designs and brands as its own.
What to ask before choosing wallet infrastructure
A non-bank evaluating infrastructure for a wallet is really asking whether the plumbing underneath the app will hold up once real money and real regulatory scrutiny arrive. A few questions surface the answer faster than a feature list does.
Does the balance update the moment a transaction happens, or does it catch up later on a batch cycle? A wallet that shows a stale number is a wallet that will eventually show a customer money they do not have.
Can a spendable credential be issued digitally and tokenized, so a customer can fund the wallet and start spending the same day, rather than waiting on a card to arrive by mail?
How many ways can money move in and out of the wallet, and how easily can a new one be added once the company wants to support a new funding source or payout method?
Are fraud monitoring, sanctions screening, and identity verification part of the same decision as the transaction, or a separate system the company has to bolt on and reconcile itself?
Does every capability read from the same view of the customer, or does the wallet risk becoming exactly what it was built to avoid: another set of disconnected systems that happen to share a brand?
The company that answers those questions honestly before it launches spends far less time reconciling systems after it does.