Softwr

APIs · head to head

Increase vs Tink

Increase logo

Increase

APIs

Direct banking API for ACH, wires, real-time payments, accounts and cards

From
On request
Rated
-
Full reviewWebsite
Tink logo

Tink

APIs

European open banking platform for account data and payment initiation

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Increase the published per transaction rates exclude a monthly platform fee that Increase states varies by use case, so the transparent price page cannot produce a total cost and the material part of the deal is still negotiated privately.; 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.
  • They diverge on capability: Increase covers ACH origination and receipt, Tink covers Account data access.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Increase and Tink actually diverge.

Attributes where Increase and Tink differ
AttributeIncreaseTink

Identical on both: starting price (On request), pricing model (quote), free tier (No), platforms (API, Web), 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 Increase

  • ACH origination and receipt
  • Domestic wires
  • Real-time payments
  • Bank accounts
  • Cards
  • Cheques
  • Sandbox and simulations
  • Audit and reconciliation data

Only in Tink

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

What people use each for

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

Increase

  • A payroll or treasury product that needs to originate same-day ACH and wires under its own control rather than through a payment processornot Tink
  • A marketplace that must hold seller balances in ledgered accounts with real account and routing numbersnot Tink
  • A fintech that wants FedNow and RTP payouts so recipients are paid outside banking hoursnot Tink
  • An engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logicnot Tink

Tink

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

Where each one falls short

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

Increase

  • The published per transaction rates exclude a monthly platform fee that Increase states varies by use case, so the transparent price page cannot produce a total cost and the material part of the deal is still negotiated privately.
  • Free allowances are deliberately small at ten account numbers and five physical cards, so any programme issuing accounts or cards at volume moves to quoted pricing almost immediately.
  • Banking is provided through partner banks, so programme approval, compliance obligations and the ability to launch at all depend on a bank relationship you do not control, and post-Synapse bank risk appetite has tightened considerably.
  • The API deliberately exposes payment rail mechanics rather than smoothing them, which is correct engineering but means a team without payments expertise will build reconciliation and return handling wrongly and only discover it when funds go astray.
  • Coverage is United States only, so a company with international payout needs runs a second provider and reconciles two ledgers, and the single API argument disappears at the first cross border customer.

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.

Pricing, plan by plan

Increase

On request
  • Increase Platform$undefined/month
    • Monthly fee quoted by use case and not published
    • Next-day ACH origination listed at 0.50 US dollars per transaction
    • Same-day ACH origination listed at 2.00 per transaction

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

Which should you pick?

Choose Increase if

  • You need ach origination and receipt.
  • You work on API, Web.
  • You also want domestic wires.
Increase review

Choose Tink if

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

Questions people ask

Is Increase or Tink better?
Neither clearly leads. Increase starts at On request and Tink at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Increase or Tink?
Increase starts at On request and Tink at On request.
Does Increase or Tink run on more platforms?
Both run on API, Web, so platform support will not decide this one for you.
What is Increase best used for?
Increase is most often used for a payroll or treasury product that needs to originate same-day ach and wires under its own control rather than through a payment processor, a marketplace that must hold seller balances in ledgered accounts with real account and routing numbers, a fintech that wants fednow and rtp payouts so recipients are paid outside banking hours, an engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logic. Of those, a payroll or treasury product that needs to originate same-day ach and wires under its own control rather than through a payment processor and a marketplace that must hold seller balances in ledgered accounts with real account and routing numbers are not what Tink is typically brought in for.
What can Increase do that Tink cannot?
Increase covers ACH origination and receipt, Domestic wires, Real-time payments, Bank accounts. Tink covers Account data access, Payment initiation, EEA passporting, Categorisation.

Answered from the vendors’ own pages

Increase: Does Increase publish its pricing?

Partly. Per transaction fees for ACH, wires, RTP, FedNow and cards are listed publicly. The monthly platform fee is not, and it is described only as varying by use case.

Tink: Who owns Tink?

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

Increase: Who holds the deposits?

Partner banks, not Increase itself. That relationship determines your programme approval, your compliance obligations and your risk if the bank changes appetite.

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.

Increase: Is it international?

No. Increase covers United States rails only, so cross border payouts require a second provider.

Tink: Does Tink cover the United States?

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

Increase: How is it different from a middleware BaaS platform?

It exposes the rails rather than abstracting them, showing real return codes and settlement timing. That suits teams who understand payments and punishes teams who do not.

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 Increase

More on Tink

Keep looking

Other head to heads