Paytm Payment Gateway
Query Paytm merchant orders, payment links, refunds, settlements and subscriptions from your AI assistant. Anthropic's directory lists 12 read tools; Paytm's own documentation ships 21, and 9 of those write.
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.
Connect Paytm Payment Gateway via MCP
https://mcp.paytmpayments.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Paytm Payment Gateway Tools & Capabilities (12)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The directory's tool list is a floor, not the surface. Anthropic's snapshot names 12 read tools; Paytm's documentation publishes 21, of which 9 write. The omitted names include
initiate_refund,create_payment_link,process_transaction,cancel_subscriptionandcreate_qr_code. Check your own client's tool list before granting approval. - A
fetch_*prefix is not a permission. All 12 listed names beginfetch_, 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. - Scopes grant identity, not capability.
openid,profileandemailare 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. - Thirty days per query. Both the order list and the refund list are documented as fetching within a 30-day range. The Order List API also bounds the creation start time to 18 months and paginates by page number and page size.
- Two settlement tools have no published API reference.
fetch_settlement_ordersandfetch_settlements_by_datecarry no API link in Paytm's tools table, so their response fields are not documented on the pages we read. - The discovery metadata is inconsistent about the login host. The MCP host's authorization-server document points
authorization_endpointatpreoauth.paytmpayments.com; the authorization server's own document points it ataccounts.paytmpayments.com. Only the root form of the RFC 9728 descriptor resolves, and the 401 carries noWWW-Authenticateheader. - Tool parameters and safety annotations were not readable. The endpoint returned HTTP 401 to an anonymous
initializeon 2026-08-19, so names came from the directory snapshot and meanings from Paytm's documentation. We read noreadOnlyHintordestructiveHintoff the wire and make no claim about them. No tool was called. - Rate limits are not published. Neither Paytm's MCP documentation nor its directory entry names a request limit for the MCP server.
- MCP access is account-gated. Paytm's own troubleshooting treats "a valid Paytm merchant account with MCP access enabled" as a prerequisite, so a working merchant account is not automatically an MCP-enabled one.
Frequently asked questions
Is the Paytm MCP connector read-only?
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.
Does fetch_card_bin_details need a full card number?
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.
How does authentication work on the Paytm MCP Server?
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.
What can I do with the Paytm MCP Server?
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.
The OAuth authorization screen is not appearing. What should I check?
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.
My MCP server is not connecting in Cursor. What should I do?
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.
How far back can the Paytm MCP Server search orders and refunds?
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.
Sources
- Paytm MCP Server documentation, for the 21-row tools table with descriptions and sample prompts, the four setup guides, the OAuth flow and dynamic client registration, the four worked use cases, and all seven FAQ entries (HTTP 200 with no redirect, retrieved 2026-08-19). This is the exact URL Anthropic's directory publishes for the connector.
www.paytmpayments.com/robots.txtallows this path, names a sitemap, and carries noContent-Signaldirective. · retrieved 2026-08-19 - Paytm Fetch Bin Details API reference, for the
binrequest field documented as the first 9 digits of a card number or token, the 9-digit accuracy note, and thebinDetailresponse fieldsissuingBank,issuingBankCode,channelName,paymentMode,cnMin,cnMax,cvvRandcvvL(HTTP 200, retrieved 2026-08-19) · retrieved 2026-08-19 - Paytm Order List API reference, for the 30-day range limit, the 18-month creation-time bound, the pagination parameters, and the per-order response fields including
txnId,mid,merchantName,vanId,vanIfscCodeandrrn(HTTP 200, retrieved 2026-08-19) · retrieved 2026-08-19 - Live unauthenticated probes of
https://mcp.paytmpayments.com/mcp— HTTP 401 to bothGETand aninitializePOST, with noWWW-Authenticateheader; host root and/sseeach HTTP 403 (2026-08-19). No tool was called and no credential was supplied. · retrieved 2026-08-19 - Live RFC 9728 and RFC 8414 discovery —
/.well-known/oauth-protected-resourceHTTP 200 declaringresourceas the/mcpURL andscopes_supportedas the three OIDC scopes; the RFC-insert form HTTP 404;/.well-known/oauth-authorization-serverHTTP 200; and the authorization server's own metadata atpreoauth.paytmpayments.com, diffed against it (2026-08-19) · retrieved 2026-08-19 - Anthropic connector directory entry, for the
partnertier, the 12 tool names, thefinancial-servicescategory, 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-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- Paytm Payment Gateway
- Tools
- 12
- Domain
- mcp.paytmpayments.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.