Most fintech founders know compliance matters. Fewer know what it looks like in week one, or what it costs when it shows up late.
We asked industry leaders a simple question: what does building compliance in from day one actually look like for an early-stage fintech, and what happens when founders leave it too late? We wanted tactical answers, not checklists.
Their replies point to one idea. The danger is rarely a missing tool. It is missing history.
The cost of catching up
The fines tell the story. In October 2024, the UK’s Financial Conduct Authority fined Starling Bank about £29 million. Its customer base grew from roughly 43,000 in 2017 to 3.6 million in 2023, but its financial crime controls did not keep up. For years, its sanctions screening checked customers against only a fraction of the full list.
Monzo was fined about £21 million for similar failings. The regulator said it signed up more than 34,000 high-risk customers while under restrictions. In the US, Block paid $80 million to 48 state regulators and another $40 million to New York’s financial regulator over Cash App’s anti-money laundering program. Robinhood’s crypto arm paid $30 million in 2022.
None of these companies ignored compliance. Their controls simply did not grow as fast as the business.
Start with the rules you operate under
Before any code ships, a fintech needs to know whose rules it is playing by. Will you hold your own licenses, or work through a partner bank? Either way, you will need a program to check who your customers are, screen them against sanctions lists, and watch for suspicious activity.
Someone must own that program by name. That person can be part-time, but the seat cannot be empty.
This is the part founders most often push to “later.” It is also the part regulators look at first.
Build it in, don’t write it up
Svetlana Burninova sees the same mistake from the engineering side.
At YPA Finance we run bank-grade security on a multilingual personal-finance app.
You can’t retrofit security later. In fintech, trust isn’t a marketing slogan, it’s architecture. Secure cloud architecture, encryption, access controls, and compliance alignment have to be engineered from the beginning. Most early-stage fintechs don’t ignore compliance. They mistake paperwork for posture.
Svetlana Burninova, Co-Founder & CTO, YPA Finance
Her point is that good security is a set of early design choices, not a document written the week before an audit. She is specific about what those choices are.
“Compliance from day one” doesn’t mean being SOC 2-ready in month two. It means making five engineering choices in your first week that you won’t have to undo later:
Svetlana Burninova
- One IAM identity per service. Each service gets its own credentials.
- Secrets live in a secret manager like Secret Manager or Vault, not in env vars or .env files.
- Structured, append-only audit logs from your first commit. console.log doesn’t qualify.
- Zero standing production access. Break-glass with full logging.
- Infrastructure in version control. If a change isn’t in a PR, it didn’t happen.
These choices line up closely with AWS and NIST security guidance. The logic is simple. If your systems record who did what, and when, from the start, the evidence builds itself. Nobody has to reconstruct it later.
Paperwork is not the same as proof
David LoPresti comes at the problem from outside fintech, which is exactly why his view is useful. Any business that sells into regulated buyers runs into the same wall.
I’ll answer from the founder-operator seat, not as a fintech specialist. My niche is ADA and digital accessibility, but the sequencing problem is the same shape across any regulated B2B category.
Building it in from day one is less about hiring a compliance officer at seed and more about deciding, before you ship, what evidence you’ll need to produce 18 months from now. Concretely: a decision log, versioned policies, and an approval trail, even when it’s just two founders in a Slack channel. Outsource the specialist interpretation (fractional counsel, a RegTech vendor for the workflow); keep ownership of the evidence trail in-house. The inflection point is your first enterprise or bank partner deal: that’s when procurement asks for two years of history you don’t have.
David LoPresti, Founder, ADA Compliance Professionals
Two parts of his answer stand out. First, a small team does not need a big compliance department to start. It needs the habit of writing decisions down and keeping every version. Second, you can hire outside help to interpret the rules, but you cannot outsource the record. That stays with you.
How far back buyers look varies. A SOC 2 Type II report, which many banks and enterprise customers ask for, covers three to twelve months of evidence. US anti-money laundering rules require firms to keep records for five years. Either way, the clock starts when your controls do, not when a buyer asks.
What “too late” looks like
For most startups, the bill does not arrive as a fine. It arrives as a hard question in a meeting that matters.
What “too late” looks like in practice: six months in, the founder can’t answer “describe your audit trail” in a diligence call. The fix is a 6 to 10 week rewrite of IAM, secrets, and logging, at exactly the moment they need to be shipping product. I’ve watched that cost a fundraise quarter.
Svetlana Burninova
Partner banks feel the same pressure, and they pass it down. In 2024, the Federal Reserve barred Evolve Bank & Trust from taking on new fintech partners without approval. When the middleware firm Synapse collapsed that same year, more than 100,000 users lost access to their money. Records of who owned what did not match, and the shortfall was estimated at $65 million to $95 million.
The lesson for founders is blunt. Your partner’s problems become yours, and a bank that cannot see clean records will not keep the relationship.
The founders who called us in a panic weren’t non-compliant today. They were non-compliant 18 months ago, and now that history is the problem. You can fix a control in a week. You cannot retroactively create the paper trail that proves the control existed when it mattered.
David LoPresti
Where to start
The advice from the leaders we spoke with fits on one short list. Map the rules you operate under before you build. Name a compliance owner, even a part-time one. Make the core engineering choices in your first week. Write down every decision and keep every policy version. Start your evidence clock early, because no one can wind it back.
The timing matters. On September 11, 2026, US banking agencies proposed new guidance on how banks manage their fintech partners. Comments are due November 16. Whatever the final rules say, the direction is clear. Regulators and banks want proof that controls work, not documents that say they exist.
The framing I keep coming back to: you don’t get extra credit for being secure. You simply get destroyed if you aren’t. Compliance from day one means your security model survives SOC 2 prep without a rewrite. The cost of catching up is measured in features you can’t ship that quarter.
Svetlana Burninova
Building compliance in from day one is not about spending more early. It is about making choices that leave a trail. Leave the trail until later, and you pay for it in fines, lost partners and features you never shipped.
Fintechbits covers payments, banking and fintech developments for readers in the US and UK. This article is for information only and is not financial advice. Views in quotes are those of the contributors.



