APIs · head to head
Increase vs Trustly

Increase
APIs
Direct banking API for ACH, wires, real-time payments, accounts and cards
- From
- On request
- Rated
- -

Trustly
APIs
Pay-by-bank payments network, majority-owned by private equity firm Nordic Capital
- From
- On request
- Rated
- -
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.; Trustly it is majority-owned by Nordic Capital, a private equity firm, so its long-term roadmap is ultimately oriented toward an eventual sale or IPO rather than indefinite independent operation.
- They diverge on capability: Increase covers ACH origination and receipt, Trustly covers Pay by bank checkout.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Increase and Trustly 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 Increase
- ACH origination and receipt
- Domestic wires
- Real-time payments
- Bank accounts
- Cards
- Cheques
- Sandbox and simulations
- Audit and reconciliation data
Only in Trustly
- Pay by bank checkout
- Instant refunds
- Verified payouts
- Multi-market bank connectivity
- Merchant dashboard and reconciliation
- Fraud and risk tooling
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 Trustly
- A marketplace that must hold seller balances in ledgered accounts with real account and routing numbersnot Trustly
- A fintech that wants FedNow and RTP payouts so recipients are paid outside banking hoursnot Trustly
- An engineering team that needs the underlying return codes and settlement timing visible in order to build correct reconciliation and retry logicnot Trustly
Trustly
- An e-commerce merchant wanting a lower-cost alternative or complement to card payment acceptancenot Increase
- A gaming or gambling operator needing verified, instant payouts to players' bank accountsnot Increase
- A merchant wanting instant refunds processed directly to a customer's bank account rather than card reversal delaysnot Increase
- A business in a market with strong open banking adoption wanting pay-by-bank as a checkout optionnot 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.
Trustly
- It is majority-owned by Nordic Capital, a private equity firm, so its long-term roadmap is ultimately oriented toward an eventual sale or IPO rather than indefinite independent operation.
- Consumer familiarity with paying by bank transfer still lags card payments in most markets, so merchants typically see it used as a secondary option rather than a full card replacement.
- The 1.15 to 3.15% merchant fee range is not a single published rate, so a merchant cannot know its actual cost without a sales negotiation.
- As with all open banking-dependent payment methods, reliability depends on the consistency of the underlying banks' own APIs, which Trustly does not control.
- Its verified payout functionality is heavily used in gaming and gambling, a sector with additional regulatory scrutiny, which is worth factoring in when evaluating vendor risk exposure by association.
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
Trustly
On request- Trustly$undefined/month
- Typical merchant cost of 1.15% to 3.15% depending on volume and market
- Exact rate negotiated per merchant, not published as a flat card
Which should you pick?
Choose Increase if
- You need ach origination and receipt.
- You work on API, Web.
- You also want domestic wires.
Choose Trustly if
- You need pay by bank checkout.
- You work on Web, API.
- You also want instant refunds.
Questions people ask
- Is Increase or Trustly better?
- Neither clearly leads. Increase starts at On request and Trustly at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Increase or Trustly?
- Increase starts at On request and Trustly at On request.
- Does Increase or Trustly run on more platforms?
- Increase runs on API, Web. Trustly runs on Web, API.
- 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 Trustly is typically brought in for.
- What can Increase do that Trustly cannot?
- Increase covers ACH origination and receipt, Domestic wires, Real-time payments, Bank accounts. Trustly covers Pay by bank checkout, Instant refunds, Verified payouts, Multi-market bank connectivity.
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.
Trustly: Who owns Trustly?
Nordic Capital, a private equity firm, holds a 51.1% majority stake; Alfven & Didrikson and BlackRock hold smaller stakes.
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.
Trustly: Is Trustly going public?
It has discussed an IPO but as of its most recent comments said one remained at least a year away.
Increase: Is it international?
No. Increase covers United States rails only, so cross border payouts require a second provider.
Trustly: What does it typically cost a merchant?
Roughly 1.15% to 3.15% of transaction value depending on volume and market, negotiated per merchant.
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.
Related pages
Other head to heads
- Increase vs Dwolla
- Increase vs Astra
- Increase vs Unit
- Increase vs Treasury Prime
- Increase vs Sila
- Increase vs Moov
- Increase vs Column
- Increase vs Lithic
- Increase vs Volt
- Increase vs Swan
- Increase vs TrueLayer
- Increase vs Griffin
- Increase vs KeystoneJS
- Increase vs Kong
- Increase vs Liveblocks
- Increase vs Moesif
- Increase vs Ozone API
- Increase vs Parse Server
- Increase vs Yapily
- Increase vs Aiia
- Increase vs Token.io
- Increase vs Tink
- Increase vs Brite Payments
- Increase vs Zimpler
- Increase vs Salt Edge
- Increase vs Yodlee
- Increase vs Stainless
- Increase vs Strapi
- Increase vs Swagger/OpenAPI
- Increase vs Thredd
- Increase vs Thunder Client
- Increase vs Toqio
- Trustly vs Dwolla
- Trustly vs Astra
- Trustly vs Unit
- Trustly vs Treasury Prime
- Trustly vs Sila
- Trustly vs Moov
- Trustly vs Column
- Trustly vs Lithic
- Trustly vs Volt
- Trustly vs Swan
- Trustly vs TrueLayer
- Trustly vs Griffin
- Trustly vs KeystoneJS
- Trustly vs Kong
- Trustly vs Liveblocks
- Trustly vs Moesif
- Trustly vs Ozone API
- Trustly vs Parse Server
- Trustly vs Yapily
- Trustly vs Aiia
- Trustly vs Token.io
- Trustly vs Tink
- Trustly vs Brite Payments
- Trustly vs Zimpler
- Trustly vs Salt Edge
- Trustly vs Yodlee
- Trustly vs Stainless
- Trustly vs Strapi
- Trustly vs Swagger/OpenAPI
- Trustly vs Thredd
- Trustly vs Thunder Client
- Trustly vs Toqio
