Griffin stablecoin services: $20M Series B—UK onchain ⚡12 min read2,366 words

Griffin stablecoin services: $20M Series B—UK onchain ⚡

Griffin stablecoin services just raised a $20M Series B in the UK—see plans for crypto banking regulation, cards, and onchain cross-border payments.

Griffin stablecoin servicesGriffin Series BUK stablecoin infrastructureonchain cross-border paymentscrypto banking regulation
Griffin stablecoin services: $20M Series B—UK onchain ⚡

Griffin's $20M Raise Puts Stablecoin Infrastructure on the Roadmap

A bank raising venture capital to build stablecoin services doesn't, by itself, prove that businesses are ready to swap out normal payments for blockchain-based rails. The real question is what the bank plans to offer - and whether it can plug those services into the systems and accounts companies already use.

UK-based digital bank Griffin has raised $20 million in a Series B round led by Octagon Partners, valuing the company at more than $100 million. Griffin says it will use the money to expand into card issuance, stablecoin reserve services, and onchain cross-border payments. It already provides banking infrastructure to more than 80 companies, reaching more than 300,000 retail and business customers through those partners. Uber is one example, using Griffin to provide bank accounts to UK drivers.

That puts Griffin at the overlap of regulated banking and crypto infrastructure. Still, the announcement leaves key operational questions unanswered: what exactly the reserve services will cover, which stablecoins or networks it may support, and how the products fit the rules that apply to each activity. This article sticks to what Griffin has said - then flags what still needs to be demonstrated, including what the raise could mean for its partners and the wider market.

What did Griffin raise, and what is the funding for?

Griffin raised $20 million in a Series B led by Octagon Partners. The round values the UK digital bank at more than $100 million, according to the announcement. Griffin says the funding will support expansion into card issuance and stablecoin services, including reserve services and onchain cross-border payments.

The card plans are aimed at companies that want to offer branded debit cards to retail or corporate customers through Griffin's platform. Credit cards may come later, but Griffin described them as a next step. That distinction matters: debit and credit work under different operating models and risk rules. Debit typically draws on available funds, while credit introduces lending, underwriting, and credit-loss risk.

Griffin's current setup provides a useful baseline for what "infrastructure" looks like today. The company says its banking platform serves more than 300,000 retail and business customers through more than 80 companies. It's a partner-led model: Griffin supplies the infrastructure, and partners deliver products to their own customers. Uber is one example - it uses Griffin to provide bank accounts to drivers in the UK.

Griffin received its UK banking license in March 2024. That helps explain why Griffin is positioned as a banking infrastructure provider, but a banking license isn't a blanket green light for every product it might build next. The permissions, controls, and counterparties required for cards or stablecoin-related services depend on what those products actually do.

Griffin also reported that recurring revenue at its September fiscal year-end was 3.2 times the prior year, based on unaudited accounts. Octagon managing partner Paraag Davé said he expects Griffin's annual recurring revenue to exceed £10 million soon. The first figure is Griffin's own growth comparison; the second is an investor's expectation. Neither number, by itself, answers whether the business is profitable, how well it retains customers, or what the new stablecoin and card services will cost to run.

So, for Griffin, this raise is both growth capital and a test of execution. It can pay for product development and the operational work needed to support new services. The commercial case will hinge on whether those plans translate into products customers actually adopt - while keeping the reliability you'd expect from a bank.

Why would a digital bank build stablecoin infrastructure?

The strategic logic here isn't that every company wants to become a crypto business. Many firms just need to move money across products, payment providers, and national borders. Stablecoins and blockchain settlement may offer a different way to handle some of those flows, but businesses usually still need a dependable bridge between digital assets and conventional finance before they can use that approach at scale.

A bank or banking infrastructure provider may be able to supply parts of that bridge - accounts, payment operations, customer onboarding, compliance processes, and connections to other financial institutions. What Griffin will provide isn't fully spelled out yet. The announcement points to expanding stablecoin reserve services and adding onchain cross-border payments. It doesn't say Griffin will issue a stablecoin itself, or run every part of the transaction chain.

That distinction is important. In many stablecoin setups, an issuer creates and redeems tokens. Other parties may handle custody, payments, reserve administration, or access to banking services. Those roles can overlap, but they aren't interchangeable. If a business is evaluating a provider, it needs clarity on who controls funds, who is responsible for redemption, and what happens when a payment is delayed or a counterparty disappears.

For a platform company, the practical appeal is often integration. A business may want to add payment capability through an existing infrastructure relationship rather than stitching together separate providers for accounts, cards, and settlement. One technical and operational relationship can cut coordination costs - and it can also concentrate risk. If one provider becomes a critical dependency, outages or service changes can affect a bigger portion of the product.

That trade-off shows up in Griffin's partner model too. Serving customers through more than 80 companies gives Griffin a path to reach businesses and consumers without relying only on a direct-to-consumer brand. But partner growth doesn't automatically mean Griffin controls the end-user experience, or that every partner will use every future service. Adoption has to be measured product by product.

There's also a straightforward commercial reason to extend the platform. Cards and payment services can deepen relationships with existing partners, potentially making the infrastructure more valuable and broadening what partners can offer. That's a plausible growth strategy - but it isn't guaranteed. It only works if the products solve a real operational problem at a competitive cost and are reliable enough to be used routinely.

What could Griffin's stablecoin and payment services involve?

Griffin has pointed to two related areas: stablecoin reserve services and onchain cross-border payments. The announcement doesn't define the exact products, so it's safest to treat these as directions rather than assume a specific technical or legal structure.

Reserve services are not the same as issuing a stablecoin

A stablecoin is built to maintain a relatively stable value, often against a fiat currency. That stability depends on how the token is backed, how reserves are managed, and whether holders can redeem the token under defined conditions. In principle, a reserve service could support parts of that model. In practice, though, the announcement doesn't say whether Griffin would hold, administer, safeguard, or otherwise support reserves - or even which stablecoin(s) and customer groups it might be tied to.

Those details aren't minor. A potential customer would need to know what assets are involved, where they sit, who has legal control, how reserves are reported, and what redemption arrangements apply. It would also need to separate the obligations of a service provider from those of the stablecoin issuer. Without that information, "reserve services" reads more like a market direction than a complete product description.

Onchain payments still need dependable off-chain operations

An onchain cross-border payment uses a blockchain to record or settle a transfer. That changes how value moves between parties, but it doesn't eliminate the surrounding work: converting currencies, validating transaction parties, meeting compliance requirements, handling errors, and tying the transfer back to a company's accounting and customer support systems.

For businesses, the comparison isn't simply "blockchain" versus "bank transfer." It's the total cost and performance of one payment route versus another - fees, settlement time, availability, liquidity, reconciliation effort, and what happens when something goes wrong. A transfer that settles quickly on-chain can still be a bad fit if recipients can't access funds easily or if a business has to maintain separate processes for each corridor.

A banking infrastructure provider can help make those workflows usable for companies that don't want to manage every component themselves. The value comes from clear service boundaries and reliable operations - not from putting a payment onchain for its own sake.

Cards may provide a familiar route to distribution

Branded debit cards could give Griffin's partners a familiar way to offer access to accounts and spending. They can also bridge a digital financial product into everyday retail payments. But a card isn't automatically tied to a stablecoin, and Griffin hasn't said its planned cards will spend stablecoins directly.

Keeping these product areas separate until the details are clear helps avoid a common mistake: assuming adjacent plans already form one integrated offering. Griffin has described cards and stablecoin services as areas for expansion. Customers and partners will need the product documentation to understand whether they connect - and how.

What will determine whether the expansion succeeds?

The funding and valuation get attention, but they don't answer the operational questions. For partners deciding whether to build on Griffin's new services, the test is whether the products are authorized for their intended use, dependable in production, and economically sensible.

Regulatory scope must match the actual product

Griffin's UK banking license matters for its banking activities. It doesn't, by itself, settle every regulatory question around stablecoin reserves, digital-asset transfers, or card issuance. The requirements depend on the product's structure, the parties involved, the assets handled, and where customers operate.

A partner should ask which entity provides each piece of the service and what permissions or arrangements support it. It should also understand where responsibility sits for customer due diligence, transaction monitoring, safeguarding or custody, complaints handling, and redemptions, as applicable. These are product design questions as much as legal ones - unclear ownership can create gaps when something goes wrong or when customers need help.

Reliability and partner dependency matter

Financial products are judged by what happens on a regular Tuesday, not just by their architecture. Partners need clarity on service availability, support processes, incident communication, and reconciliation procedures. If the service depends on multiple banks, payment networks, blockchain networks, or vendors, partners need to know how failures are handled across those dependencies.

Taking more services from a single provider can simplify integration. The trade-off is concentration risk. A sensible rollout plan identifies critical dependencies, clarifies how data and funds are accessed, and lays out what a migration would require if the relationship changes. Integrated infrastructure isn't automatically good or bad - it just has to be used responsibly.

Growth figures need operating context

Griffin's recurring revenue growing to 3.2 times the prior-year level suggests momentum, but it's based on unaudited accounts and doesn't show the underlying revenue amount. Octagon's expectation of more than £10 million in annual recurring revenue is forward-looking as well. Neither figure tells readers how much of growth comes from specific products, how expensive expansion will be, or whether customers will stick around.

The next signals that will matter are concrete: which services launch, who uses them, what transaction volumes they support, and whether Griffin can keep service quality as usage grows. For card issuance, adoption and actual usage matter more than the existence of a program. For stablecoin services, supported roles, reserves, redemption mechanics, and the payment corridors will matter more than a broad label.

For business buyers, a practical evaluation checklist is:

  • Confirm the exact service and the legal entity providing it.
  • Map the movement and control of customer funds at each step.
  • Check supported currencies, networks, payment corridors and redemption terms.
  • Review fees, reconciliation requirements, service levels and incident procedures.
  • Identify critical third-party dependencies and an exit or continuity plan.

That checklist applies to any provider entering regulated payments. It's especially useful when a company blends established banking infrastructure with newer blockchain-based services, because the operational boundaries can get overlooked.

Conclusion

Griffin's $20 million raise is a bet that companies will want banking infrastructure that can extend into cards and selected blockchain-based payment services. Its existing partner network and UK banking license give it a starting point, and its reported revenue growth suggests there's commercial momentum. But that doesn't guarantee the new products will get real adoption.

The details that matter are still ahead: what Griffin's reserve services actually do, how its onchain payments handle the full transaction lifecycle, and which partners are using the products in production. For businesses, the right response isn't to dismiss the plans as crypto branding - or to assume blockchain settlement alone solves cross-border payments. Look closely at service boundaries, controls, costs, and failure modes. That's where the real upside - or the real risk - will show up.

Frequently Asked Questions

Griffin is a UK-based digital bank and banking infrastructure provider. It says its platform serves more than 300,000 retail and business customers through more than 80 companies. Uber uses Griffin to provide bank accounts to drivers in the UK.
Griffin raised $20 million in a Series B round led by Octagon Partners. The financing valued the company at more than $100 million. Griffin said the funds would support expansion into card issuance and stablecoin-related services.
The announcement does not say that Griffin plans to issue a stablecoin. It says the bank plans to expand its stablecoin reserve services and add onchain cross-border payments. The specific roles, assets and products involved have not been detailed.
Not necessarily. A banking license does not automatically establish that every distinct payment or stablecoin activity is covered. The relevant permissions and requirements depend on the product, its structure and the jurisdictions involved. Partners should assess the specific service rather than infer coverage from the bank’s license alone.

Related articles