Skip to content

Connectors / Payment Gateway

Payment Gateway MCP connectors for Claude, ChatGPT and Cursor

20+ Payment Gateway connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.

https://api.elaichi.ai/mcp The same for every user.
  • Their own access. An agent never gets more than the person it acts for.

  • One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.

In practice

What teams do with Payment Gateway connectors

Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.

Finance

  • Reconcile the day's balance transactions

    Pull the list of balance transactions for a date range, group them by type, and check the totals against what landed in the bank.

  • Check balances across every wallet

    Ask for the current balances across all Circle wallets in one go instead of opening each wallet set. Get a plain answer you can paste into the morning report.

  • Reconcile yesterday's payments and refunds

    List every Square payment and refund for a date range, spot the ones that failed or were canceled, and get a clean picture before closing the books.

Support

  • Answer a charge question in one look

    Pull up a customer's GoCardless payments and mandate status while they are still on the phone, and cancel a payment that should not go out.

  • Find out what a customer is entitled to

    Look up a customer's benefit grants in Polar to confirm which license keys, downloads or Discord access they should have. Fetch the downloadable they are asking about instead of hunting for it in the dashboard.

  • Trace a disputed charge to a settlement

    When a customer disputes a charge, find the chargeback, see which settlement it was deducted from and give the customer a clear answer.

Operations

  • Set up QR codes for the pop-up

    Create a Razorpay QR code for each stall or counter, and close them again when the event ends so nobody pays into a code that should be retired.

  • Onboard a new sub account in minutes

    Create a JustiFi sub account for a new merchant or location, review its settings, and confirm its payout account is in place before the first sale.

  • Set up a new beneficiary correctly

    Look up the beneficiary rules and accepted identification types for a country, then create the beneficiary bank record with the fields that country actually requires.

Sales

  • NMI

    Authorize a card, capture later

    Run an authorization on a new customer's card to confirm it is good, then capture the payment once the order ships.

  • Set up a new customer to bill

    Create the Flutterwave customer when a deal closes, add their payment method and raise the first charge from the same conversation.

  • Send a payment link to close a deal

    Create a Midtrans payment link for the agreed amount, share it with the customer, and check later whether it has been paid.

Once it is connected

Things to ask

Each of these is answered against the access the person asking already has, in the Payment Gateway account you connected.

  • Show today's exchange rates for USD to KES.

    Chimoney

  • List monitored tokens added to Circle this week.

    Circle

  • List failed Dwolla transfers from the last seven days.

    Dwolla

  • Show Finexio invoices created for Acme this month.

    Finexio

  • Show Flutterwave charges created this week by payment method.

    Flutterwave

  • Show me all failed payments from this week.

    GoCardless

  • Show yesterday's failed payments by sub account.

    JustiFi

  • Show all pending Midtrans transactions from this week.

    Midtrans

The tools

What an agent can call in Payment Gateway

Connectors
20+

in the Payment Gateway catalog

Tools
2,431

callable the moment you connect

Hosted sign-in
21

connect with nothing to register

Of those 2,431 tools, 5% delete something. Restricting an agent to reads is not a promise here, it is 1,106 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 45%
1,106 tools · list, get, search
Write 34%
835 tools · create, update, send
Delete 5%
132 tools · delete, remove, archive
Other 15%
358 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

Every Payment Gateway connector, by depth

Tool counts are what the connector exposes today; the split is what those tools do.

Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.

Payment Gateway connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
Stripe 532 Hosted
Circle 294 Hosted
Square 287 Your own app
GoCardless 137 Hosted
Polar 136 Hosted
Mollie 124 Hosted
Razorpay 100 Hosted
JustiFi 90 Hosted
Chimoney 86 Hosted
Dwolla 82 Hosted
Spreedly 78 Hosted
Zum Rails 74 Hosted
Tap Payments 72 Hosted
Orum 70 Hosted
NMI 68 Hosted
Flutterwave 57 Hosted
Midtrans 44 Hosted
Moment 33 Hosted
Finexio 26 Hosted
Plastiq 26 Hosted
Peach 10 Hosted
Rootline 5 Hosted

FAQ

Frequently asked questions

How many Payment Gateway connectors does Elaichi have?

20+ Payment Gateway connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.

Can Claude, ChatGPT and Cursor all use Payment Gateway connectors?

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Payment Gateway account once makes it reachable from every one of them.

Do Payment Gateway connectors work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Payment Gateway connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.

Do Payment Gateway connectors need me to bring my own OAuth app?

Most do not. 21 of the Payment Gateway connectors use Elaichi's hosted sign-in, with nothing to register. The other 1 ask you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.

Can I stop an agent from writing to Payment Gateway tools?

Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Payment Gateway connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Payment Gateway connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

Nearby

Teams that connect Payment Gateway usually connect these too

Put Payment Gateway connectors in front of your team

14 days on Gold, no credit card. Connect one 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.