# Fiserv MCP connector

Connect Fiserv to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can look up payments, create orders and payment links, manage schedules and void charges, each person signed in as themselves, every call logged.

Source: https://elaichi.ai/connectors/fiserv/

## Facts

| | |
| --- | --- |
| Application | Fiserv |
| Category | Payment Gateway |
| AI tools | 44 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Fiserv is connected

- Look up payment 48213 and tell me its current status
- Create a payment link for the Hartwell order, 1,250 dollars
- What is today's USD to EUR exchange rate in Fiserv?

## Connect Fiserv in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Fiserv.
2. Optionally set Share with, then press Connect.
3. Paste a Fiserv API key. One person generates a token in Fiserv and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Fiserv tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Fiserv MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Fiserv MCP connector for Claude Code

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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`.

## Fiserv MCP connector for ChatGPT

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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.

## Fiserv MCP connector for Cursor

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Fiserv MCP connector for Microsoft Copilot

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

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.
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.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Fiserv to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Fiserv tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Fiserv through Elaichi

### Check a payment while the customer waits

Support. Pull up a Fiserv payment by its ID and read back the amount, status and order it belongs to without leaving the chat.

### Void a mistaken charge on the spot

Support. When a customer was charged twice, ask the agent to void the Fiserv payment and confirm it is done, with the action logged under your name.

### Set up a recurring payment schedule

Billing. Create a Fiserv payment schedule for a new subscription, change the amount or date when the plan changes, and delete it when the customer cancels.

### Send a payment link instead of an invoice

Sales. Create a Fiserv payment URL for a quoted amount and paste it into an email, then clear out expired links in one go.

### Verify a card or bank account first

Operations. Run a Fiserv card verification or account verification before onboarding a customer, and store a payment token so the card details are not asked for again.

### Check exchange rates before quoting abroad

Finance. Pull today's Fiserv exchange rates and the available installment plans so a cross-border quote is priced correctly the first time.

## Elaichi vs Zapier MCP vs Composio for Fiserv

All three can connect Fiserv 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. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Fiserv tools | Allow or restrict single Fiserv 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 Fiserv 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Fiserv to Claude?

Connect Fiserv in Elaichi by pasting your Fiserv API key, 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 to Elaichi as yourself and Fiserv payments, orders and schedules are available in Claude.

### Does Fiserv work with ChatGPT and Cursor as well as Claude?

Yes. Once Fiserv 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 Fiserv once and every client uses it.

### What can an AI agent actually do with my Fiserv data?

An agent can look up a Fiserv payment or order by ID, create a new payment or order, void a charge, create and manage payment schedules, create payment links and tokens, run card and account verifications, and pull exchange rates and installment plans. Short, concrete asks such as "void payment 48213" work better than long paragraphs.

### Does connecting Fiserv give the AI everything my merchant account can do?

No. A Fiserv connection carries only what the API key behind it is allowed to do, and each person reaches it through their own Elaichi sign-in and role. Elaichi can narrow what a person or role may do with Fiserv, and it never widens access beyond what the connection already had.

### Can my team share one Fiserv connection?

Yes. One person connects Fiserv with the API key and shares the connection with a team, and nobody else ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who voided a payment or created a schedule, not the account.

### Can I stop an agent from deleting or changing things in Fiserv?

Yes. Restrictions in Elaichi work per action, so you can restrict voiding Fiserv payments or deleting payment schedules for a role or for one person while leaving lookups open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Fiserv connection when someone leaves?

Offboarding a person in Elaichi ends their access to Fiserv at once, in every client they used. A shared Fiserv connection keeps working for everyone else on the team. If you want the connection gone entirely, disconnecting Fiserv once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

### Does the Fiserv MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Fiserv 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 Fiserv?

Yes. Both let Claude, ChatGPT or Cursor use Fiserv. 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 Fiserv call.

### How is Elaichi different from Composio for Fiserv?

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 Fiserv: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 44 Fiserv tools

Every tool below is callable through https://api.elaichi.ai/mcp once Fiserv is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Fiserv payment** (Create). Create a primary Fiserv payment transaction such as a sale, preauthorization, or credit. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, approvedAmount, transactionStatus, transactionResult, approvalCode, and 32 more. Required: requestType, transactionAmount.
- **Get single Fiserv payment by ID** (Get). Get the current state of an existing Fiserv payment transaction by id. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, transactionOrigin, paymentMethodDetails, transactionAmount, transactionStatus, approvalCode, transactionState, and 30 more. Required: id.
- **Update a Fiserv payment by ID** (Update). Update a Fiserv payment and continue processing after a redirect response, such as 3D Secure authentication. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, transactionStatus, transactionState, secure3dResponse, and 33 more. Required: id, authenticationType.
- **Fiserv payments void** (Action). Perform a secondary transaction, such as a void or reversal, on an existing Fiserv payment. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, transactionOrigin, transactionStatus, transactionResult, approvalCode, and 32 more. Required: payment_id, requestType.
- **Update a Fiserv payments action by ID** (Update). Update an existing transaction in Fiserv. Returns the transaction response including ipgTransactionId, transactionStatus, transactionAmount, approvalCode, and transactionState. Only applicable to existing preAuth transactions. Required: id, requestType.
- **Create a Fiserv payments apm** (Create). Perform an action on an existing Fiserv APM transaction, identified by its apm_id. Returns the transaction response including ipgTransactionId, orderId, transactionStatus, transactionResult, approvalCode, and redirectURL. Required: apm_id, requestType.
- **Update a Fiserv payments apm by ID** (Update). Update an existing Fiserv APM transaction by performing an action on it. Returns the transaction response including ipgTransactionId, orderId, transactionStatus, transactionResult, and approvalCode. Required: id, requestType.
- **Get single Fiserv order by ID** (Get). Get the current state of an existing Fiserv order. Returns: clientRequestId, apiTraceId, responseType, type, orderId, numberOfInstallments, billing, shipping, mandate, transactions, additionalDetails. Required: id.
- **Create a Fiserv order** (Create). Perform a secondary transaction (postAuth or return) against an existing Fiserv order, referenced by its order ID. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, approvedAmount, transactionStatus, approvalCode, and 33 more. Required: order_id, requestType.
- **Create a Fiserv payment schedule** (Create). Create a gateway-managed payment schedule in Fiserv. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, userId, state, transactionResponse. Required: requestType, startDate, frequency, transactionAmount.
- **Get single Fiserv payment schedule by ID** (Get). Get details of a gateway-managed payment schedule in Fiserv by id. Returns: clientRequestId, apiTraceId, responseType, type, orderId, numberOfInstallments, billing, shipping, mandate, transactions, additionalDetails, recurringPaymentDetails, industrySpecificExtensions. Required: id.
- **Update a Fiserv payment schedule by ID** (Update). Update a gateway-managed payment schedule in Fiserv by id. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, userId, state, transactionResponse. Required: id, requestType, frequency, transactionAmount.
- **Delete a Fiserv payment schedule by ID** (Delete). Cancel a gateway-managed payment schedule in Fiserv by id. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, userId, state, transactionResponse. Required: id.
- **List all Fiserv payment URLS** (List). Get the current state of an existing Fiserv payment URL. Returns: clientRequestId, apiTraceId, responseType, type, paymentUrlDetails, industrySpecificExtensions. Required: fromDate, toDate.
- **Create a Fiserv payment URL** (Create). Create a Fiserv payment URL to generate a payment link for a transaction. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, paymentUrl, expiration, transactionId. Required: transactionAmount, transactionType.
- **Fiserv payment URLS bulk delete** (Delete). Delete an existing Fiserv payment URL link. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, paymentUrl, expiration, transactionId.
- **Create a Fiserv payment token** (Create). Create a Fiserv payment token from a payment card, payment device, or referenced order to securely store sensitive card details. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, requestTime, brand, country, paymentToken, paymentCard, networkToken, processor, tokenAlias, orderId, and 3 more. Required: requestType.
- **Get single Fiserv payment token by ID** (Get). Get the payment card details associated with a Fiserv payment token by id. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, requestTime, brand, country, paymentToken, paymentCard, networkToken, processor, tokenAlias, orderId, ipgTransactionId, merchantTransactionId, additionalResponseData. Required: id.
- **Delete a Fiserv payment token by ID** (Delete). Delete a Fiserv payment token by id. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, requestTime, brand, country, paymentToken, paymentCard, networkToken, processor, tokenAlias, orderId, ipgTransactionId, merchantTransactionId, additionalResponseData. Required: id.
- **Fiserv payment tokens bulk update** (Update). Update one or more Fiserv payment tokens in a single request. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, requestTime, errors. Required: requestType, paymentTokens.
- **List all Fiserv installments plans** (List). Get eligible installment plans for a payment in Fiserv by submitting store and payment card or token details. Returns: clientRequestId, apiTraceId, responseType, type, installmentPlans. Required: requestType, storeId, amount. Arguments are sent as the JSON body.
- **Fiserv card verifications verify** (Verify). Verify a payment card in Fiserv. Returns the verification result including ipgTransactionId, transactionStatus, transactionResult, approvalCode, transactionAmount, and paymentToken.
- **Fiserv account verifications verify** (Verify). Verify a payment card or payment token in Fiserv. Returns the transaction response including clientRequestId, responseType, transactionType, transactionResult, approvalCode, paymentMethodDetails, and accountVerificationResponse. Required: requestType. The body must be either a PaymentCardVerificationRequest or a PaymentTokenVerificationRequest.
- **List all Fiserv exchange rates** (List). Generate a dynamic currency conversion in Fiserv by converting a base amount to a foreign currency. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, requestTime, exchangeRateDetails. Required: requestType, baseAmount. Use requestType DCCExchangeRateRequest with bin, or DynamicPricingExchangeRateRequest with foreignCurrency; arguments are sent as the JSON body.
- **Fiserv card informations lookup** (Action). Look up card information such as issuer country, card function, and card brand in Fiserv. Returns: clientRequestId, apiTraceId, responseType, type, cardDetails, requestStatus. Requires storeId and a paymentCard or paymentCardEncrypted payload.
- **Fiserv account informations lookup** (Action). Look up card-related account information in Fiserv for a payment card or payment token. Returns: clientRequestId, apiTraceId, responseType, type, cardDetails, requestStatus. Required: requestType.
- **Create a Fiserv checkout** (Create). Create a new Fiserv checkout to initiate a payment transaction. Returns the checkout object with its checkoutId, storeId, and redirectionUrl for the hosted payment page. Required: storeId, transactionType, transactionAmount.
- **Get single Fiserv checkout by ID** (Get). Get a single Fiserv checkout by id. Returns: storeId, checkoutId, orderId, transactionType, approvedAmount, transactionStatus, transactionFailure, paymentMethodUsed, currencyConversion, ipgTransactionDetails, requestSent. Required: id.
- **Create a Fiserv payment link** (Create). Create a Fiserv payment link that can be passed to the end consumer to direct them to a checkout page. Returns: paymentLink. Required: storeId, transactionType.
- **Get single Fiserv payment link by ID** (Get). Get the details of a Fiserv payment link by id — the short link identifier (e.g. dBpYUi) generated when the link was created. Returns: storeId, paymentLink, checkoutId, orderId, approvedAmount, transactionType, transactionStatus, transactionFailure, paymentMethodUsed, currencyConversion, ipgTransactionDetails, requestSent. Required: id.
- **List all Fiserv disputes** (List). Search Fiserv disputes by date range, status, acquirer reference number, order ID, merchant ID, or card scheme case ID. Returns: id, status, stageCode, stageDescription, result, lastAction, posted, due, workByDate, cardScheme, cardIssuer, acquirerReferenceNumber, amount, currency, visaId, and 10 more. Status defaults to OPEN. Max 100 per page. Requires the Institution number credential field when the API key covers more than one institution.
- **Get single Fiserv dispute by ID** (Get). Retrieve a single Fiserv dispute by id. Returns the full dispute record including status, stageCode, reasonCode, amount, currency, and related transactions, documents, events, and notes. Required: id. Requires the Institution number credential field when the API key covers more than one institution.
- **Get single Fiserv dispute document by ID** (Get). Retrieve a dispute document by id in Fiserv. Returns the raw binary document content in the requested format (PDF, image, DOCX, XML, or XML-to-JSON). Required: id, dispute_id. The document is returned only if it matches the requested Accept format. Requires the Institution number credential field when the API key covers more than one institution.
- **Create a Fiserv dispute document** (Create). Attach an evidence document file to a Fiserv dispute case. Returns: documentId. Required: dispute_id, evidence, templateCategoryCode, tcn, networkFormType. Only one document can be attached per API call. Requires the Institution number credential field when the API key covers more than one institution.
- **Create a Fiserv event action** (Create). Execute an action against a dispute event in Fiserv. Returns an empty 204 response on success. Required: dispute_id, event_id, code, tcn. Additional data fields may be required depending on the action code; retrieve them from the dispute's allowedActions requiredDataFields via GET Disputes by Id. Requires the Institution number credential field when the API key covers more than one institution.
- **Create a Fiserv action undo** (Create). Undo a previously taken action on a Fiserv dispute case. Returns an empty 204 response on success. Required: dispute_id, action_id, tcn. The undo is only allowed while the action has not yet been processed in the daily cycle. Requires the Institution number credential field when the API key covers more than one institution.
- **Create a Fiserv dispute note** (Create). Add a note to a Fiserv dispute case to provide more detail and information. Returns the created note's id, tcn, createdBy, created, and userName. Required: dispute_id, tcn, content. Notes cannot be updated once added, but additional notes can be added. Requires the Institution number credential field when the API key covers more than one institution.
- **List all Fiserv funding rejects** (List). List Fiserv funding rejects, optionally filtered by merchant, status, funding id, or posted-date range. Returns: id, reason, reprocessedDate, posted, lastUpdatedBy, status, merchant, originalPayment, account. Max 100 per page. Requires the Institution number credential field when the API key covers more than one institution.
- **Fiserv funding rejects bulk update** (Update). Update the Funding Reject statuses of a batch of funding ids in Fiserv. Accepts an array of items, each with fundingId and status (3 digit status index), minimum one item. Returns an empty 204 response on success. Requires the Institution number credential field when the API key covers more than one institution.
- **Create a Fiserv post adjustment** (Create). Create financial adjustments in Fiserv OmniPay by submitting fees and adjustments to merchant accounts as an array, to be applied as part of the merchant payment or collection. Returns: adjustmentSlipNumber, adjustmentStatus, adjustmentCreationDate. Max 1,000 adjustments per call. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host.
- **Fiserv modify adjustments bulk update** (Update). Modify one or more previously created adjustments in Fiserv OmniPay by submitting a JSON array of modifications (up to 1,000 per call); adjustments can only be modified before processing pickup and only while their status is neither Released nor Cancelled. Returns an empty 204 response on success. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host.
- **Fiserv cancel adjustments bulk delete** (Delete). Cancel one or more adjustments in Fiserv OmniPay by submitting them as an array in the request body. Returns an empty 204 response on success. Up to 1,000 adjustments can be cancelled per request, and only adjustments that have not yet been picked up for processing (status neither 'Released' nor 'Cancelled') can be cancelled. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host.
- **List all Fiserv get adjustments stageds** (List). List staged adjustments in Fiserv OmniPay. Returns: merchantId, adjustmentSlipNumber, adjustmentStatus, adjustmentCategory, adjustmentType, adjustmentCreationDate, accountNumber, amount, currency, date, description, feeSequence, originalTransactionArn, and 5 more. Date ranges span at most 1 month within the last 6 months; max 1000 per page. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host.
- **List all Fiserv reference datas** (List). List reference data valid values for an institution in Fiserv OmniPay adjustments. Returns: classification, code, description. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host.
