Tap Payments MCP connector
The Tap Payments connector for Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot and other MCP clients look up charges, issue refunds, raise invoices and add customers in Tap Payments, with every action running as the signed-in person and recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
List charges over 500 AED created this week.
Working in Tap Payments with Elaichi
-
List all Tap Payments charge
-
List all Tap Payments business
-
List all Tap Payments destination
How to connect Tap Payments to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Tap Payments MCP connector for 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.
Tap Payments MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Tap Payments MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Tap Payments MCP connector for 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.
Tap Payments MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Tap Payments 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.
What teams do with Tap Payments through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Tap Payments is logged.
-
Finance
Find a charge and issue the refund
Pull up a customer's charges by amount or date, confirm which one they mean, and issue the full or partial refund in Tap Payments without leaving the conversation.
-
Support
Answer a payment question from live records
When a customer asks why a card was charged twice, list their recent Tap Payments charges and give them a clear answer while they are still on the line.
-
Accounts receivable
Raise an invoice and chase it later
Create a Tap Payments invoice for a customer, then come back in a week to list what is still unpaid and update the due date or notes on the ones that need it.
-
Operations
Set up a new customer before the first charge
Add a new customer record in Tap Payments with their name, email and phone so the first charge or invoice goes out with the right details attached.
-
Finance
Export charges, refunds and disputes for reconciliation
Request a download of the month's charges, refunds or disputes from Tap Payments and hand the file to whoever closes the books.
-
Partnerships
Check merchant accounts and payout destinations
List the businesses and merchants under your Tap Payments account, look up where a merchant's payouts are routed, and onboard a new merchant when a partner signs.
Try asking
- “List charges over 500 AED created this week.”
- “Summarize refunds issued against the Retail business yesterday.”
- “Which authorizations are still uncaptured after 48 hours?”
What connecting Tap Payments gets you
6 screens from Elaichi, each doing one job for your Tap Payments account.
Ask Elaichi to work across your apps.
List charges over 500 AED created this week.
Summarize refunds issued against the Retail business yesterday.
Which authorizations are still uncaptured after 48 hours?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about charges, get live answers.
Plain language questions run against Tap Payments charges, refunds and authorizations.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Every client reaches Tap Payments over OAuth, with no SDK and no shared key.
Tool catalog
72 Tap Payments tools, no custom code.
Charges, authorizations, refunds, businesses and downloads are cataloged with methods and resources.
Toolboxes
Every team gets its own toolbox.
Finance, support and engineering each see the Tap Payments tools their work needs.
Shared connections
Teammates run refunds without touching keys.
Each Tap Payments connection shows who connected it and which teams share it.
Audit log
Every charge and refund call is recorded.
When, who, what happened, type and resource for each Tap Payments call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Tap Payments digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch charges
Tap Payments
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 Jake Morgan
Approve Deny -
Post the digest
Tap Payments
Queued
Automations
A schedule fires, a refund digest ships.
Tap Payments charges are fetched, grouped, drafted, approved by a person, then posted back.
Tap Payments health
Refreshed 4 minutes ago · every 15 minutes · from the charges collection
Charges
1,284 ↓ 12%
Refunds
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Charges created
Last 14 days
By team
Share of activity
Retail UAE 34%
Marketplace KSA 27%
Subscriptions 21%
Support Refunds 18%
Collections and dashboards
Payment health, computed and refreshed on schedule.
Four metrics, 14 days of charges created and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Tap Payments
All three can connect Tap Payments to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Tap Payments tools | Allow or restrict single Tap Payments tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Tap Payments call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Tap Payments tools for your AI agents
72 tools are ready to call through Elaichi's MCP endpoint the moment you connect Tap Payments, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Tap Payments to Claude?
In Elaichi, choose Tap Payments from the catalog and paste in the API key from your Tap Payments dashboard. 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 the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Tap Payments is ready to use.
Does Tap Payments work with ChatGPT and Cursor as well as Claude?
Yes. Once Tap Payments is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Tap Payments once and every client you use picks it up.
What can an AI agent actually do with my Tap Payments data?
It can look up charges, create a charge or an authorization, issue refunds, raise and update invoices, add customers, and list the businesses, merchants and payout destinations under your Tap Payments account. It can also request downloads of charges, refunds, authorizations and disputes for reconciliation. Because Tap Payments has a large set of actions, short concrete asks like "refund the 120 SAR charge from yesterday" work better than long paragraphs.
Does connecting Tap Payments give the AI access to every account and merchant?
No. The AI acts through the Tap Payments credentials of the person who connected it, so it can only reach the businesses, merchants and charges that key already covers. Elaichi can narrow that further, for example to read-only or to specific actions, but it can never grant more than Tap Payments itself allows.
Can I stop an agent from refunding or changing things in Tap Payments?
Yes. Restrictions in Elaichi apply per action, so you can allow looking up Tap Payments charges and invoices while restricting refunds, new charges or changes to existing records. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Tap Payments connection when someone leaves?
Offboarding that person in Elaichi ends their access to Tap Payments at once, across every client they used. If they shared a Tap Payments connection with a team, it keeps working for everyone else. Disconnecting Tap Payments once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Tap Payments MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Tap Payments is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Tap Payments?
Yes. Both let Claude, ChatGPT or Cursor use Tap Payments. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Tap Payments call.
How is Elaichi different from Composio for Tap Payments?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Tap Payments: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Tap Payments in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot