Is Tink or Weavr better?

Neither clearly leads. Tink 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, Tink or Weavr?

Tink starts at On request and Weavr at On request.

Does Tink or Weavr run on more platforms?

Tink runs on API, Web. Weavr runs on Web, REST API.

What is Tink best used for?

Tink is most often used for a european lender that needs verified income and expense data from a borrower bank account across several eea markets under one licence, a merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value baskets, a fintech that does not hold its own psd2 licence and needs to operate under an authorised provider passported across the eea, a bank building an account aggregation view of a customer external accounts without negotiating with each institution individually. Of those, a european lender that needs verified income and expense data from a borrower bank account across several eea markets under one licence and a merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value baskets are not what Weavr is typically brought in for.

What can Tink do that Weavr cannot?

Tink covers Account data access, Payment initiation, EEA passporting, Categorisation. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.

APIs · head to head

Tink vs Weavr

Tink

APIs

European open banking platform for account data and payment initiation

From: On request
Rated: -

Full review Website

Weavr

APIs

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

From: On request
Rated: -

Full review Website

The short version

Each has a real cost: Tink visa owns Tink, and pay-by-bank exists to move payments off card rails, so the roadmap and pricing of the product you are using to reduce interchange are set by the company that earns the interchange.; 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: Tink covers Account data access, 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 Tink and Weavr actually diverge.

Attributes where Tink and Weavr differ
Attribute	Tink	Weavr
Platforms	API, Web	Web, 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 Tink

Account data access
Payment initiation
EEA passporting
Categorisation
Account verification
Risk and affordability signals
Variable recurring payments support
Consent management

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.

Tink

A European lender that needs verified income and expense data from a borrower bank account across several EEA markets under one licencenot Weavr
A merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value basketsnot Weavr
A fintech that does not hold its own PSD2 licence and needs to operate under an authorised provider passported across the EEAnot Weavr
A bank building an account aggregation view of a customer external accounts without negotiating with each institution individuallynot Weavr

Weavr

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

Where each one falls short

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

Tink

Visa owns Tink, and pay-by-bank exists to move payments off card rails, so the roadmap and pricing of the product you are using to reduce interchange are set by the company that earns the interchange.
Coverage is Europe only, so a product serving both European and United States users runs a second aggregator with a different data model and a separate contract.
PSD2 connection quality varies sharply by bank, and headline connection counts hide wide differences in success rate, consent lifetime and re-authentication frequency that determine what users actually experience.
Consent under PSD2 expires and requires periodic re-authentication, so any product depending on continuous data access has a recurring user friction it cannot design away, and drop-off at re-consent is a real product problem.
Pricing is quoted with data access and payment initiation priced separately, and there is no published rate card, so small merchants cannot compare pay-by-bank economics against card acceptance without a sales process.

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

Tink

On request

Tink Platform$undefined/year
- Priced by product, market and volume
- Data access and payment initiation priced separately
- Annual commitments typical for enterprise agreements

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

You need account data access.
You work on API, Web.
You also want payment initiation.

Tink 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 Tink or Weavr better?: Neither clearly leads. Tink 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, Tink or Weavr?: Tink starts at On request and Weavr at On request.
Does Tink or Weavr run on more platforms?: Tink runs on API, Web. Weavr runs on Web, REST API.
What is Tink best used for?: Tink is most often used for a european lender that needs verified income and expense data from a borrower bank account across several eea markets under one licence, a merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value baskets, a fintech that does not hold its own psd2 licence and needs to operate under an authorised provider passported across the eea, a bank building an account aggregation view of a customer external accounts without negotiating with each institution individually. Of those, a european lender that needs verified income and expense data from a borrower bank account across several eea markets under one licence and a merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value baskets are not what Weavr is typically brought in for.
What can Tink do that Weavr cannot?: Tink covers Account data access, Payment initiation, EEA passporting, Categorisation. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.

Answered from the vendors’ own pages

Tink: Who owns Tink?

Visa, since 2022. That is directly relevant if you are adopting pay-by-bank specifically to reduce card costs.

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.

Tink: Do I need my own PSD2 licence?

No. Tink holds AIS and PIS licences from the Swedish FSA passported across the EEA, and customers can operate as its agent rather than obtaining their own authorisation.

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.

Tink: Does Tink cover the United States?

No. It is a European platform. US coverage requires a separate provider.

Weavr: How does Weavr make money?

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

Tink: How reliable are the bank connections?

It varies by institution far more than the headline count of roughly 6,000 connections suggests. Ask for per market and per bank success rates and consent lifetimes for the banks your users actually hold accounts with.

Tink vs Weavr

Tink

Weavr

The short version

Where they differ

What each one covers

Only in Tink

Only in Weavr

What people use each for

Tink

Weavr

Where each one falls short

Tink

Weavr

Pricing, plan by plan

Tink

Weavr

Which should you pick?

Choose Tink if

Choose Weavr if

Questions people ask

Answered from the vendors’ own pages

Related pages

More on Tink

More on Weavr

Keep looking

Other head to heads