APIs · head to head
Griffin vs Increase

Griffin
APIs
UK banking-as-a-service from a company that holds its own full banking licence
- From
- £100/month
- Rated
- -

Increase
APIs
Direct banking API for ACH, wires, real-time payments, accounts and cards
- From
- On request
- Rated
- -
The short version
- Each has a real cost: Griffin platform banking carries a one-off onboarding fee from 15,000 pounds and a 3,500 pound monthly minimum, which prices out early-stage companies entirely.; Increase the published per transaction rates exclude a monthly platform fee that Increase states varies by use case, so the transparent price page cannot produce a total cost and the material part of the deal is still negotiated privately.
- They diverge on capability: Griffin covers Bank accounts by API, Increase covers ACH origination and receipt.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Griffin and Increase actually diverge.
Identical on both: free tier (No), user rating (Not yet rated), category (APIs).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Griffin
- Bank accounts by API
- UK payment rails
- Integrated ledger
- Automated onboarding
- Debit cards
- Interest on balances
Only in Increase
- ACH origination and receipt
- Domestic wires
- Real-time payments
- Bank accounts
- Cards
- Cheques
- Sandbox and simulations
- Audit and reconciliation data
What people use each for
The jobs each tool is most often brought in to do.
Griffin
- A wealth platform that must hold client money in a licensed bank rather than an EMI safeguarding accountnot Increase
- A lender wanting UK accounts and payment rails without becoming a bank itselfnot Increase
- A fintech burned by sponsor bank instability that wants the deposit holder and the API provider to be the same entitynot Increase
- A platform needing sub-account ledgering for pooled client funds with a clean audit trailnot Increase
Increase
- A payroll or treasury product that needs to originate same-day ACH and wires under its own control rather than through a payment processornot Griffin
- A marketplace that must hold seller balances in ledgered accounts with real account and routing numbersnot Griffin
- A fintech that wants FedNow and RTP payouts so recipients are paid outside banking hoursnot Griffin
- An engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logicnot Griffin
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Griffin
- Platform banking carries a one-off onboarding fee from 15,000 pounds and a 3,500 pound monthly minimum, which prices out early-stage companies entirely.
- It is UK-only, so a business with European or US operations needs a second banking provider and a second integration for those entities.
- It is a young bank with a small balance sheet relative to incumbents, and enterprise counterparties still ask hard questions about concentration risk.
- Holding a banking licence means Griffin applies bank-grade due diligence to its own clients, so onboarding is slower and more selective than an EMI-based provider.
- Feature breadth is narrower than long-established providers, particularly in card programme management and in payment types beyond core UK rails.
Increase
- The published per transaction rates exclude a monthly platform fee that Increase states varies by use case, so the transparent price page cannot produce a total cost and the material part of the deal is still negotiated privately.
- Free allowances are deliberately small at ten account numbers and five physical cards, so any programme issuing accounts or cards at volume moves to quoted pricing almost immediately.
- Banking is provided through partner banks, so programme approval, compliance obligations and the ability to launch at all depend on a bank relationship you do not control, and post-Synapse bank risk appetite has tightened considerably.
- The API deliberately exposes payment rail mechanics rather than smoothing them, which is correct engineering but means a team without payments expertise will build reconciliation and return handling wrongly and only discover it when funds go astray.
- Coverage is United States only, so a company with international payout needs runs a second provider and reconciles two ledgers, and the single API argument disappears at the first cross border customer.
Pricing, plan by plan
Griffin
£100/month- Business Banking$100/month
- From 100 pounds per month
- Interest or commission from around 1.75 percent AER variable
- Operational accounts and UK payment rails
- Platform Banking$3500/month
- One-off onboarding fee from 15,000 pounds
- Minimum monthly spend of 3,500 pounds, drawn down by usage
- Higher committed tiers at 5,000 and 10,000 pounds with discounts
- Enterprise$undefined/month
- Custom pricing
- Bespoke account structures and volumes
- Negotiated interest or commission share
Increase
On request- Increase Platform$undefined/month
- Monthly fee quoted by use case and not published
- Next-day ACH origination listed at 0.50 US dollars per transaction
- Same-day ACH origination listed at 2.00 per transaction
Which should you pick?
Choose Griffin if
- You need bank accounts by api.
- You work on Web, REST API.
- You also want uk payment rails.
Choose Increase if
- You need ach origination and receipt.
- You work on API, Web.
- You also want domestic wires.
Questions people ask
- Is Griffin or Increase better?
- Neither clearly leads. Griffin starts at £100/month and Increase at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Griffin or Increase?
- Griffin starts at £100/month and Increase at On request.
- Does Griffin or Increase run on more platforms?
- Griffin runs on Web, REST API. Increase runs on API, Web.
- What is Griffin best used for?
- Griffin is most often used for a wealth platform that must hold client money in a licensed bank rather than an emi safeguarding account, a lender wanting uk accounts and payment rails without becoming a bank itself, a fintech burned by sponsor bank instability that wants the deposit holder and the api provider to be the same entity, a platform needing sub-account ledgering for pooled client funds with a clean audit trail. Of those, a wealth platform that must hold client money in a licensed bank rather than an emi safeguarding account and a lender wanting uk accounts and payment rails without becoming a bank itself are not what Increase is typically brought in for.
- What can Griffin do that Increase cannot?
- Griffin covers Bank accounts by API, UK payment rails, Integrated ledger, Automated onboarding. Increase covers ACH origination and receipt, Domestic wires, Real-time payments, Bank accounts.
Answered from the vendors’ own pages
Griffin: Is Griffin actually a bank?
Yes. It received a UK banking licence with restrictions in March 2023 and a full licence in March 2024 after exiting mobilisation.
Increase: Does Increase publish its pricing?
Partly. Per transaction fees for ACH, wires, RTP, FedNow and cards are listed publicly. The monthly platform fee is not, and it is described only as varying by use case.
Griffin: What does it cost?
Business banking from 100 pounds a month; platform banking from a 15,000 pound onboarding fee plus a 3,500 pound monthly minimum drawn down by usage.
Increase: Who holds the deposits?
Partner banks, not Increase itself. That relationship determines your programme approval, your compliance obligations and your risk if the bank changes appetite.
Griffin: Does it cover Europe?
No. Griffin is a UK bank serving UK accounts and UK payment rails.
Increase: Is it international?
No. Increase covers United States rails only, so cross border payouts require a second provider.
Increase: How is it different from a middleware BaaS platform?
It exposes the rails rather than abstracting them, showing real return codes and settlement timing. That suits teams who understand payments and punishes teams who do not.
Related pages
Other head to heads
- Griffin vs Weavr
- Griffin vs Synctera
- Griffin vs 10x Banking
- Griffin vs Skaleet
- Griffin vs Solaris
- Griffin vs Swan
- Griffin vs Treasury Prime
- Griffin vs Unit
- Griffin vs Vodeno
- Griffin vs Fintech Farm
- Griffin vs Astra
- Griffin vs Temenos Transact
- Griffin vs Token.io
- Griffin vs Yapily
- Griffin vs Dwolla
- Griffin vs Sila
- Griffin vs Moov
- Griffin vs Column
- Griffin vs Lithic
- Griffin vs Volt
- Griffin vs TrueLayer
- Griffin vs KeystoneJS
- Griffin vs Kong
- Griffin vs Liveblocks
- Griffin vs Moesif
- Griffin vs Ozone API
- Griffin vs Parse Server
- Increase vs Weavr
- Increase vs Synctera
- Increase vs 10x Banking
- Increase vs Skaleet
- Increase vs Solaris
- Increase vs Swan
- Increase vs Treasury Prime
- Increase vs Unit
- Increase vs Vodeno
- Increase vs Fintech Farm
- Increase vs Astra
- Increase vs Temenos Transact
- Increase vs Token.io
- Increase vs Yapily
- Increase vs Dwolla
- Increase vs Sila
- Increase vs Moov
- Increase vs Column
- Increase vs Lithic
- Increase vs Volt
- Increase vs TrueLayer
- Increase vs KeystoneJS
- Increase vs Kong
- Increase vs Liveblocks
- Increase vs Moesif
- Increase vs Ozone API
- Increase vs Parse Server
