It's all linked: to launch a card you need an account, to open an account you need KYC
It’s all linked: to launch a card you need an account, to open an account you need KYC
Every week I get a version of the same message: “We want to launch a debit card. How fast can we go live?”
It’s a fair question. It’s also the wrong one to open with, and the gap between those two things is the most expensive lesson in fintech. So let me walk you through what “a debit card” actually is, not to put you off, but because the founders who launch well are the ones who scoped the real project from day one.
Walk the chain backwards
Start with the tap.
A customer puts your card against a terminal. For that to work, the terminal’s acquirer asks the card scheme, the scheme asks your card processor, and your processor asks one question: does this customer have the money?
Answered against what, exactly? Not a bank account with their name on it, surprisingly that’s not how card programmes typically work. It’s answered against a balance on a ledger. Your ledger, or your provider’s. Which means before you have a card, you have an account: a ledger entry that knows, in real time, how much money this specific customer holds.
One step further back.
An account holding customer money isn’t a database row, it’s a regulated thing. The money has to physically sit somewhere and that’s normally safeguarded at a credit institution under an e-money licence. If you don’t hold that licence you’re operating under someone else’s, a sponsoring EMI whose regulatory permissions cover your product. A key thing to note: their licence, their rules.
One more step back.
That sponsor cannot let money into an account until they know whose money it is. So before the account, there’s KYC that needs to be performed: identity verification, screening, risk scoring. And here’s the part almost everyone assumes incorrectly: your KYC setup isn’t calibrated to your risk appetite, it's calibrated to your sponsor’s. They’re the regulated entity; their appetite is your ceiling.
So the chain, forwards this time:
KYC decides who gets in → the account holds the money on a ledger → the money sits safeguarded at a bank under an EMI’s licence → the card spends against the ledger balance → settlement moves real money day(s) after the tap.
Break any link and everything upstream stops working. There is no card without the account. No account without KYC. No KYC without a sponsor whose appetite you understand.
It’s all linked.
Now count the counterparties
Here's that same chain translated into commercial reality.
You'll typically need a sponsoring EMI, a safeguarding bank, a card processor, a BIN sponsor, KYC and AML providers, Open Banking capability, card manufacturing, and a handful of other specialist partners. Some relationships overlap, some are bundled together, but every one exists somewhere in your stack—and every one has its own commercial negotiation, onboarding process, integration work, and potential failure mode.
Suddenly, "launching a debit card" doesn't look like one project anymore.
“A debit card” is not one project. It’s many, wearing a trench coat.
Where founders find this out
Almost nobody discovers this on day one. They discover it after weeks of speaking to vendors across the ecosystem.
Founders often spend months stitching this together one vendor call at a time. You start with the card processor because the card is the product. They ask who your BIN sponsor is. The BIN sponsor asks about your compliance model. Your KYC provider asks how onboarding should be configured. Every answer depends on a conversation you haven't had yet.
Every call teaches you something you hadn't considered, but no call gives you the whole picture. That's not because anyone is being difficult. Every vendor knows their own piece exceptionally well. They sell their piece exceptionally well too. They quite reasonably assume someone else is helping you connect the dots.
Nobody is.
Instead, you're left trying to assemble a jigsaw where every piece depends on another. The sponsor wants to understand your flow of funds. Your flow of funds depends on your banking partner. Your banking partner depends on your regulatory model. Your regulatory model depends on your sponsor. There isn't a neat sequence. That's why founders spend months feeling busy without feeling like they're moving.
The decisions made earliest, your account structure, safeguarding model and KYC configuration, are also the hardest to unwind later. Unfortunately, they're often made almost by accident, buried inside conversations about something else entirely.
Get those decisions right and you save months. Get them wrong and you'll often find yourself renegotiating contracts, rebuilding integrations, and revisiting compliance approvals you thought were already behind you.
The honest question
None of this is an argument against launching. Plenty of products have shipped through exactly this chain, and the infrastructure for doing it has never been better. It’s an argument for scoping honestly before you commit a roadmap to it.
The hardest part of building a fintech isn't integrating the technology. It's discovering the dependencies you didn't know existed.
So, honestly: are you ready to take on that project? Not just the card but the whole chain. The KYC configuration conversation with a sponsor. The account structure decision you can’t cheaply reverse. The safeguarding setup. The reconciliation that runs every day. And then, finally, the card.
If the answer is yes, the rest of this series is for you: over the next few months I’m dissecting each link, KYC and monitoring, accounts, FX, cards and tokenisation, ledgers, safeguarding plus the mistakes we’ve watched real programmes make, so you don’t repeat them.
Every fintech eventually builds the same map. Most build it one mistake at a time. We built it once, then turned it into infrastructure. That's what Integrated Finance really is - the context and orchestration layer that connects every moving part behind it.
If you're planning a launch and want to sanity-check your route, drop me a message. Even if we never work together, you'll, hopefully, leave with a clearer map than you started with.