Bank-Grade Is a Liability Posture, Not a Tech Stack
The happy path is solved on both sides. The exception path is what you are actually buying — and there is a way to test it before you sign.
Subscriber · Sign in to listen to the audio briefing
Audio briefings are available to subscribers. Sign in with the email you used to subscribe — we'll send a one-time code.
The happy path stopped being a differentiator
The bank-grade versus fintech-grade argument in issuing processing is almost always run as a technology question. Legacy against modern. Batch against real time. Green screen against API. My read is that the framing has been wrong the whole time, and it gets more wrong every quarter, because both sides have spent five years acquiring each other's features.
Watch the demos and you see why. Every platform authorizes inside sixty milliseconds. Every platform has a sandbox, a webhook that fires on cue, a card that provisions to a wallet while the prospect watches. The happy path was solved a long time ago. It is not a differentiator and it has not been one for years.
Who absorbs the break
What separates the two grades is the exception path — the fraction of a percent where something is wrong. Decisioning is unreachable and something has to stand in. The clearing file lands and does not match what was authorized. A cardholder disputes, and a regulatory clock starts running whether or not anyone on your side has noticed. None of that appears in a demo, because demos are built on the case where nothing breaks.
So the honest distinction is not architectural. It is about who absorbs the break. Bank-grade means the platform has taken the exception onto its own book of obligations: it reconciles to the network clearing file to the penny, it produces entries an examiner can trace without an interpreter, and it carries the dispute lifecycle inside the regulatory clock rather than handing you a queue. Fintech-grade means you get excellent primitives and the exception belongs to you. Neither is a defect. They are two liability postures sold at two prices, and the gap between the prices is roughly the cost of the posture.
The mandate-release test
Which leaves the practical problem of telling them apart during diligence, when everyone in the room is answering yes to every question. Here is the test I would use, and it is one nobody prepares for.
Twice a year the networks release mandates. Ask each platform: across the last four releases, how many required a change on your side? Not whether they are compliant — every vendor says compliant. Ask for the count of client-side changes. Zero means the platform owns the compliance calendar and absorbed the work before you heard about it. Any other number means the compliance calendar is sitting on your roadmap, and it will keep sitting there every April and every October for the life of the programme. That is a permanent engineering line nobody budgets for at signature, and it compounds quietly against a business case built on launch speed.
Two clocks, two teams
The second thing worth naming is that the advantages arrive on different clocks. Fintech-grade pays out in month three, in time to launch. Bank-grade pays out in year three, when volume is real, disputes are a department rather than a person, mandate load is cumulative, and the first examiner has questions. The decision is usually made by the team that experiences the first payoff and settled by the team that lives with the second. That is a selection problem, not a technology problem, and no amount of platform evaluation fixes it if the wrong people are in the room.
Stop asking which grade
The labels themselves are decaying. Modern platforms have shipped reconciliation, dispute automation and audit trails that would have passed for bank-grade a few years ago. Incumbents have shipped credible APIs. Stop asking which grade a platform is, because the answer is increasingly both and the word does no work.
Ask where the exception sits. Then get the answer in writing, because that is the part of the contract you will actually be living in.
Franco Di Pietro
The Payments Corner
30+ years across payments, fintech, banking, and financial infrastructure. Operator-level perspectives on the systems that move money.
The author is employed at Euronet Worldwide, a card issuer processing company. The author may own securities or assets referenced across The Payments Corner ecosystem. Content is provided for informational and editorial purposes only and should not be considered investment advice.
Related Insights
BNPL Isn't a Checkout Feature. It's Credit.
BNPL is often discussed as a checkout experience or a UX innovation. But increasingly, the market is beginning to price it for what it fundamentally is. Credit. Yesterday's market activity, paired with New York's proposed regulatory framework, reinforced that distinction clearly.
At Some Point, BNPL Stops Being a Product Discussion and Becomes a Processing Discussion
Whether a transaction can be posted as deferred, split into installments, or follow distinct billing logic isn't determined at checkout. It's determined by what the processing platform can express after authorization. BNPL capabilities themselves are increasingly table stakes — the real differentiator is execution.
BNPL Is Often a Platform Decision Long Before It's a UX Decision
BNPL often gets discussed primarily as a consumer experience decision. In reality, it's frequently a platform and execution decision long before it becomes a user-experience discussion. Three different operating models — merchant-funded, issuer-funded, third-party — each place very different demands on the infrastructure stack.