Softwr

APIs · head to head

Griffin vs Tribe Payments

Griffin logo

Griffin

APIs

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

From
£100/month
Rated
-
Full reviewWebsite
Tribe Payments logo

Tribe Payments

APIs

Combined issuer and acquirer processing platform for fintechs, banks and acquirers

From
On request
Rated
-
Full reviewWebsite

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.; Tribe Payments running both issuing and acquiring through one vendor concentrates operational risk, since a platform fault affects both sides of a client's card business at once rather than just one.
  • They diverge on capability: Griffin covers Bank accounts by API, Tribe Payments covers ISAAC core platform.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Griffin and Tribe Payments actually diverge.

Attributes where Griffin and Tribe Payments differ
AttributeGriffinTribe Payments
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 Tribe Payments

  • ISAAC core platform
  • Issuer processing
  • Acquirer processing
  • Multi-scheme connectivity
  • Open banking module
  • 3D Secure and fraud tooling

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

Tribe Payments

  • A bank or fintech wanting to run both card issuing and merchant acquiring on one processing platformnot Griffin
  • A payment facilitator consolidating separate issuing and acquiring vendor relationships into one contractnot Griffin
  • A company needing multi-scheme processing across Visa, Mastercard and regional networks like UnionPaynot Griffin
  • An Asia-Pacific expansion where Tribe's Singapore office provides regional supportnot 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.

Tribe Payments

  • Running both issuing and acquiring through one vendor concentrates operational risk, since a platform fault affects both sides of a client's card business at once rather than just one.
  • Pricing for either the issuing or acquiring modules is not published, so budgeting requires a sales conversation.
  • With roughly 60-plus customers, it is smaller scale than Visa or Mastercard-owned processing infrastructure, which is a factor for a client prioritising vendor size and track record.
  • Its client base and support depth are concentrated in the UK and continental Europe, and the Asia-Pacific presence via Singapore is comparatively newer and less proven.
  • As with any combined issuing and acquiring platform, a client that only needs one side still evaluates and pays for a vendor built around doing both, which may not be the most specialised option available.

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

Tribe Payments

On request
  • Tribe Payments$undefined/year
    • Pricing not published for issuing or acquiring modules
    • Custom quote required via sales

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.
Griffin review

Choose Tribe Payments if

  • You need isaac core platform.
  • You work on Web, API.
  • You also want issuer processing.
Tribe Payments review

Questions people ask

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

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.

Tribe Payments: Does Tribe do both issuing and acquiring?

Yes, its ISAAC platform supports both, built for issuing in 2019 and acquiring from 2020.

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.

Tribe Payments: How many card schemes does it support?

Visa, Mastercard, Amex, Discover, JCB and UnionPay.

Griffin: Does it cover Europe?

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

Tribe Payments: Where is its customer base concentrated?

The UK and continental Europe, with a newer Singapore office serving Asia-Pacific.

Share

Related pages

More on Griffin

More on Tribe Payments

Keep looking

Other head to heads