APIs · head to head
Dwolla vs Tink
Dwolla
APIs
Account to account payment API for ACH, RTP and FedNow with pay by bank and instant payment routing
- From
- On request
- Rated
- -
Tink
APIs
European open banking platform for account data and payment initiation
- From
- On request
- Rated
- -
The short version
- Each has a real cost: Dwolla nothing is published: there are no per-transaction rates, no platform fee and no minimum on the pricing page, so every buyer negotiates blind and small platforms have no way to sanity check what they are quoted.; 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: Dwolla covers ACH transfers, Tink covers Account data access.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Dwolla and Tink actually diverge.
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 Dwolla
- ACH transfers
- Instant payments
- Rail orchestration
- Bank account verification
- Dwolla Balance
- Webhooks and reconciliation
- Pay by bank
- White label flows
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.
Dwolla
- An insurance or lending platform disbursing funds to customer bank accounts where card payout fees would destroy the marginnot Tink
- A B2B marketplace collecting large invoice payments by bank transfer rather than paying interchange on cardsnot Tink
- A payroll or gig platform that needs to pay workers instantly and wants the rail chosen automatically by receiving bank capabilitynot Tink
- A property management system collecting rent by ACH with verified bank accounts and reliable return handlingnot Tink
Tink
- A European lender that needs verified income and expense data from a borrower bank account across several EEA markets under one licencenot Dwolla
- A merchant offering pay-by-bank at checkout to avoid card acceptance costs on high value basketsnot Dwolla
- A fintech that does not hold its own PSD2 licence and needs to operate under an authorised provider passported across the EEAnot Dwolla
- A bank building an account aggregation view of a customer external accounts without negotiating with each institution individuallynot Dwolla
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Dwolla
- Nothing is published: there are no per-transaction rates, no platform fee and no minimum on the pricing page, so every buyer negotiates blind and small platforms have no way to sanity check what they are quoted.
- It is payments only, with no deposit accounts, card issuing or general ledger, so companies embedding financial products need at least one further vendor and the reconciliation between them.
- Instant payment reach depends on the receiving institution supporting RTP or FedNow, so a meaningful share of payouts still fall back to ACH timing regardless of what the API can do.
- ACH returns and administrative returns remain your operational problem, and platforms new to bank rails routinely underestimate the customer support load that failed debits generate.
- Access to instant rails runs through Dwolla banking partner, which reintroduces a bank dependency into a product that otherwise avoids sponsor bank programme risk.
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
Dwolla
On request- Dwolla Payment API$undefined/year
- Custom pricing built around transaction volume, rails used and integration needs
- No published per-transaction rates or platform fees
- Volume based plans for platforms and enterprises
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 Tink if
- You need account data access.
- You work on API, Web.
- You also want payment initiation.
Questions people ask
- Is Dwolla or Tink better?
- Neither clearly leads. Dwolla 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, Dwolla or Tink?
- Dwolla starts at On request and Tink at On request.
- Does Dwolla or Tink run on more platforms?
- Dwolla runs on Web. Tink runs on API, Web.
- What is Dwolla best used for?
- Dwolla is most often used for an insurance or lending platform disbursing funds to customer bank accounts where card payout fees would destroy the margin, a b2b marketplace collecting large invoice payments by bank transfer rather than paying interchange on cards, a payroll or gig platform that needs to pay workers instantly and wants the rail chosen automatically by receiving bank capability, a property management system collecting rent by ach with verified bank accounts and reliable return handling. Of those, an insurance or lending platform disbursing funds to customer bank accounts where card payout fees would destroy the margin and a b2b marketplace collecting large invoice payments by bank transfer rather than paying interchange on cards are not what Tink is typically brought in for.
- What can Dwolla do that Tink cannot?
- Dwolla covers ACH transfers, Instant payments, Rail orchestration, Bank account verification. Tink covers Account data access, Payment initiation, EEA passporting, Categorisation.
Answered from the vendors’ own pages
Dwolla: What does Dwolla cost?
It does not publish anything. Pricing is custom and built around volume, rails and integration. Establish the monthly platform fee and any minimum before negotiating per-transaction rates.
Tink: Who owns Tink?
Visa, since 2022. That is directly relevant if you are adopting pay-by-bank specifically to reduce card costs.
Dwolla: Does it support instant payments?
Yes, through both the RTP network and the FedNow Service, with automatic selection based on the receiving bank. Where neither is supported, payments fall back to ACH.
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.
Dwolla: Is Dwolla a bank?
No. It is a payments platform that works through banking partners. It does not offer deposit accounts or card issuing.
Tink: Does Tink cover the United States?
No. It is a European platform. US coverage requires a separate provider.
Dwolla: How does bank account verification work?
Either instantly through open banking connections or by micro-deposit verification, which takes a day or two but works where instant linking fails.
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.
Related pages
Other head to heads
- Dwolla vs Moov
- Dwolla vs Increase
- Dwolla vs Method Financial
- Dwolla vs Sila
- Dwolla vs Trustly
- Dwolla vs Volt
- Dwolla vs TrueLayer
- Dwolla vs Yapily
- Dwolla vs Astra
- Dwolla vs Token.io
- Dwolla vs Zimpler
- Dwolla vs Griffin
- Dwolla vs Lithic
- Dwolla vs Stoplight
- Dwolla vs Swan
- Dwolla vs Temenos Transact
- Dwolla vs Enable Banking
- Dwolla vs Yodlee
- Dwolla vs Bud Financial
- Dwolla vs MX Technologies
- Dwolla vs Neonomics
- Dwolla vs Enfuce
- Dwolla vs Salt Edge
- Dwolla vs Skaleet
- Dwolla vs Svix
- Dwolla vs Synctera
- Dwolla vs Treblle
- Dwolla vs Tribe Payments
- Tink vs Moov
- Tink vs Increase
- Tink vs Method Financial
- Tink vs Sila
- Tink vs Trustly
- Tink vs Volt
- Tink vs TrueLayer
- Tink vs Yapily
- Tink vs Astra
- Tink vs Token.io
- Tink vs Zimpler
- Tink vs Griffin
- Tink vs Lithic
- Tink vs Stoplight
- Tink vs Swan
- Tink vs Temenos Transact
- Tink vs Enable Banking
- Tink vs Yodlee
- Tink vs Bud Financial
- Tink vs MX Technologies
- Tink vs Neonomics
- Tink vs Enfuce
- Tink vs Salt Edge
- Tink vs Skaleet
- Tink vs Svix
- Tink vs Synctera
- Tink vs Treblle
- Tink vs Tribe Payments