Skip to content

Tap Payments MCP connector

The Tap Payments connector for Elaichi lets Claude, ChatGPT, Cursor 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.

  • 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 Tap Payments to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Tap Payments once

  1. Open Connections, choose Add connection, and pick Tap Payments.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Tap Payments API key. One person generates a token in Tap Payments 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.

tap payments
Tap Payments
Airwallex
Cashfree Payments
ChargeDesk
Chimoney
Circle
2

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.

Tap Payments MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Tap Payments MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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 Tap Payments to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Tap Payments through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • 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?”

See all 72 Tap Payments tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Tap Payments, by what to check
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 $15 per user per month. 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.

AI tools

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.

See it in Elaichi

What connecting Tap Payments gets you

6 screens from the product, each doing one job for your Tap Payments account.

The agent

Ask about charges, get live answers.

Plain language questions run against Tap Payments charges, refunds and authorizations.

  • charges
  • refunds
  • authorizations
  • businesses

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 or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Every client reaches Tap Payments over OAuth, with no SDK and no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

72 Tap Payments tools, no custom code.

Charges, authorizations, refunds, businesses and downloads are cataloged with methods and resources.

  • Create a Tap Payments authorize
  • Update a Tap Payments authorize by ID
  • Tap Payments authorize download
  • Create a Tap Payments authorize download
ElaichiTools
Tool Action Description
Create a Tap Payments authorize Create Create an authorization hold on a card in Tap. Returns the authorize object including id, object, status, amount, currency, live_mode, api_version, method, transaction, reference, response, card, customer, source, redirect, post, auto, merchant, metadata, and payment_agreement.
Update a Tap Payments authorize by ID Update Update an existing Tap authorization by id. Only description, metadata, and receipt may be modified; all other fields remain unchanged. Returns the updated authorize object including id, status, amount, currency, live_mode, api_version, transaction, customer, source, card, redirect, post, and auto details. Required: id.
Tap Payments authorize download Download Download Tap authorize records filtered by date range and merchant IDs. Returns the authorize records as a downloadable file.
Create a Tap Payments authorize download Create Create a Tap authorize download request to export authorize records matching specified filter criteria. Returns a downloadable file of matched authorize records; response format is content-type-specific (text/plain or application/json).
Create a Tap Payments charge Create Create a charge in Tap to collect payment from a customer. Returns the created charge object including id, status, amount, currency, customer, card, source, and transaction details. Required: amount, currency, customer, source, redirect.

Toolboxes

Every team gets its own toolbox.

Finance, support and engineering each see the Tap Payments tools their work needs.

  • Finance
  • Support
  • Engineering
  • Risk
ElaichiToolboxes
Name Source template Tools Created

Finance toolbox

Tap Payments · charges and settlements

Tap Payments starter 18 Mar 4, 2026

Support toolbox

Tap Payments · refunds and disputes

— 9 Mar 2, 2026

Engineering toolbox

Tap Payments · authorizations and webhooks

— 24 Feb 27, 2026

Risk toolbox

Tap Payments · declines and chargebacks

Tap Payments starter 6 Feb 19, 2026

Operations toolbox

Tap Payments · businesses and downloads

— 31 Jan 30, 2026

Data toolbox

Tap Payments · charge exports and reporting

— 12 Jan 22, 2026

Shared connections

Teammates run refunds without touching keys.

Each Tap Payments connection shows who connected it and which teams share it.

  • Retail UAE
  • Marketplace KSA
  • Subscriptions
  • Support Refunds
ElaichiConnections
Connection Scope Status Access
TA

Tap Payments (Retail UAE)

Connected by Emily Carter

Personal • Active 1 team · 6 members
TA

Tap Payments (Marketplace KSA)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
TA

Tap Payments (Subscriptions)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
TA

Tap Payments (Support Refunds)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
TA

Tap Payments (Sandbox)

Connected by Ryan Hayes

Personal • Active Not shared
TA

Tap Payments (Finance Ops)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every charge and refund call is recorded.

When, who, what happened, type and resource for each Tap Payments call.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Tap Payments Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Tap Payments Charges Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Tap Payments Charges List Toolbox

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 fires, a refund digest ships.

Tap Payments charges are fetched, grouped, drafted, approved by a person, then posted back.

Tap Payments digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch charges

    Tap Payments

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Tap Payments

    Queued

Collections and dashboards

Payment health, computed and refreshed on schedule.

Four metrics, 14 days of charges created and a breakdown by team.

Tap Payments health

Refreshed 4 minutes ago · every 15 minutes · from the charges collection

Live

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%

FAQ

Frequently asked questions

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, 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 my team share one Tap Payments connection?

Yes. One person connects Tap Payments in Elaichi and shares it with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who issued a refund or created an invoice in Tap Payments.

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 blocking refunds, new charges or changes to existing records. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.

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 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.