Ensure all recipient Dwolla customers are verified and their funding sources are added and verified (via micro-deposits or Plaid instant verification)
Construct the mass payment request body with the _links source funding source and the items array, each item specifying a destination funding source and amount
POST to the mass payments endpoint and capture the Location header containing the mass payment resource URL
Poll the mass payment resource and each mass payment item resource to monitor individual transfer statuses as they progress from pending to processed
Handle items in failed status by reading the failure reason and deciding whether to retry with a new mass payment item or alert the customer
Reconcile each successful item against your internal payout ledger using the Dwolla transfer resource ID
Known gotchas
Mass payments in Dwolla are asynchronous; do not assume all items succeed because the top-level POST returned 201 Created
A single failed item in a mass payment does not cause the entire batch to fail; other items continue processing, requiring per-item status tracking
Dwolla ACH funding sources are subject to a hold period for unverified or recently verified sources; verify hold policies before promising same-day disbursement
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp