Why the next wave of fintech infrastructure looks nothing like the last one

For a decade, "Banking-as-a-Service" has been the industry's favourite phrase and one of its most misleading promises. The pitch deck always opens the same way: integrate our API, embed banking into your product, unlock a new revenue line. By the time a platform team finishes reading the implementation guide, the picture is less inspiring — a six-month engineering sprint, an integration fee in the tens of thousands, monthly platform minimums that kick in whether you transact or not, and a compliance overhead that only an existing financial institution can comfortably absorb.

That isn't embedded banking. It's a procurement exercise dressed up as a product.

We started Gemba because we were tired of telling potential partners "yes, embedded finance is the future" and then walking them through a contract that read like a punishment. The version we wanted to ship — the version that actually deserves to be called embedded — needed to clear a higher bar. It had to be live in minutes, not quarters. It had to require zero engineering effort to start. And it had to cost nothing until our partners themselves were earning.

That product now exists. Here's what it does, what it doesn't, and why we think it changes the math for any platform that touches money.

7 minutes from sign-up to a working bank

The headline claim sounds like marketing until you see the timer running. From the moment a partner creates an account on www.ge.mba, the median time to a fully branded, fully functional web banking portal is around seven minutes. There is no development sprint. There is no integration backlog. There are no engineers in the room.

What happens in those seven minutes is straightforward. A partner uploads their logo, selects their colour palette, chooses the domain their customers will see, and confirms which products they want exposed — accounts, IBANs, payments, cards, payouts. The portal renders. Sandbox credentials arrive. The partner's customers can be onboarded that afternoon.

If a developer is in the room, the same setup unlocks our full API surface. But the deliberate point is that one is not required. The product team, the operations lead, or the founder can stand the whole thing up themselves.

The features under the surface

The speed only matters because the substance is real. What partners switch on in those seven minutes is the same regulated banking stack that, until recently, required a multi-year licence application to access.

On the accounts side, partners can issue dedicated UK account numbers and multi-currency IBANs across more than twelve currencies, including GBP, EUR, USD, CAD, and CHF. Virtual IBANs are unlimited — useful for accounting firms reconciling client funds, marketplaces segregating seller balances, and umbrella companies splitting workers' payroll into clean, individually addressable strings.

On the payments side, every meaningful UK and European rail is live from day one: Faster Payments, BACS, CHAPS, SEPA, SEPA Instant, SWIFT for international wires, and Direct Debit for collections. Where the rail supports instant settlement, payments clear in seconds, not days.

For partners moving money at scale, our bulk payout engine processes up to 3,000 payments per minute. Payroll providers, marketplace platforms, and gig-economy operators run their full disbursement cycle in a single API call rather than queuing thousands of individual transfers.

The capability we are proudest of, and the one most often underestimated, is account-to-card instant cross-border payout. A partner can push funds directly from a Gemba account to any Visa or Mastercard anywhere in the world, in seconds. No correspondent banking chain. No two-day SWIFT delay. No screenshot from a beneficiary asking where their money is. For platforms serving freelancers, contractors, suppliers, or claimants in countries with weak banking infrastructure, this single feature is often the deciding factor in choosing Gemba over a legacy provider.

Card-side, partners can issue branded physical and virtual Visa or Mastercard corporate cards to their own customers. Cards can be programmable — single-use, time-bound, capped to a specific merchant — for partners building procurement, expense, or treasury products on top of the platform.

The whole experience sits inside a white-label web banking portal that adapts to the partner's brand, with an open-source mobile front-end and Open Banking API endpoints rolling out through 2026 for partners that want deeper customisation.

The compliance question, answered

The conversation we have with every prospective partner eventually arrives at the same question: who carries the licence?

The answer is that we do. Gemba is an FCA Authorised Payment Institution — FRN 804853 — and we sit on the regulated side of every transaction that flows through the platform. That means we own the KYC, KYB, AML, transaction monitoring, sanctions screening, and safeguarding obligations. We sit across the regulatory perimeter so our partners don't have to.

For a platform that wants to add banking without building a compliance team, hiring a Money Laundering Reporting Officer, or applying for its own licence, the structural difference is enormous. The rule-of-thumb cost of running your own EMI application in the UK is £1.2 million to £2 million in year-one investment, plus 12 to 24 months of organisational distraction. With Gemba, that line item disappears from the business case.

Pricing that reverses the usual incentives

The commercial model is the part of Gemba that most often makes a procurement team re-read the contract.

There is no setup fee. There is no integration fee. There is no monthly platform fee. Partners pay nothing until they begin moving money, and even then, the model is built to align our incentives with theirs.

Partners earn 20% of our base transaction fees on every payment we process for them. On top of that, partners can set their own custom markup — pricing the service to their own customers however they choose — and keep 70% of that markup. Most BaaS providers treat their partners as a cost centre to be optimised. We treat them as a revenue partner whose growth we are paid to accelerate.

For introducers, agencies, and consultants who bring partners onto the platform, we pay a 5% commission on our net retained revenue from those partners — recurring, not one-off.

Who this is for

The platforms that benefit most from Gemba are the ones drowning in operational friction that banking should have solved a decade ago. Accounting firms reconciling client money across hundreds of micro-accounts. Law firms moving completion funds across borders under time pressure. Payroll and umbrella companies disbursing thousands of payments on the same day. PE-backed consolidators running fragmented branch networks where cash is trapped at the local level. AI-native rollups acquiring legacy service businesses and modernising them with embedded finance. Vertical SaaS platforms that already own the customer relationship and now want to own the financial layer too.

The common thread isn't industry. It's the gap between how fast these platforms move and how slowly banking moves around them. Gemba closes that gap by being the regulated infrastructure they were going to have to build, hire, and license themselves — without the wait, the licence application, or the seven-figure overhead.

If any of that sounds like your business, you don't need a meeting to find out. You need seven minutes.

Start at www.ge.mba. No card. No call. No catch.