Softwr

APIs · head to head

Token.io vs Weavr

Token.io logo

Token.io

APIs

Account to account pay by bank infrastructure across the UK and Europe

From
On request
Rated
-
Full reviewWebsite
Weavr logo

Weavr

APIs

Packaged embedded finance for B2B SaaS, with an in-house EU e-money licence

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Token.io account to account payments carry no chargeback scheme, so merchants gain cost savings but consumers lose the dispute protection cards provide, which limits adoption in general retail.; Weavr products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • They diverge on capability: Token.io covers Payment initiation, Weavr covers Plug-and-play products.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Token.io and Weavr actually diverge.

Attributes where Token.io and Weavr differ
AttributeToken.ioWeavr
PlatformsWeb, APIWeb, REST API

Identical on both: starting price (On request), pricing model (quote), 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 Token.io

  • Payment initiation
  • Variable recurring payments
  • Bank network coverage
  • giroAPI membership
  • Payouts and refunds
  • Data and account information
  • Hosted payment pages
  • Reconciliation reporting

Only in Weavr

  • Plug-and-play products
  • Regulated cover
  • Card issuing
  • Multi-currency accounts
  • Identity and onboarding
  • Data insights

What people use each for

The jobs each tool is most often brought in to do.

Token.io

  • A utility or telecom collecting high value bills where card interchange makes acceptance expensivenot Weavr
  • An investment or trading platform funding customer accounts without card chargeback exposurenot Weavr
  • A payment service provider adding pay by bank to its merchant proposition without building bank connectivitynot Weavr
  • A German merchant using giroAPI scheme access for recurring and future dated bank paymentsnot Weavr

Weavr

  • A project management SaaS adding expense cards without hiring a compliance officernot Token.io
  • A marketplace paying out sellers from accounts held inside its own productnot Token.io
  • A procurement platform issuing virtual cards against approved purchase ordersnot Token.io
  • A European SaaS vendor wanting a regulated entity to sit behind its financial featuresnot Token.io

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Token.io

  • Account to account payments carry no chargeback scheme, so merchants gain cost savings but consumers lose the dispute protection cards provide, which limits adoption in general retail.
  • Conversion depends on each bank's own authentication journey, and slow or broken bank redirects cost sales in ways the merchant cannot fix or even always diagnose.
  • Variable recurring payments beyond sweeping are still being rolled out unevenly across banks and markets, so a subscription use case may be supported at one bank and not another.
  • Token.io initiates payments rather than acting as acquirer of record, so merchants still need settlement, safeguarding and reconciliation arrangements elsewhere.
  • Coverage and feature parity vary by country, so a pan European rollout means different capabilities and different bank behaviour in each market rather than one uniform product.

Weavr

  • Products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • Programme economics depend on interchange, and SaaS vendors routinely overestimate how much card volume their customers will actually route through the embedded product.
  • It is a small company with limited headcount supporting a regulated dependency, which is a real concentration risk for a feature your customers rely on.
  • Monthly minimums on card programmes mean a slow-adopting customer base leaves you paying for volume you never reach.
  • European interchange caps hold programme revenue well below what US embedded finance case studies suggest, so imported business cases do not transfer.

Pricing, plan by plan

Token.io

On request
  • Token.io platform$undefined/year
    • Quoted per customer, typically per initiated payment
    • Volume tiers and monthly minimums are common
    • No interchange, so unit cost is usually well below card acceptance

Weavr

On request
  • Weavr embedded finance$undefined/year
    • Platform subscription plus per-account and per-card fees
    • Interchange share negotiated as part of the commercial terms
    • Monthly minimums apply to card programmes

Which should you pick?

Choose Token.io if

  • You need payment initiation.
  • You work on Web, API.
  • You also want variable recurring payments.
Token.io review

Choose Weavr if

  • You need plug-and-play products.
  • You work on Web, REST API.
  • You also want regulated cover.
Weavr review

Questions people ask

Is Token.io or Weavr better?
Neither clearly leads. Token.io starts at On request and Weavr at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Token.io or Weavr?
Token.io starts at On request and Weavr at On request.
Does Token.io or Weavr run on more platforms?
Token.io runs on Web, API. Weavr runs on Web, REST API.
What is Token.io best used for?
Token.io is most often used for a utility or telecom collecting high value bills where card interchange makes acceptance expensive, an investment or trading platform funding customer accounts without card chargeback exposure, a payment service provider adding pay by bank to its merchant proposition without building bank connectivity, a german merchant using giroapi scheme access for recurring and future dated bank payments. Of those, a utility or telecom collecting high value bills where card interchange makes acceptance expensive and an investment or trading platform funding customer accounts without card chargeback exposure are not what Weavr is typically brought in for.
What can Token.io do that Weavr cannot?
Token.io covers Payment initiation, Variable recurring payments, Bank network coverage, giroAPI membership. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.

Answered from the vendors’ own pages

Token.io: Does pay by bank remove card fees?

It removes interchange and scheme fees, so unit cost is normally far below card acceptance, particularly on high value payments.

Weavr: Do I need my own financial licence?

No. Weavr holds an e-money licence, including a Maltese authorisation for the EU, and acts as the regulated entity for the embedded product.

Token.io: What about chargebacks?

There are none. That is the cost saving and the consumer protection gap, which is why it suits bills, top ups and account funding more than retail.

Weavr: How is it different from a banking-as-a-service API?

It sells finished product shapes with compliance built in rather than raw banking primitives, which trades flexibility for a much shorter route to launch.

Token.io: Is Token.io regulated?

Yes, it is an authorised third party provider under UK and European open banking rules, but it initiates payments rather than holding merchant funds as an acquirer.

Weavr: How does Weavr make money?

Platform fees plus per-account and per-card charges, with a negotiated share of card interchange.

Share

Related pages

More on Token.io

More on Weavr

Keep looking

Other head to heads