Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Query Paytm merchant orders, payment links, refunds, settlements and subscriptions.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Paytm MCP Server connects a Paytm merchant account to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 12 tools, every one a fetch_* read over orders, payment links, refunds, settlements and subscriptions. Paytm's own documentation publishes 21 tools, and 9 of those write — including initiating a refund. Sign-in is OAuth 2.0 through the Paytm merchant dashboard.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
initiate_refund, create_payment_link, process_transaction, cancel_subscription and create_qr_code. Check your own client's tool list before granting approval.fetch_* prefix is not a permission. All 12 listed names begin fetch_, and Anthropic labels the connector "Read". Paytm's own product copy names creating payment links and processing refunds as core features of the same server.openid, profile and email are the only advertised scopes. There is no read-versus-write scope and nothing on the consent screen to decline, so the real boundary is the merchant account and whether MCP access is enabled on it.fetch_settlement_orders and fetch_settlements_by_date carry no API link in Paytm's tools table, so their response fields are not documented on the pages we read.authorization_endpoint at preoauth.paytmpayments.com; the authorization server's own document points it at accounts.paytmpayments.com. Only the root form of the RFC 9728 descriptor resolves, and the 401 carries no WWW-Authenticate header.initialize on 2026-08-19, so names came from the directory snapshot and meanings from Paytm's documentation. We read no readOnlyHint or destructiveHint off the wire and make no claim about them. No tool was called.The Anthropic listing is; the server is not. Anthropic's directory sets permissions to Read and names 12 tools, all prefixed fetch_. Paytm's own MCP documentation publishes 21 tools, and 9 of those create, update, cancel or initiate — including a tool that initiates a refund and one that creates a payment link.
No. Paytm's Fetch Bin Details API takes a bin field documented as the first 9 digits of a card number or card token, and the reference note asks for exactly 9 digits for an accurate response. Never paste a full card number into an AI assistant regardless, because nine digits is all the tool uses.
Through OAuth 2.0 against your Paytm merchant dashboard login. Paytm's documentation describes redirecting to the merchant dashboard, signing in with credentials and an OTP, then approving an authorization screen. The connector receives an access token, and Paytm states your API keys and secrets are never shared with or stored by the AI client.
Paytm's own answer lists creating payment links, fetching transaction details, tracking settlements, processing refunds, checking refund status, validating UPI VPAs, fetching BIN details, checking subscription status, and retrieving convenience charge details. Four of those nine are write operations that Anthropic's 12-tool directory listing does not name.
Paytm's troubleshooting answer names three things. Confirm you are using a valid Paytm merchant account with MCP access enabled, since the feature is gated per account. Check that your browser is not blocking pop-ups from the Paytm domain. Then clear your browser cache and attempt the connection again.
Paytm lists four checks. Confirm the server URL in your mcp.json is exactly the /mcp endpoint on mcp.paytmpayments.com. Confirm you clicked Connect in the MCP servers list after adding the server. Confirm you completed authentication by entering your email and OTP on the login page. Then restart Cursor after saving.
Thirty days per query. Paytm's tool descriptions state that both the order list and the refund list fetch within a date range of 30 days. The underlying Order List API adds a second bound, requiring the order creation start time to fall within 18 months, and it paginates rather than returning everything at once.
www.paytmpayments.com/robots.txt allows this path, names a sitemap, and carries no Content-Signal directive. · retrieved 2026-08-19bin request field documented as the first 9 digits of a card number or token, the 9-digit accuracy note, and the binDetail response fields issuingBank, issuingBankCode, channelName, paymentMode, cnMin, cnMax, cvvR and cvvL (HTTP 200, retrieved 2026-08-19) · retrieved 2026-08-19txnId, mid, merchantName, vanId, vanIfscCode and rrn (HTTP 200, retrieved 2026-08-19) · retrieved 2026-08-19https://mcp.paytmpayments.com/mcp — HTTP 401 to both GET and an initialize POST, with no WWW-Authenticate header; host root and /sse each HTTP 403 (2026-08-19). No tool was called and no credential was supplied. · retrieved 2026-08-19/.well-known/oauth-protected-resource HTTP 200 declaring resource as the /mcp URL and scopes_supported as the three OIDC scopes; the RFC-insert form HTTP 404; /.well-known/oauth-authorization-server HTTP 200; and the authorization server's own metadata at preoauth.paytmpayments.com, diffed against it (2026-08-19) · retrieved 2026-08-19partner tier, the 12 tool names, the financial-services category, the "Read" permissions label, the endpoint, the transport, the documentation and support URLs and the Claude Code install string (snapshot dated 2026-08-16) · retrieved 2026-08-16Connect Paytm Payment Gateway once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.