Softwr

APIs · head to head

Dwolla vs MX Technologies

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
-
Full reviewWebsite
MX Technologies logo

MX Technologies

APIs

US financial data aggregation with heavy transaction cleansing and enrichment

From
On request
Rated
-
Full reviewWebsite

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.; MX Technologies coverage is United States focused, so any product with European or other international users runs a second aggregator and reconciles two data models, which removes most of the single vendor argument.
  • They diverge on capability: Dwolla covers ACH transfers, MX Technologies covers Account aggregation.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Dwolla and MX Technologies actually diverge.

Attributes where Dwolla and MX Technologies differ
AttributeDwollaMX Technologies
PlatformsWebAPI, Web

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 MX Technologies

  • Account aggregation
  • Transaction cleansing
  • Categorisation
  • Merchant resolution
  • Account verification
  • Balance and funds checks
  • Data enhancement APIs
  • Consent and connection management

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

MX Technologies

  • A credit union building a personal finance view in its own app that needs its own transaction descriptions made readablenot Dwolla
  • A lender using cash flow underwriting that needs categorised income and expense data rather than raw transaction stringsnot Dwolla
  • A bank wanting account verification and balance checks before initiating ACH debits to reduce returnsnot Dwolla
  • A fintech that already aggregates data elsewhere and licenses only the enrichment layer to clean what it hasnot 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.

MX Technologies

  • Coverage is United States focused, so any product with European or other international users runs a second aggregator and reconciles two data models, which removes most of the single vendor argument.
  • Nothing is published on price and contracts are enterprise shaped, so a small fintech cannot estimate cost or start building without a sales process, unlike self-serve competitors.
  • Data enhancement is the differentiator and is licensed separately from aggregation, so the quoted aggregation price is not the price of the product people actually buy it for.
  • Categorisation and merchant resolution are statistical and get business to business and unusual transactions wrong more often than consumer retail, so lending decisions built on categorised data need their own review layer.
  • As the United States moves to regulated API access, connection quality depends on what each institution exposes, and the long tail of small banks and credit unions remains the weakest part of any aggregator including this one.

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

MX Technologies

On request
  • MX Platform$undefined/year
    • Priced by connected users, API calls and modules
    • Data enhancement licensed separately from aggregation
    • Enterprise contracts aimed at financial institutions

Which should you pick?

Choose Dwolla if

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

Choose MX Technologies if

  • You need account aggregation.
  • You work on API, Web.
  • You also want transaction cleansing.
MX Technologies review

Questions people ask

Is Dwolla or MX Technologies better?
Neither clearly leads. Dwolla starts at On request and MX Technologies at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dwolla or MX Technologies?
Dwolla starts at On request and MX Technologies at On request.
Does Dwolla or MX Technologies run on more platforms?
Dwolla runs on Web. MX Technologies runs on API, Web.
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 MX Technologies is typically brought in for.
What can Dwolla do that MX Technologies cannot?
Dwolla covers ACH transfers, Instant payments, Rail orchestration, Bank account verification. MX Technologies covers Account aggregation, Transaction cleansing, Categorisation, Merchant resolution.

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.

MX Technologies: What does MX do that Plaid does not?

It sells transaction cleansing, categorisation and merchant resolution as a first class product, including on data you already hold, which is why financial institutions rather than startups are its core customers.

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.

MX Technologies: Does it cover Europe?

No. MX is United States focused. European coverage requires a different provider such as Tink.

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.

MX Technologies: Is pricing published?

No. Contracts are quoted by connected users, call volume and modules, with enhancement licensed separately from aggregation.

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.

MX Technologies: Does it use screen scraping?

It uses direct bank APIs where institutions expose them and credential based connections elsewhere. The credential path is being deprecated across the industry, and coverage quality now tracks which banks have real APIs.

Share

Related pages

More on Dwolla

More on MX Technologies

Keep looking

Other head to heads