Softwr

APIs · head to head

Tink vs Volt

Tink logo

Tink

APIs

European open banking platform for account data and payment initiation

From
On request
Rated
-
Full reviewWebsite
Volt logo

Volt

APIs

Account-to-account pay by bank across Europe, the UK, Brazil and Australia

From
On request
Rated
-
Full reviewWebsite

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.; Volt account-to-account payments carry no chargeback mechanism, so consumers lose scheme dispute protection and merchants lose a familiar framework for handling claims.
  • They diverge on capability: Tink covers Account data access, Volt covers Pay by bank.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Tink and Volt actually diverge.

Attributes where Tink and Volt differ
AttributeTinkVolt
PlatformsAPI, WebWeb, 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 Volt

  • Pay by bank
  • Circuit Breaker
  • Virtual IBANs
  • Payouts and refunds
  • Verify
  • Stablecoin checkout

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 Volt
  • A merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value basketsnot Volt
  • A fintech that does not hold its own PSD2 licence and needs to operate under an authorised provider passported across the EEAnot Volt
  • A bank building an account aggregation view of a customer external accounts without negotiating with each institution individuallynot Volt

Volt

  • A travel seller with high average order values paying percentage card fees it wants to replace with flat transfer feesnot Tink
  • An iGaming operator needing fast deposits and payouts where card acceptance is restrictednot Tink
  • A merchant with heavy card fraud that wants strongly authenticated irreversible paymentsnot Tink
  • A marketplace verifying seller bank accounts before paying outnot 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.

Volt

  • Account-to-account payments carry no chargeback mechanism, so consumers lose scheme dispute protection and merchants lose a familiar framework for handling claims.
  • Refunds are outbound payments rather than reversals, which changes treasury handling and means a refund can fail for reasons a card refund never would.
  • Conversion is lower than a stored card because the shopper must complete a bank authentication journey, and drop-off varies significantly by bank.
  • Core pay by bank pricing is per transaction but refunds, payouts, virtual IBANs, Verify and fraud tooling are billed separately, so the real cost is a stack of line items.
  • Bank API availability and quality vary across markets, and an outage at a major bank removes a slice of your checkout with no fallback unless you keep cards live.

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

Volt

On request
  • Volt pay by bank$undefined/year
    • Per successful transaction fee, quoted by volume and market
    • Separate charges for refunds, payouts, virtual IBANs and Verify
    • Circuit Breaker fraud tooling priced as an add-on

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

  • You need pay by bank.
  • You work on Web, REST API.
  • You also want circuit breaker.
Volt review

Questions people ask

Is Tink or Volt better?
Neither clearly leads. Tink starts at On request and Volt at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Tink or Volt?
Tink starts at On request and Volt at On request.
Does Tink or Volt run on more platforms?
Tink runs on API, Web. Volt 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 Volt is typically brought in for.
What can Tink do that Volt cannot?
Tink covers Account data access, Payment initiation, EEA passporting, Categorisation. Volt covers Pay by bank, Circuit Breaker, Virtual IBANs, Payouts and refunds.

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.

Volt: Are there chargebacks?

No. Bank transfers are irrevocable, so disputes are handled commercially between merchant and customer, not through a card scheme.

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.

Volt: How do refunds work?

As a separate outbound payment initiated by the merchant, which Volt charges for separately from the inbound transaction.

Tink: Does Tink cover the United States?

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

Volt: Which markets are covered?

Europe and the UK, plus Brazil and Australia, on a single API integration.

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.

Share

Related pages

More on Tink

More on Volt

Keep looking

Other head to heads