Softwr

APIs · head to head

Volt vs Weavr

Volt logo

Volt

APIs

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

From
On request
Rated
-
Full reviewWebsite
Weavr logo

Weavr

APIs

Packaged embedded finance for B2B SaaS, with an in-house EU e-money licence

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Volt account-to-account payments carry no chargeback mechanism, so consumers lose scheme dispute protection and merchants lose a familiar framework for handling claims.; Weavr products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • They diverge on capability: Volt covers Pay by bank, Weavr covers Plug-and-play products.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Volt and Weavr actually diverge.

Attributes where Volt and Weavr differ
AttributeVoltWeavr

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

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

Only in Weavr

  • Plug-and-play products
  • Regulated cover
  • Card issuing
  • Multi-currency accounts
  • Identity and onboarding
  • Data insights

What people use each for

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

Volt

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

Weavr

  • A project management SaaS adding expense cards without hiring a compliance officernot Volt
  • A marketplace paying out sellers from accounts held inside its own productnot Volt
  • A procurement platform issuing virtual cards against approved purchase ordersnot Volt
  • A European SaaS vendor wanting a regulated entity to sit behind its financial featuresnot Volt

Where each one falls short

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

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.

Weavr

  • Products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • Programme economics depend on interchange, and SaaS vendors routinely overestimate how much card volume their customers will actually route through the embedded product.
  • It is a small company with limited headcount supporting a regulated dependency, which is a real concentration risk for a feature your customers rely on.
  • Monthly minimums on card programmes mean a slow-adopting customer base leaves you paying for volume you never reach.
  • European interchange caps hold programme revenue well below what US embedded finance case studies suggest, so imported business cases do not transfer.

Pricing, plan by plan

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

Weavr

On request
  • Weavr embedded finance$undefined/year
    • Platform subscription plus per-account and per-card fees
    • Interchange share negotiated as part of the commercial terms
    • Monthly minimums apply to card programmes

Which should you pick?

Choose Volt if

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

Choose Weavr if

  • You need plug-and-play products.
  • You work on Web, REST API.
  • You also want regulated cover.
Weavr review

Questions people ask

Is Volt or Weavr better?
Neither clearly leads. Volt starts at On request and Weavr at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Volt or Weavr?
Volt starts at On request and Weavr at On request.
Does Volt or Weavr run on more platforms?
Both run on Web, REST API, so platform support will not decide this one for you.
What is Volt best used for?
Volt is most often used for a travel seller with high average order values paying percentage card fees it wants to replace with flat transfer fees, an igaming operator needing fast deposits and payouts where card acceptance is restricted, a merchant with heavy card fraud that wants strongly authenticated irreversible payments, a marketplace verifying seller bank accounts before paying out. Of those, a travel seller with high average order values paying percentage card fees it wants to replace with flat transfer fees and an igaming operator needing fast deposits and payouts where card acceptance is restricted are not what Weavr is typically brought in for.
What can Volt do that Weavr cannot?
Volt covers Pay by bank, Circuit Breaker, Virtual IBANs, Payouts and refunds. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.

Answered from the vendors’ own pages

Volt: Are there chargebacks?

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

Weavr: Do I need my own financial licence?

No. Weavr holds an e-money licence, including a Maltese authorisation for the EU, and acts as the regulated entity for the embedded product.

Volt: How do refunds work?

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

Weavr: How is it different from a banking-as-a-service API?

It sells finished product shapes with compliance built in rather than raw banking primitives, which trades flexibility for a much shorter route to launch.

Volt: Which markets are covered?

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

Weavr: How does Weavr make money?

Platform fees plus per-account and per-card charges, with a negotiated share of card interchange.

Share

Related pages

More on Volt

More on Weavr

Keep looking

Other head to heads