Commerce & Payments · Integration
Dwolla
Add Dwolla to your product for your customers, and give your AI agents governed access to it.
Dwolla is an ACH and real-time payments API whose responses are HAL, so you navigate by following _links rather than by building URLs, and the Accept and Content-Type headers must be application/vnd.dwolla.v1.hal+json or the call is rejected. Creating a customer, a funding source or a transfer returns 201 with an empty body and the new resource URL in the Location header, which surprises anyone expecting the object back inline. Access tokens come from an OAuth2 client_credentials exchange and expire after an hour, so long-lived jobs need refresh logic rather than a stored key. The sandbox sits on api-sandbox.dwolla.com with its own separate credentials and its own customer records, and micro-deposit verification of a bank account has to be completed there too before transfers will clear. Transfers are asynchronous and can fail days later with an ACH return code, so webhooks, verified against the HMAC signature on the request, are the only reliable source of final status. fastn holds each customer's Dwolla credentials, refreshes the short-lived tokens, and keeps the webhook subscription maintained per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Dwolla account so payouts move on their funding sources and under their limits.
Create verified customer records and attach bank funding sources from inside your onboarding flow.
Initiate transfers from your app and reconcile them against your own ledger entries.
Surface ACH returns and failed transfers to the customer with the return reason attached.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent read transfer and customer status to answer questions, with money movement kept behind human approval and audited per tenant.
Have an agent reconcile a day's transfers against expected payouts and flag mismatches.
Allow an agent to explain why a specific transfer failed by reading its return code and funding source state.
Example prompt
Which Dwolla transfers from last week failed, and what return codes came back?
Set up Dwolla in 4 steps
- 01Enable the Dwolla connector from your fastn dashboard.
- 02Have each customer authorise their own Dwolla account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Dwolla integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Dwolla integration without building it. Your customers connect their own Dwolla account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Dwolla update is not your on-call problem.
- One integration serves your product and your agents. The same governed Dwolla connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to Dwolla, across other categories.
NetSuite
Notion
Box
DocusignDwolla integration FAQ
How do I add a Dwolla integration to my product?
Enable the Dwolla connector in your fastn dashboard, then let each customer authenticate their own Dwolla account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Dwolla client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Dwolla account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Dwolla account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Dwolla integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent read transfer and customer status to answer questions, with money movement kept behind human approval and audited per tenant.
Who maintains the Dwolla integration?
fastn does. When Dwolla changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Dwolla integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Dwolla integration?
A common starting point: let a customer connect their own Dwolla account so payouts move on their funding sources and under their limits. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Dwolla integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Dwolla does not change your per-connector cost. You can start free with 3 connected accounts.
Add Dwolla to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.