Why Your BNPL AI Approves More Loans But Defaults Keep Climbing

BNPL Risk
Published on
Written byMayank Singh

TL;DR: BNPL AI approval rates climbed from 67% in 2020 to 79% in 2022. Boards and marketing teams celebrated the number. But the same period saw over 60% of originations going to subprime and deep subprime borrowers. And defaults stay invisible for 60-90 days after origination. The approval-default paradox is not a bug. It is a temporal blind spot baked into how BNPL models train, label, and learn.

Key Takeaways: - BNPL defaults are a 60-90 day problem. Models train on Day 0 labels. That gap is a structural mismatch. Retraining on incomplete data makes it worse, not better. - Counteroffer conversion feeds back into the approval model as a success signal. It trains the system to approve thinner files in the exact segments where default risk concentrates. - Survival analysis, delayed feedback loops, decoupled uplift models, and shadow deployments can align growth metrics with real borrower behavior. But only if CTOs treat BNPL risk as a time-series problem, not a classification one.

The Approval Rate Trap: When Growth Metrics Become Risk Signals

Your BNPL model approved 18% more loans last quarter. The default spike won't show up until Day 90. That comes long after your team celebrated, long after your model retrained on clean data, and long after the losses became someone else's quarterly problem.

Approval rate is the most board-friendly KPI in BNPL. It moves up, revenue climbs, growth slides look great. The metric tells you nothing about who you are approving or when those approvals will fail.

According to the CFPB's analysis of BNPL originations, approval rates climbed from 67% in 2020 to 79% in 2022. That 12-point jump came partly from counteroffer mechanisms, meaning modified terms offered to applicants who would otherwise have been rejected.

The same CFPB data shows that over 60% of originations by 2022 went to borrowers in the deep subprime and subprime FICO bands. The growth and the risk concentration are the same story.

The trap: each incremental percentage point of approval concentrates in the cohort that defaults latest. Subprime borrowers carry lower early-cycle delinquency. That looks like model success at Day 30. Their default behavior emerges in the tail.

Compounding exposure adds another layer. The CFPB defines heavy BNPL users as those originating more than one loan per month. This group grew from 18% of borrowers in 2021, and the share kept rising into 2022.

Your approval rate is not a single-loan metric. It is a velocity metric. And your risk model is not accounting for that velocity.

CTOs who report approval rate as a top-line win are reporting a metric that masks exposure, not progress. The same 79% approval rate in 2022 carries different risk than the 79% rate would have in 2020. The composition of who gets approved has shifted toward the segments that fail last.

But here is the uncomfortable question: if your model approves more borrowers and your portfolio grows, why do losses still surprise you three months later?

Why Day 90 Is Where Your Model Goes Blind

The answer lives in the temporal mismatch between how BNPL loans are structured and how they actually fail.

Most BNPL products run on 4-12 week repayment windows. Pay-in-4 models clear in 6 weeks. Longer-tenor products stretch to 12.

The model treats a "good" loan as one repaid on schedule within that window. The label is binary, the signal is clean, the training pipeline is happy.

But real default behavior does not respect the repayment window. A borrower who takes a BNPL loan in Week 1, a second in Week 3, and a third in Week 6 stacks exposure across providers and across your own portfolio. Their first loan may clear on time.

Their third loan, and their ability to repay it, depends on whether the previous two cleared, whether they took on competing debt elsewhere, and whether their cash flow held.

Cascading default across multiple loans often surfaces 60-90 days post-origination. Training labels come from first-cycle repayment status. That underweights stacking behavior.

The signal is incomplete. And it is incomplete in a directional way: the loans that look cleanest at Day 30 often tail into default at Day 75.

This means your retraining cycles operate on partial signal. Every model refresh teaches the system to be more confident in patterns that have not had time to fail. The model gets better at predicting 30-day outcomes. The actual loss materializes at 90.

By the time a Day 90 default shows up, the borrower has often taken 2-3 more loans. Each was approved by a model that still considered them creditworthy.

The loss is not a single event. It is a cascade your model did not see coming. It was trained on data from before the cascade resolved.

The timing problem is bad enough on its own. The way counteroffers interact with your model makes it worse.

The Counteroffer Spiral: How AI Learns to Say Yes Too Often

Counteroffers are the BNPL industry's answer to the rejection problem. A borrower gets declined. The system offers a smaller amount, a shorter tenor, or a higher fee. It converts what would have been a "no" into a "yes" on modified terms.

The business logic is sound. Conversion is revenue. But the model training logic is broken.

From the model's perspective, every counteroffer conversion looks like a successful approval. The borrower did not default in the first cycle. The system wrote the loan. The outcome flag reads "good."

That "good" flag flows back into the training set as a positive example. It reinforces the decision boundary that produced the original rejection.

Over 18-24 months, this feedback loop trains the model to approve thinner files. The rejected-but-converted cohort performed acceptably in the short window the model observed. So the model shifts its decision threshold to include more of those profiles.

The same profile that triggered a counteroffer in 2022 may trigger a straight approval in 2024. The model has learned that this kind of borrower "works."

The 60%+ concentration in subprime and deep subprime originations by 2022 is the direct result of this reinforcement pattern. Counteroffers rewired the model's notion of who is safe to approve. And they did it in the exact segments where late-stage default risk is highest.

Counteroffer economics are real. Conversion is a valid lever. But when counteroffer conversion feeds the same training signal as first-line approval, the model loses the ability to distinguish between two things: "this borrower was approved on standard terms" and "this borrower was approved because we softened the terms."

That distinction is exactly where the risk lives, and most BNPL data architectures stop short of capturing it.

What Your Model Isn't Seeing: Three Data Blind Spots in BNPL Underwriting

Most BNPL risk models operate on a fraction of the data they could use. Industry-leading BNPL architectures draw on rich consumer data signals across behavior, transactions, and merchant context. Many in-house stacks run on narrower feature sets, leaving thin-file segments under-modeled.

Three categories of signal are systematically underused: - Behavioral signals across prior loans. Repayment velocity, time-to-second-loan, merchant category patterns, and seasonality of borrowing all carry predictive weight. They need cross-loan linkage in your data pipeline, meaning tying today's applicant to their full history with you, not just the most recent transaction. Most BNPL data architectures treat each loan as an isolated event, which is backward. - Merchant-level and stock-keeping data. Cart abandonment, return rate, category volatility, and SKU-level purchase patterns provide risk signal that traditional credit data cannot. BNPL providers capture transaction-level and stock-keeping data that traditional bank credit data does not reach. That advantage only matters if the underwriting model actually ingests it. - Cross-provider exposure signals. A borrower taking loans from two or three BNPL providers in the same month is a different risk than a borrower with a single position. The CFPB's heavy-user growth from 18% in 2021 reflects exactly this pattern. Without data sharing or proxy signals, each provider underweights the borrower's true exposure.

The CFPB finding that low-FICO and no-FICO borrowers drove approval growth means your blind spot is concentrated where default risk is highest. The model is least informed about the cohort it is approving most aggressively.

The BNPL problem is not different in kind from other data-integration-heavy risk domains. It is a data integration problem disguised as a modeling problem.

Knowing what data to capture is one thing. Getting the model architecture to use it correctly under BNPL's temporal dynamics is the harder problem.

Rebuilding the Risk Stack: Four Architectural Changes for CTOs

The fix is not a better classifier. It is a different kind of model, trained on a different feedback loop, evaluated on a different timeline.

Four changes actually move the needle: - Replace point-in-time classification with survival analysis. Standard classifiers output a probability of default at a fixed horizon. Survival analysis models estimate time-to-default. That means Day 90 risk is scored at origination rather than discovered three months later. The model learns the shape of the default curve, not just the endpoint. - Build delayed feedback loops. Your training pipeline should wait for full repayment windows to close before updating labels. Accept slower model refresh in exchange for honest signal. Teams that retrain weekly on Day 30 labels are optimizing for a metric that does not exist. - Decouple counteroffer conversion from approval training. Counteroffers should feed a separate uplift model that measures incremental conversion and incremental risk independently. The base approval classifier should not see counteroffer outcomes as positive training examples. When the same signal serves two decisions, the model optimizes for neither. - Run shadow deployments with 90-day evaluation windows. Every model change should run in shadow, scoring real applications but not affecting decisions, for the full default tail before promotion. This catches temporal blind spots before they hit production. It is the equivalent of 200ms loan approvals paired with 4-hour audit windows: speed at the point of decision, patience at the point of evaluation.

What Changes When You Get This Right: From Reactive Underwriting to Predictive Defense

The payoff is not a single metric. It is a reorientation of the entire risk function.

Approval rates stabilize at rational levels. They stop chasing top-line growth that hides in 90-day tail losses. The number stops being a vanity metric and starts being a calibrated decision.

Loss forecasting becomes a leading indicator rather than a quarterly reconciliation exercise. Finance and risk teams work from the same source of truth. The quarterly "where did the losses come from" conversation stops happening.

Counteroffer economics become visible and tunable. You can optimize conversion without inflating default exposure, because the counteroffer signal feeds its own model, not the base approval classifier. The lever stops being a trap.

Long-term model performance holds. Training labels reflect real borrower behavior across full loan lifecycles, not just first-cycle repayment. The model degrades less between retrains. Retraining itself becomes less urgent.

This is what a mature MLOps discipline looks like when applied to risk rather than to generic ML pipelines. It separates systems that age well from those that quietly decay. Once you commit to the rebuild, engineering quality tells you the architecture was right, not just the launch.


Frequently Asked Questions

Q: What is the Day 90 problem in BNPL default prediction?

A: The Day 90 problem refers to BNPL defaults that surface 60-90 days after origination. By then, borrowers have often stacked multiple loans across providers. Training labels from early-cycle repayment miss this signal, so models underestimate the risk they actively approve. The model trains on incomplete data and gets rewarded for being confidently wrong.

Q: How do counteroffers affect BNPL approval rates and default risk?

A: Counteroffers convert rejected applicants into approved loans through modified terms. That conversion feeds back into training data as a success. Over time, it reinforces approval patterns in thin-file and subprime segments. The pattern matches the concentration CFPB documented: 60%+ of originations going to deep subprime and subprime FICO borrowers by 2022. The same mechanism that grows the portfolio also shifts the risk mix.

Q: How often should a BNPL risk model be retrained to catch late defaults?

A: Retraining frequency should align with your longest realistic default tail, typically 90 days, not your release cadence. Faster retraining on incomplete labels reinforces the blind spot. Slower, label-complete retraining produces models that reflect borrower behavior across full loan lifecycles. Speed is not a substitute for honesty in training data.

Q: What alternative data improves BNPL default prediction most?

A: Behavioral signals across prior loans, including repayment velocity, time-to-second-loan, and merchant category patterns, combined with stock-keeping and cart-level data from merchants, tend to outperform traditional credit data in thin-file segments. The gap is largest where BNPL growth is concentrated, which is also where your data advantage compounds fastest.

Q: What model architecture works best for BNPL AI risk?

A: Survival analysis models that estimate time-to-default outperform standard classification for BNPL. They score the risk at origination that would otherwise only surface at Day 90. Pairing survival models with delayed feedback loops and decoupled counteroffer uplift modeling gives the most stable long-term performance. The architecture has to match the temporal structure of how BNPL loans actually fail, not the snapshot classification frameworks designed for first-cycle repayment alone.

About the author

MS
Mayank Singh
Software Developer, Levitation Infotech

Mayank Singh is a software developer at Levitation Infotech, where he builds web and AI-powered applications across the company’s fintech, healthcare, and enterprise projects.

Supercharge Your Success with Our Expertise

Amplify Your Business with Our Expertise. Explore Services Tailored for Your Success.

Get In Touch