Softwr

APIs · head to head

Dwolla vs Weavr

Dwolla logo

Dwolla

APIs

Account to account payment API for ACH, RTP and FedNow with pay by bank and instant payment routing

From
On request
Rated
-
Weavr logo

Weavr

APIs

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

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.; 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: Dwolla covers ACH transfers, 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 Dwolla and Weavr actually diverge.

Attributes where Dwolla and Weavr differ
AttributeDwollaWeavr
PlatformsWebWeb, REST API

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 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.

Dwolla

  • An insurance or lending platform disbursing funds to customer bank accounts where card payout fees would destroy the marginnot Weavr
  • A B2B marketplace collecting large invoice payments by bank transfer rather than paying interchange on cardsnot Weavr
  • A payroll or gig platform that needs to pay workers instantly and wants the rail chosen automatically by receiving bank capabilitynot Weavr
  • A property management system collecting rent by ACH with verified bank accounts and reliable return handlingnot Weavr

Weavr

  • A project management SaaS adding expense cards without hiring a compliance officernot Dwolla
  • A marketplace paying out sellers from accounts held inside its own productnot Dwolla
  • A procurement platform issuing virtual cards against approved purchase ordersnot Dwolla
  • A European SaaS vendor wanting a regulated entity to sit behind its financial featuresnot 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.

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

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

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

  • You need ach transfers.
  • You also want instant payments.

Choose Weavr if

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

Questions people ask

Is Dwolla or Weavr better?
Neither clearly leads. Dwolla 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, Dwolla or Weavr?
Dwolla starts at On request and Weavr at On request.
Does Dwolla or Weavr run on more platforms?
Dwolla runs on Web. Weavr runs on Web, REST API.
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 Weavr is typically brought in for.
What can Dwolla do that Weavr cannot?
Dwolla covers ACH transfers, Instant payments, Rail orchestration, Bank account verification. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.

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.

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.

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.

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.

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.

Weavr: How does Weavr make money?

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

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.

Share

Related pages

Other head to heads