Payment Gateway
Zum Rails MCP connector
The Zum Rails connector brings users, payment instruments, bank accounts, cards, balances, card transactions and statements into Claude, ChatGPT, Cursor and any MCP client, so your team can look them up and update them by asking, within their own Zum Rails access.
-
How it connects. Connects with an API key. 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 Zum Rails to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Zum Rails once
-
Open Connections, choose Add connection, and pick Zum Rails.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Zum Rails API key. One person generates a token in Zum Rails and pastes it once. Everyone else works through Share with, and never sees it.
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 Zum Rails 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 Zum Rails 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 Zum Rails 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 Zum Rails 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 Zum Rails through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Freeze a lost card and reissue it
When a cardholder calls about a missing card, look up the card, change its status so it stops working, and order a reissue in the same conversation. The audit log records who did it and when.
-
Finance
Check a card balance before approving spend
Ask for the current balance on a specific Zum Rails card and its recent transactions before you sign off on a purchase or a top-up, without opening another tab.
-
Operations
Update a user's bank account or address
When a customer sends new banking details or moves, update their bank account, billing address or shipping address on the Zum Rails user record from the notes in front of you.
-
Onboarding
Set up a new user with a payment instrument
Create the Zum Rails user, add their payment instrument or credit card, and record the card approval as one job instead of five screens.
-
Accounting
Pull statements and transactions for a period
Ask for a card's statements for the quarter and the transactions behind each one, then have the agent summarize totals for the close or an expense query.
-
Card programs
Review cards and transactions across a program
List the cards in a program, see which ones are active or blocked, scan their transactions, and adjust the card program settings when the terms change.
Try asking
- “List Zum Rails users added this week with bank accounts.”
- “Which card approvals are still pending in Zum Rails?”
- “Show payment instruments updated for our top ten users.”
AI tools
Zum Rails tools for your AI agents
74 tools are ready to call through Elaichi's MCP endpoint the moment you connect Zum Rails, 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 Zum Rails gets you
6 screens from the product, each doing one job for your Zum Rails account.
The agent
Ask about Zum Rails users in plain language.
Answers come from live Zum Rails users, payment instruments and card approvals.
- users
- payment instruments
- bank accounts
- card approvals
Ask Elaichi to work across your apps.
List Zum Rails users added this week with bank accounts.
Which card approvals are still pending in Zum Rails?
Show payment instruments updated for our top ten users.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect Zum Rails from any MCP client over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
All 74 Zum Rails tools, no custom code.
Users, payment instruments, bank accounts, credit cards and card approvals, ready to call.
- Create a Zum Rails auth
- Update a Zum Rails auth by ID
- Create a Zum Rails user
- Get single Zum Rails user by ID
Toolboxes
Every team gets its own Zum Rails toolbox.
Finance, payments and support each see the toolbox scoped to their work.
- Finance
- Payments Ops
- Risk
- Support
Shared connections
Teammates move payments without seeing a credential.
Each Zum Rails connection shows who added it and which teams share it.
- Finance Canada
- Payments Ops
- Risk Review
- Support Tier 1
Audit log
Answer who touched which Zum Rails user.
Append-only log records when, who, what happened, type and resource.
- 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 the payout digest, you approve.
Six steps fetch Zum Rails transactions, group them, draft, wait for approval, post back.
Zum Rails digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch users
Zum Rails
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
Zum Rails
Queued
Collections and dashboards
Zum Rails payment numbers, computed not generated.
Four metrics, 14 days of users created and a team breakdown, refreshed on schedule.
Zum Rails health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Payment instruments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Finance Canada 34%
Payments Ops 27%
Risk Review 21%
Support Tier 1 18%
FAQ
Frequently asked questions
How do I connect Zum Rails to Claude?
First connect Zum Rails in Elaichi by pasting your Zum Rails API key when prompted. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Zum Rails users, cards and statements are available in your chat.
Does Zum Rails work with ChatGPT and Cursor as well as Claude?
Yes. Once Zum Rails is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect Zum Rails once and every client you use picks it up.
What can an AI agent actually do with my Zum Rails data?
An agent connected to Zum Rails can look up a user, create or update a user and their payment instruments, bank account, credit card and addresses, check a card balance, change a card's status, order a reissue, and pull card transactions and statements. Because Zum Rails offers many actions, short concrete asks such as "show the balance on card ending 4412" work better than long paragraphs.
Does connecting Zum Rails give the AI access to everything in my account?
No. Every request to Zum Rails runs inside the access of the person who signed in to Elaichi, so the agent sees and changes only what that person could already see and change. Elaichi can narrow that further, for example to read-only on cards and statements, but it can never widen it.
Can I stop an agent from deleting or changing things in Zum Rails?
Yes. Restrictions in Elaichi work per action, so you can allow looking up Zum Rails users and card balances while blocking deleting a user or changing a card's status. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.
What happens to a Zum Rails connection when someone leaves?
Offboarding the person in Elaichi ends their access to Zum Rails through every client at once. If they set up a shared Zum Rails connection, it keeps working for everyone else on the team. Disconnecting Zum Rails once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Put Zum Rails in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.