In-House BNPL: What it really costs in 2026
At first, building in-house BNPL makes sense: control over credit logic, no third-party dependency, the ability to move at your own pace. But the total cost of that control – engineering maintenance, fraud exposure, dispute handling, compliance overhead – rarely surfaces cleanly on the P&L. CCD2 has made that accounting unavoidable. This guide breaks down what running in-house BNPL actually costs, and what your options look like now.
The build decision was right. The question now is what it’s costing to run.
Most in-house operators have a clear view of what it costs to build. Fewer have a clean view of what it costs to maintain – and the two numbers are rarely the same.
Engineering maintenance pulls resources away from the product roadmap. Fraud models degrade without continuous investment, disputes accumulate, and by November 2026, in-house operators in Europe must meet a set of CCD2 requirements that aren’t configuration changes – they’re engineering projects. No single breaking point; just a gradual realisation that full ownership has a cost that’s been absorbed rather than measured.
What this guide covers
- The true ongoing cost of in-house BNPL, broken down as concrete cost lines most merchants haven’t fully accounted for
- What CCD2 specifically requires – and why the gap between current setup and compliant setup is usually larger than expected
- How one merchant made the transition, and what changed operationally when a partner absorbed the complexity
- Your options going forward, and how to think about which one fits your setup
The full picture, before you decide
here isn’t one right answer. Some merchants will find that a full transition to a managed partner makes sense; others will conclude that adding a managed layer on top of their existing stack is the smarter first move. Both are valid, and both are covered here. Download the paper for the complete breakdown, including what CCD2 requires, what the numbers look like in practice, and what it looks like when the operational complexity lands somewhere else.
Download the case study now
Fill in the form and you'll have the insights in your inbox.
Frequently Asked Questions
More than most merchants expect, once they account for it properly. Beyond the upfront build, ongoing costs include engineering maintenance, credit assessment and fraud prevention, dispute handling, and settlement reconciliation – spread across teams, rarely visible as a single line item.
By November 2026, in-house operators in Germany and the Netherlands must implement updated payment flows, Strong Customer Authentication, revised credit disclosures, advertising restrictions, late payment cost caps, and age verification. For most operators, that means new engineering work and legal sign-off, not a simple configuration update.
It depends on how far your current setup is from compliant, which is often further than expected. The work typically spans engineering, legal, and product, and competes directly with roadmap priorities.
It depends on where your current setup is creating value, and where it’s creating cost. Some merchants will conclude a full transition makes sense; others will find a managed layer on top of their existing setup is the smarter first move.
The main risks are credit and fraud exposure carried entirely by the merchant, dispute handling overhead that scales with volume, and compliance risk under CCD2. A managed provider takes these on directly.