16 Apr 2026

Payabli is not a consumer brand. Nobody downloads it, nobody reviews it on Trustpilot, and borrowers will never know it exists. That is precisely why it matters.

The company's model, sitting between banks and software platforms to handle payments, payouts, and underwriting as background infrastructure, is a playbook that UK consumer credit is still catching up with. We talk endlessly about front-end customer experience while underinvesting in the plumbing beneath it. Origination platforms, affordability tools, payment collections: too many lenders and brokers still build this themselves, expensively and slowly, because the embedded infrastructure market here is less mature than in the US.

The Huntington Bank integration is the detail worth paying attention to. A regional bank plugging into a third-party infrastructure layer rather than building in-house is a significant cultural shift. UK banks have historically treated payments and origination infrastructure as something you own, not something you buy. That instinct is expensive and it slows everyone down.

The AI angle in Payabli's next phase is automated underwriting and payables. That combination is interesting because it moves AI from a bolt-on feature into the core decisioning layer. For UK consumer credit specifically, where FCA scrutiny on affordability assessment is only increasing, automating underwriting is not just an efficiency question. It is a governance and auditability question. Any infrastructure provider that embeds AI into credit decisions for UK lenders will need to answer those questions clearly before compliance teams will sign off.

The broader signal here is that financial infrastructure is consolidating around a small number of specialist providers, and the winners are the ones who make integration trivially easy. How many UK credit operations are still running on bespoke systems they built five years ago and can no longer afford to replace?

The interesting thing about Plain is not that it's another Python framework. It's the explicit design choice to make code legible to AI agents, not just human developers.

Django is genuinely brilliant for building loan origination platforms. Convention over configuration gets you to a working credit application journey faster than almost anything else. But those conventions are implicit. They live in the heads of senior engineers and in documentation that an AI coding agent has to infer its way through. Plain's approach, forking Django and making everything typed and explicit, is a direct response to the reality that AI is now writing and reviewing a significant chunk of production code.

For technology leaders in consumer finance, this matters more than in most sectors. We operate under conduct rules that require explainability and auditability. When an AI agent generates a change to your eligibility logic or your affordability calculation, you need to be confident that the change is:

• Traceable to a deliberate decision
• Typed and predictable enough to catch errors before they reach production
• Readable by a compliance engineer, not just the original developer

Implicit magic in a framework makes all three harder.

I'm not suggesting everyone abandon Django tomorrow. The ecosystem, the talent pool, the existing platform investment, none of that disappears because a new framework has better type annotations. But the underlying question Plain raises is worth sitting with: are your engineering choices optimised for a world where humans write all the code, or for the one you're actually in?

The teams I see moving fastest right now are the ones treating AI coding agents as a genuine constraint on their architecture decisions. Plain is one answer to that constraint. The more important shift is recognising the question exists at all.