Softwr

APIs · head to head

Griffin vs Rutter

Griffin logo

Griffin

APIs

UK banking-as-a-service from a company that holds its own full banking licence

From
£100/month
Rated
-
Rutter logo

Rutter

APIs

One API across accounting, commerce, payments and advertising platforms

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.; Rutter a unified schema exposes only the fields common across platforms, so the platform-specific detail underwriting models want usually requires passthrough calls and per-platform code, which is the work the unified API was bought to avoid.
  • They diverge on capability: Griffin covers Bank accounts by API, Rutter covers Accounting and ERP.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Griffin and Rutter actually diverge.

Attributes where Griffin and Rutter differ
AttributeGriffinRutter
Starting price£100/monthOn request
Pricing modelPer month with usage drawdownquote
PlatformsWeb, REST APIWeb, API

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 Rutter

  • Accounting and ERP
  • Commerce data
  • Payments data
  • Advertising data
  • Write operations
  • Passthrough requests
  • Observability tooling
  • Sandbox

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 Rutter
  • A lender wanting UK accounts and payment rails without becoming a bank itselfnot Rutter
  • A fintech burned by sponsor bank instability that wants the deposit holder and the API provider to be the same entitynot Rutter
  • A platform needing sub-account ledgering for pooled client funds with a clean audit trailnot Rutter

Rutter

  • A revenue-based lender that must pull a merchant's sales, payouts and general ledger before pricing a facilitynot Griffin
  • A spend management product that needs to push bills and journal entries back into whichever accounting system its customer runsnot Griffin
  • A B2B payments platform reconciling invoices across customers using four different ERPsnot Griffin
  • An insurance or benefits provider that needs verified business financials without asking the customer to upload PDFsnot 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.

Rutter

  • A unified schema exposes only the fields common across platforms, so the platform-specific detail underwriting models want usually requires passthrough calls and per-platform code, which is the work the unified API was bought to avoid.
  • Write operations into accounting systems are where these products break, because each system validates differently, and a rejected journal entry surfaces as a support ticket against you rather than against the ERP.
  • No pricing is published beyond a sandbox trial, so cost cannot be compared against alternatives without a sales process, and pricing tends to scale with connected accounts.
  • QuickBooks Desktop and other on-premises systems require a local connector or hosted agent, which introduces installation steps your customers must complete and support burden you inherit.
  • Sync freshness varies by platform and by customer authorisation state, so a product promising near real-time figures will find some connections update far less often than the marketing implies.

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

Rutter

On request
  • Starter$undefined/month
    • Thirty day sandbox trial
    • Test integrations with QuickBooks, Xero, FreshBooks and Zoho Books
    • Documentation and workflow guides
  • Full Access$undefined/year
    • Production access across all platforms
    • Includes NetSuite, QuickBooks Desktop and Sage Intacct
    • Write operations and passthrough

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 Rutter if

  • You need accounting and erp.
  • You work on Web, API.
  • You also want commerce data.

Questions people ask

Is Griffin or Rutter better?
Neither clearly leads. Griffin starts at £100/month and Rutter at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Griffin or Rutter?
Griffin starts at £100/month and Rutter at On request.
Does Griffin or Rutter run on more platforms?
Griffin runs on Web, REST API. Rutter runs on Web, API.
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 Rutter is typically brought in for.
What can Griffin do that Rutter cannot?
Griffin covers Bank accounts by API, UK payment rails, Integrated ledger, Automated onboarding. Rutter covers Accounting and ERP, Commerce data, Payments data, Advertising data.

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.

Rutter: Does Rutter support QuickBooks Desktop?

Yes, which distinguishes it from unified APIs that only cover cloud accounting, and matters because many small businesses still run it.

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.

Rutter: Can Rutter write data back?

Yes. Invoices, bills and journal entries can be pushed into supported accounting systems, not only read.

Griffin: Does it cover Europe?

No. Griffin is a UK bank serving UK accounts and UK payment rails.

Rutter: Is there a free tier?

There is a thirty day sandbox trial with test data. Production access requires a paid plan with quoted pricing.

Rutter: What if the unified model lacks a field I need?

Rutter supports passthrough requests to the underlying platform API, though using them reintroduces platform-specific code.

Share

Related pages

Other head to heads