30 Apr 2026

Kashable's $60 million raise from Goldman Sachs isn't really a story about employer benefits. It's a story about data quality in underwriting, and that should make UK consumer credit leaders uncomfortable.

The core insight is simple: when repayment comes directly from payroll, default risk drops sharply. You know employment status in near real-time. You have visibility into income stability that a credit bureau snapshot can't provide. And crucially, the borrower's relationship with their employer creates a behavioural incentive that no credit agreement on its own replicates. That combination produces better loan performance, which is why Goldman is backing it.

In the UK, we've had Open Banking for years and the promise was exactly this kind of richer, real-time income verification. But most lenders are still using it defensively, to confirm affordability at origination rather than to build a fundamentally different risk model. Kashable's approach goes further by making the employer the distribution channel and the repayment infrastructure simultaneously.

The FCA's consumer duty focus on fair value makes this model interesting from a regulatory angle too. Lower default rates mean lower cost of capital, which should translate to lower APRs. That's a demonstrable fair value story, and it's one that's genuinely hard to tell when your underwriting is still anchored to traditional bureau data.

The barriers to replicating this in the UK are real. Employer adoption takes time, payroll integrations are fragmented, and HR departments don't naturally think of themselves as financial services distributors. But with salary finance models already operating here, the concept has proven traction.

The question for UK credit leaders is whether Open Banking ever actually delivered the underwriting revolution it promised, or whether we bolted it onto legacy models and called it innovation.

Mercury getting conditional OCC approval is the most important fintech story of the month, and almost nobody in the UK is paying attention to it.

The received wisdom in UK fintech has long been that a banking licence is a burden. Capital requirements, regulatory scrutiny, compliance overhead. The smarter play, the argument goes, is to stay lean and ride on partner bank rails. Mercury is making the opposite bet, and the logic is worth taking seriously.

When you own your charter, you own your margin. Every basis point that currently flows to a Banking-as-a-Service partner stays in house. More importantly, you own your risk decisions. Partner bank arrangements come with someone else's credit appetite, someone else's compliance culture, and someone else's ability to pull the plug when their own regulatory situation gets complicated. We saw exactly that dynamic play out in the US over the last two years when several BaaS banks faced enforcement actions and their fintech clients had nowhere to go.

The parallel for UK consumer finance is direct. A number of credit brokers and embedded finance businesses have built significant customer bases on top of third-party infrastructure. That works until it doesn't. The operational resilience rules coming from the FCA and PRA are partly aimed at exactly this concentration risk.

Two things make the Mercury move genuinely significant rather than just American fintech news:

• Lending is now in scope. A chartered Mercury can underwrite directly, which changes the unit economics of the whole business.
• The timing matters. The OCC has historically been cautious with fintech charters. Approval under this administration signals a regulatory environment that is prepared to let fintechs compete with banks on equal infrastructure.

The question UK technology leaders should be sitting with is whether the capital cost of a banking licence is still the right frame. The real cost might be continuing to build customer relationships on infrastructure you don't control.

Customers Bank embedding OpenAI across lending, deposits, and payments sounds like a headline win. Custom models, internal data, strict governance standards. The press release writes itself.

But here's what I'd be asking if I were sitting on the board: what does 'strict governance standards' actually mean when your core banking workflows depend on a model you didn't build, can't fully audit, and whose underlying architecture changes on OpenAI's roadmap, not yours?

This is the tension that matters for UK consumer finance leaders right now. The FCA's Consumer Duty and the incoming AI obligations being shaped through the government's pro-innovation framework both point in the same direction: explainability and accountability sit with the firm, not the model provider. You can outsource the compute. You cannot outsource the regulatory responsibility.

The Customers Bank announcement is a US commercial bank, so the direct regulatory comparison doesn't hold perfectly. But the operational model being described, where bankers shift away from manual tasks toward client-facing work because AI handles workflows, is exactly what mid-sized UK lenders are exploring right now. Our own originations teams have similar conversations every quarter.

The part worth thinking hard about is the model training on internal data. That's where it gets genuinely interesting and genuinely risky in the same breath. Internal data carries your historical credit decisions, your existing biases, your legacy pricing logic. Train a model on that without rigorous pre-processing and you've industrialised your past mistakes at scale.

Two things need to be true simultaneously for this kind of collaboration to work:

• The governance framework has to be built before deployment, not retrofitted after an incident
• Model performance needs continuous monitoring against real outcomes, not just point-in-time validation

Neither of those is technically difficult. Both are organisationally hard, because they require technology, risk, and compliance to actually work together rather than hand off documents to each other.

The question for any UK consumer credit firm watching this announcement isn't whether to pursue AI automation in originations. That decision is already made by competitive pressure alone. The question is whether your governance infrastructure is being built at the same pace as your model ambitions.

A free book from AWS, written by enterprise leaders across data strategy, ML, and agentic AI. It sounds useful. And it probably is, if you already know what problem you're solving.

That's the tension I keep running into with this kind of content. The chapters on data products and classical ML are genuinely valuable territory for anyone building credit decisioning infrastructure. Getting your data products right, treating data as something you deliberately design rather than accidentally accumulate, is foundational work that most consumer finance firms still haven't done properly. We talk about AI readiness while sitting on top of data pipelines held together with manual fixes and undocumented logic.

But the jump to agentic AI is where I'd push back on the sequencing these books typically imply.

Agentic AI, systems that plan, act, and iterate without a human approving each step, carries a different class of risk in regulated consumer credit than in, say, logistics or retail. The FCA's Consumer Duty requires firms to act in the best interests of customers. An autonomous agent making or influencing credit decisions, or handling complaints, or managing collections contact, is not a neutral efficiency tool. It's a regulated activity, and the accountability question doesn't get easier just because AWS has packaged the infrastructure nicely.

Two things matter here for UK leaders specifically:

• Data strategy isn't a precursor to AI, it's the same project. If your data governance isn't audit-ready, you're not ready to automate decisions at scale.
• Agentic AI needs a compliance architecture before it needs a technical one. The 'who is responsible when it goes wrong' question should be answered before deployment, not after the FCA writes to you.

I'd read the book. The perspectives from practitioners are more grounded than most vendor content. But the frame is still very much 'here's what's possible.' The harder question for consumer finance is what's permissible, and who owns it when the agent gets it wrong.

Shopify quietly did something that should make every fintech engineering team pay attention. They took a large general-purpose model, decided it was the wrong tool, and fine-tuned a smaller open-source model on their own domain data. The result was better accuracy, faster responses, and lower running costs. That combination rarely happens when you swap one approach for another. Getting all three is a signal worth taking seriously.

The consumer credit world is full of workflow problems that look exactly like this. Decisioning logic, case management rules, collections triggers, affordability reassessment flows. These are all domain-specific processes with their own vocabulary, edge cases, and internal logic that a general model has never been trained on. When teams experiment with AI-assisted workflow building and find the results frustrating or unreliable, the instinct is to blame the technology. The more likely explanation is that they are using the wrong model for the job.

Fine-tuning gets treated as the advanced option, something you do after you have exhausted the easier routes. Shopify's experience suggests the opposite framing. For a specific, well-defined domain with enough internal examples, fine-tuning on a smaller model should be the first serious option you evaluate, not the fallback.

There is a practical constraint worth naming. Consumer credit generates sensitive data, and using that data to train models introduces regulatory and data governance questions that Shopify does not face in the same way. The FCA's expectations around model risk, explainability, and customer outcomes apply here. But this is a solvable problem with the right data handling approach, not a reason to avoid the technique entirely.

The broader point is about how UK financial services organisations think about AI tooling. The default is to buy access to the largest available model and treat prompt engineering as the primary lever. Shopify's approach is a reminder that specificity usually beats scale when the domain is narrow enough. Consumer credit workflow automation is about as narrow and well-defined a domain as you will find. The question is whether engineering teams have enough internal example data, and the organisational appetite, to take this seriously.

The race to build finance-specific foundation models is not a research story. It's a decisioning story, and it will determine which lenders and brokers remain competitive in credit risk over the next decade.

Revolut and Nubank have transaction datasets that most UK lenders can only dream about. When you train a foundation model on hundreds of millions of behavioural signals across credit, fraud, and payments simultaneously, you're not just improving a single model's accuracy. You're building a proprietary view of financial behaviour that compounds over time. The gap between institutions with that data and those without it widens every quarter.

For UK consumer credit specifically, this matters more than the general fintech commentary suggests. Open Banking promised to democratise transaction data access, and it has done that partially. But there's a difference between accessing someone's last 90 days of bank statements via an API and training a foundation model on billions of transactions across diverse customer populations over years. The former is a point-in-time input. The latter is institutional knowledge encoded into weights.

What this means practically

• Mid-tier lenders and brokers cannot out-data the Revoluts of the world. The window to try closed a few years ago.
• The interesting play for everyone else is fine-tuning open or third-party foundation models on proprietary data, not building from scratch.
• Tooling accessibility, which the article rightly flags, means execution quality becomes the differentiator. That's an organisational capability question, not a technology question.

The FCA will eventually have views on foundation models in credit decisioning, particularly around explainability under the Consumer Duty framework. A single architecture consolidating multiple ML systems sounds efficient until a regulator asks you to explain a declined application and your answer involves attention mechanisms across 47 input features.

The real question for UK credit leaders isn't whether to invest in this direction. It's whether you're building the internal capability to use these models responsibly, or whether you're about to buy a black box from a vendor and hope for the best.