Payment Gateway
Dwolla MCP connector
The Dwolla connector lets Claude, ChatGPT, Cursor, and other MCP clients look up and update Dwolla customers, funding sources, transfers, and beneficial owner records inside each person's own Dwolla access, with every call audited.
-
How it connects. App credentials. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Dwolla to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Dwolla once
-
Open Connections, choose Add connection, and pick Dwolla.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Dwolla app credentials. Dwolla authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Dwolla to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Dwolla to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Dwolla to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Dwolla to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Dwolla through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Check where a transfer stands
Ask for the transfers on a Dwolla account and see which ones are pending, processed, or failed without opening the dashboard.
-
Operations
Onboard a new customer in Dwolla
Create the Dwolla customer record from the details in a signup form, then attach the identity document they sent over.
-
Compliance
Verify beneficial owners for a business
List the beneficial owners on a Dwolla business customer, add or correct one, upload their document, and certify ownership when the set is complete.
-
Support
Fix a customer's bank details
Pull up a Dwolla customer's funding sources, confirm which bank account is linked, and rename or update one after a call.
-
Treasury
Review mass payments before reconciliation
List the mass payments run from your Dwolla account and match them against the payout schedule for the month.
-
Onboarding
Pick the right business classification
Search Dwolla's business classifications to find the correct category and industry code before creating a business customer.
Try asking
- “List failed Dwolla transfers from the last seven days.”
- “Which customers have no verified funding source yet?”
- “Summarize this week's mass payments by receiving customer.”
AI tools
Dwolla tools for your AI agents
82 tools are ready to call through Elaichi's MCP endpoint the moment you connect Dwolla, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Dwolla gets you
6 screens from the product, each doing one job for your Dwolla account.
The agent
Ask about transfers, get live answers.
Plain language questions run against Dwolla customers, transfers and funding sources.
- customers
- transfers
- funding sources
- mass payments
Ask Elaichi to work across your apps.
List failed Dwolla transfers from the last seven days.
Which customers have no verified funding source yet?
Summarize this week's mass payments by receiving customer.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Dwolla.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
82 Dwolla tools ready to call.
Customers, transfers, funding sources, mass payments and beneficial owners, no custom code.
- Create a Dwolla funding source
- List all Dwolla funding sources
- Get single Dwolla funding source by ID
- Update a Dwolla funding source by ID
Toolboxes
Every team gets its own toolbox.
Finance, Treasury and Support each see a curated set of Dwolla tools.
- Finance
- Treasury
- Payments Ops
- Compliance
Shared connections
Teammates move money without holding keys.
See who connected each Dwolla account and which teams and members use it.
- Finance US
- Treasury
- Payments Ops
- Compliance
Audit log
Every Dwolla call is on the record.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your transfer digest.
Six steps fetch Dwolla transfers, group them, draft, wait for approval, then post back.
Dwolla digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch customers
Dwolla
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Dwolla
Queued
Collections and dashboards
Dwolla numbers are waiting when you arrive.
Four metrics, 14 days of transfers created and a team breakdown, computed on schedule.
Dwolla health
Refreshed 4 minutes ago · every 15 minutes · from the customers collection
Customers
1,284 ↓ 12%
Transfers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Customers created
Last 14 days
By team
Share of activity
Finance US 34%
Treasury 27%
Payments Ops 21%
Compliance 18%
FAQ
Frequently asked questions
How do I connect Dwolla to Claude?
Connect Dwolla in Elaichi first, where you sign in with your Dwolla app credentials. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you in through Elaichi and Dwolla is available in your next conversation.
Does Dwolla work with ChatGPT and Cursor as well as Claude?
Yes. Once Dwolla is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Dwolla once and every client picks it up.
What can an AI agent actually do with my Dwolla data?
With Dwolla connected, an agent can look up customers, create or update a customer, list and update funding sources, and review the transfers and mass payments on your Dwolla accounts. It can also manage beneficial owners, upload customer and owner documents, certify beneficial ownership, and search business classifications. Because Dwolla has many actions, short direct asks such as "list funding sources for customer Acme" work better than long paragraphs.
Does connecting Dwolla give the AI access to everything in my account?
No. Every call to Dwolla runs inside the access of the person who signed in, so an agent sees only the Dwolla customers, funding sources, and transfers that person can already see. Elaichi can narrow that further by turning off specific actions, but it can never grant more than the person's own Dwolla access allows.
Can I stop an agent from deleting or changing things in Dwolla?
Yes. Restrictions in Elaichi apply per action, so you can allow looking up Dwolla customers and transfers while blocking updates, document uploads, or deleting a beneficial owner. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.
What happens to a Dwolla connection when someone leaves?
Offboarding a person in Elaichi ends their access to Dwolla and every other connected application at once, in every client they used. A Dwolla connection shared with a team keeps working for everyone else on it. If you want Dwolla gone entirely, disconnecting it once in Elaichi removes it from every client.
Put Dwolla in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.