Softwr

APIs · head to head

Rutter vs Trustly

Rutter logo

Rutter

APIs

One API across accounting, commerce, payments and advertising platforms

From
On request
Rated
-
Trustly logo

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: Rutter a unified schema exposes only the fields common across platforms, so the platform-specific detail underwriting models want usually requires passthrough calls and per-platform code, which is the work the unified API was bought to avoid.; 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: Rutter covers Accounting and ERP, 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 Rutter and Trustly actually diverge.

Attributes where Rutter and Trustly differ
AttributeRutterTrustly

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

  • Accounting and ERP
  • Commerce data
  • Payments data
  • Advertising data
  • Write operations
  • Passthrough requests
  • Observability tooling
  • Sandbox

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.

Rutter

  • A revenue-based lender that must pull a merchant's sales, payouts and general ledger before pricing a facilitynot Trustly
  • A spend management product that needs to push bills and journal entries back into whichever accounting system its customer runsnot Trustly
  • A B2B payments platform reconciling invoices across customers using four different ERPsnot Trustly
  • An insurance or benefits provider that needs verified business financials without asking the customer to upload PDFsnot Trustly

Trustly

  • An e-commerce merchant wanting a lower-cost alternative or complement to card payment acceptancenot Rutter
  • A gaming or gambling operator needing verified, instant payouts to players' bank accountsnot Rutter
  • A merchant wanting instant refunds processed directly to a customer's bank account rather than card reversal delaysnot Rutter
  • A business in a market with strong open banking adoption wanting pay-by-bank as a checkout optionnot Rutter

Where each one falls short

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

Rutter

  • A unified schema exposes only the fields common across platforms, so the platform-specific detail underwriting models want usually requires passthrough calls and per-platform code, which is the work the unified API was bought to avoid.
  • Write operations into accounting systems are where these products break, because each system validates differently, and a rejected journal entry surfaces as a support ticket against you rather than against the ERP.
  • No pricing is published beyond a sandbox trial, so cost cannot be compared against alternatives without a sales process, and pricing tends to scale with connected accounts.
  • QuickBooks Desktop and other on-premises systems require a local connector or hosted agent, which introduces installation steps your customers must complete and support burden you inherit.
  • Sync freshness varies by platform and by customer authorisation state, so a product promising near real-time figures will find some connections update far less often than the marketing implies.

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

Rutter

On request
  • Starter$undefined/month
    • Thirty day sandbox trial
    • Test integrations with QuickBooks, Xero, FreshBooks and Zoho Books
    • Documentation and workflow guides
  • Full Access$undefined/year
    • Production access across all platforms
    • Includes NetSuite, QuickBooks Desktop and Sage Intacct
    • Write operations and passthrough

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

  • You need accounting and erp.
  • You work on Web, API.
  • You also want commerce data.

Choose Trustly if

  • You need pay by bank checkout.
  • You work on Web, API.
  • You also want instant refunds.

Questions people ask

Is Rutter or Trustly better?
Neither clearly leads. Rutter 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, Rutter or Trustly?
Rutter starts at On request and Trustly at On request.
Does Rutter or Trustly run on more platforms?
Both run on Web, API, so platform support will not decide this one for you.
What is Rutter best used for?
Rutter is most often used for a revenue-based lender that must pull a merchant's sales, payouts and general ledger before pricing a facility, a spend management product that needs to push bills and journal entries back into whichever accounting system its customer runs, a b2b payments platform reconciling invoices across customers using four different erps, an insurance or benefits provider that needs verified business financials without asking the customer to upload pdfs. Of those, a revenue-based lender that must pull a merchant's sales, payouts and general ledger before pricing a facility and a spend management product that needs to push bills and journal entries back into whichever accounting system its customer runs are not what Trustly is typically brought in for.
What can Rutter do that Trustly cannot?
Rutter covers Accounting and ERP, Commerce data, Payments data, Advertising data. Trustly covers Pay by bank checkout, Instant refunds, Verified payouts, Multi-market bank connectivity.

Answered from the vendors’ own pages

Rutter: Does Rutter support QuickBooks Desktop?

Yes, which distinguishes it from unified APIs that only cover cloud accounting, and matters because many small businesses still run it.

Trustly: Who owns Trustly?

Nordic Capital, a private equity firm, holds a 51.1% majority stake; Alfven & Didrikson and BlackRock hold smaller stakes.

Rutter: Can Rutter write data back?

Yes. Invoices, bills and journal entries can be pushed into supported accounting systems, not only read.

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.

Rutter: Is there a free tier?

There is a thirty day sandbox trial with test data. Production access requires a paid plan with quoted pricing.

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.

Rutter: What if the unified model lacks a field I need?

Rutter supports passthrough requests to the underlying platform API, though using them reintroduces platform-specific code.

Share

Related pages

Other head to heads