Softwr

APIs · head to head

Dwolla vs Skaleet

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
-
Skaleet logo

Skaleet

APIs

Cloud-native core banking and payment hub with deployments measured in months

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.; Skaleet the installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.
  • They diverge on capability: Dwolla covers ACH transfers, Skaleet covers Cloud-native core.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Dwolla and Skaleet actually diverge.

Attributes where Dwolla and Skaleet differ
AttributeDwollaSkaleet
PlatformsWebWeb, REST API, Linux

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 Skaleet

  • Cloud-native core
  • Payment hub
  • Card management
  • Lending
  • API-first
  • Configurable products

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 Skaleet
  • A B2B marketplace collecting large invoice payments by bank transfer rather than paying interchange on cardsnot Skaleet
  • A payroll or gig platform that needs to pay workers instantly and wants the rail chosen automatically by receiving bank capabilitynot Skaleet
  • A property management system collecting rent by ACH with verified bank accounts and reliable return handlingnot Skaleet

Skaleet

  • A banking group launching a digital savings or deposit brand in a new country within a yearnot Dwolla
  • A bank modernising payments to ISO 20022 without replacing its whole corenot Dwolla
  • A payroll or HR software company adding embedded banking to its productnot Dwolla
  • A payment service provider needing a ledger and accounts under its existing licencenot 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.

Skaleet

  • The installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.
  • Speed references are mostly greenfield launches inside large groups, which is an easier problem than migrating an existing book off a legacy core.
  • It is European-centric, with payment rails and regulatory work concentrated on SEPA and EU requirements rather than global coverage.
  • As a smaller vendor carrying a bank core, it attracts hard concentration and viability questions in procurement that larger competitors do not face.
  • Pricing is unpublished and scaled by accounts and transactions, so a bank whose volumes grow faster than forecast faces cost escalation it did not model.

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

Skaleet

On request
  • Skaleet Core Banking Platform$undefined/year
    • Subscription licence scaled by accounts and transaction volume
    • Payment hub licensable separately from the full core
    • Implementation and configuration charged as a project

Which should you pick?

Choose Dwolla if

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

Choose Skaleet if

  • You need cloud-native core.
  • You work on Web, REST API, Linux.
  • You also want payment hub.

Questions people ask

Is Dwolla or Skaleet better?
Neither clearly leads. Dwolla starts at On request and Skaleet at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dwolla or Skaleet?
Dwolla starts at On request and Skaleet at On request.
Does Dwolla or Skaleet run on more platforms?
Dwolla runs on Web. Skaleet runs on Web, REST API, Linux.
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 Skaleet is typically brought in for.
What can Dwolla do that Skaleet cannot?
Dwolla covers ACH transfers, Instant payments, Rail orchestration, Bank account verification. Skaleet covers Cloud-native core, Payment hub, Card management, Lending.

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.

Skaleet: What was Skaleet called before?

TagPay. The company rebranded to Skaleet while keeping the same platform lineage.

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.

Skaleet: Can I buy just the payment hub?

Yes. The payment engine is licensable standalone and can sit over an existing core, which is a common first step.

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.

Skaleet: How fast are real deployments?

Named European deployments have gone live in six to twelve months, including a Crédit Agricole savings platform live in Germany in eight months.

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