Skip to main content
The Model Context Protocol (MCP) is an open standard that connects AI applications to external data sources. With the PayNext MCP servers, you can search the docs or work with your payments, customers, and plans by chatting with your AI tool. Connect one or both. The documentation server is read-only and needs no credentials. The account server works with your live PayNext data, and you connect to it either by signing in or with an API key.

Documentation server

The documentation server lets AI tools search PayNext documentation directly instead of relying on training data or web search. You get answers from the latest docs, including new features and API changes, with relevant code examples while you work. URL: https://docs.paynext.com/mcp

Account server

The account server gives your AI tool access to your PayNext data, using the same data and rules as the Dashboard. Ask in plain language, and your AI tool picks the right tool and fills in the details:
  • “Find payments for jane@example.com from last week and tell me why the failed ones failed.”
  • “Refund pay_123 but keep the customer’s subscription.”
  • “What was our acceptance rate last month?”
  • “How did MRR change over the last 3 months?”
  • “How much revenue did we recognize in September, and how much is still deferred?”
  • “Add these eight BINs to our block list.”
  • “Create a monthly Pro plan at 19.99 EUR with a 7-day trial.”
  • “Which of our API keys haven’t been used this month?”
Answers follow the Dashboard’s rules. A payment the Dashboard wouldn’t let you refund can’t be refunded through your AI tool either. URL: https://mcp.paynext.com/mcp

Sign in and grant access

  1. Add the account server to your AI tool. See Connect to AI tools.
  2. Your browser opens. Sign in with your PayNext account.
  3. On the access screen, review the access your AI tool asks for, then select Approve:
    • Read access lets your AI tool look up your data.
    • Write access also lets it make changes, such as refunds, cancellations, and plan updates. Without it, every change is refused.
  4. Return to your AI tool. The session starts in the organization you last selected in the Dashboard.
Your AI tool never sees your PayNext password. To check which organization and role a session uses, ask “Which organization am I in?” To move to another of your organizations, ask your AI tool to switch. It may give you a link to open in your browser to finish the switch. If your PayNext sign-in ends, changes stop at once and reads stop within a minute. A sign-in ends when you sign out in the browser you signed in with, or when it expires. Your AI tool then asks you to sign in again. If it doesn’t, remove the account server from your AI tool and add it again.

What you can do

The tools available to you depend on your role. Your AI tool only lists the tools your role allows.
“All” means Admin, Member, and Support Specialist. With a role outside these three, your AI tool can look up records, such as payments and customers. It can’t change data or read the Dashboard figures, and it can’t see API keys, processors, tax providers, integration health, or workflow runs.

Dashboard figures

The Dashboard tools return the same figures as the Dashboard charts, so an answer matches what you see on the same tab with the same settings.
  • Same defaults. Without a date range, each tool reads the period its tab opens on: the last 30 days for Overview, Risk, and Disputes, the last 3 months for Billing, and the last 6 months for Revenue recognition. Open disputes are always as of now. Name a different period, interval, breakdown, or filter in your question, as you would pick it on the tab. A period can’t end after today.
  • UTC and USD. Dates are in UTC, and amounts are in USD, as on the Dashboard.
  • Today is still moving. A period that includes today shows it to date, so figures for today can change between two questions.
  • Unavailable isn’t zero. If a figure can’t be read, your AI tool says it’s unavailable rather than showing 0, and whether asking again can help. If a Revenue recognition report is too large for your AI tool to compute, add filters, such as a processor, payment method, or currency. A shorter period helps less than you might expect.

Before a change runs

Every change runs with your role, in the organization your session was in when your AI tool asked for it.
The account server changes live data. Refunds, subscription cancellations, and revoking an API key can’t be undone. When you sign in, they wait for your approval, and with an API key they run at once.
  • A rate limit on changes. You can make up to 30 changes per minute in each organization. The limit is yours alone, and your teammates each have their own. Above it, the change isn’t sent, and your AI tool tells you when you can continue. Your approvals in the browser have their own limit of 30 per minute. Above it, the page tells you when to try again, and the link still works.
  • No silent repeats. If PayNext doesn’t confirm a change, for example after a timeout, your AI tool tells you the result is unknown. Check the record before you try again, so a refund is never sent twice.
  • Amounts use minor units. 1999 in EUR is 19.99 EUR. See Currencies for currencies with other decimal places.

Approve a change in your browser

When you sign in to the account server, a refund, a subscription cancellation, or revoking an API key waits for your approval. Your AI tool asks, and you decide on a PayNext page. Your AI tool gives you an approval link, or opens it in your browser. Nothing has changed yet. Only you can approve: anyone else who opens the link is refused.
  1. Open the link in a browser signed in to PayNext as yourself, if your AI tool hasn’t opened it for you. If you aren’t signed in, the page takes you to the PayNext sign-in first, then back to the approval page. On the approval page, check that your browser’s address bar shows mcp.paynext.com. If it doesn’t, don’t approve.
  2. Check the action on the page, then select Approve or Reject. Approve runs what the page shows, once. For a refund, that can include the subscription cancellation. Reject changes nothing.
  3. Return to your AI tool. If it hasn’t reported the result, send it any message.
When you select Approve, PayNext reads the record again and sends nothing if the change no longer applies. For example, the payment was already refunded, or a refund’s amount or cancellation differs from what the page showed. PayNext also sends nothing if you left the organization or your role no longer allows the change. The page says why. The change runs in the organization where your AI tool asked for it, even if you’ve switched since. The link works for 10 minutes. After that, nothing changes, and your AI tool can give you a new link. Closing the page, ending the chat, or dismissing your AI tool’s prompt to open the link doesn’t reject the change. Only Reject does. Some AI tools show the link themselves, wait up to 5 minutes for your decision, and report the result in the same reply. Others reply at once and report the result after your next message, or on their own. To check in the same session, ask “What happened to my approvals?” Your AI tool can report a result for up to 10 minutes after the change ends. After that, or in a new chat, ask it to look up the payment, subscription, or API key. If PayNext doesn’t confirm an approved change, your AI tool says it may or may not have happened, and nothing is sent again. Only refunds, subscription cancellations, and API key revocations wait for approval. Every other change runs as soon as your AI tool calls it. That includes creating an API key, and your AI tool sees the new key’s secret. A key with the Refunds: Write permission can refund through an API key connection, where nothing waits. Approval doesn’t protect you from an AI tool you don’t trust, so don’t give one write access.
An approval isn’t a second factor. Anyone, or any AI tool, that can use your signed-in browser can approve. Don’t let an AI tool control the browser you approve in.

Connect your software with an API key

Your own software can connect to the account server without a person signing in. Send your PayNext API key in the Authorization header of every request. Most AI tools accept a configuration like this:
With an API key, the account server offers four tools: A search looks like payment_status:"SETTLED" AND amount>5000, which finds settled payments over 5000 in minor units (50.00 in a two-decimal currency). The key’s own permissions decide what each call can do, so a key without the Refunds: Write permission can’t refund. The 30-changes-per-minute rate limit applies to each key. Nothing waits for approval with an API key: a refund or a cancellation runs as soon as your software calls it. For security, the account server refuses any search that mentions network_token, including payment_token_type:"NETWORK_TOKEN". To find a payment by its card, search payment_method.details.bin or payment_method.details.last4. To find a customer by a card, search payment_methods.details.bin or payment_methods.details.last4. You can sort results by any field PayNext supports sorting on. Sorting by a field whose value is always hidden, such as a card number or a token, is refused.
Never expose API keys in frontend code, public repositories, or client-side applications. Create a separate key for each integration, with only the permissions it needs.

Connect to AI tools

Each example adds the documentation server and the account server. Drop the PayNext server if you only need documentation search.
  1. Press Cmd + Shift + P (Mac) or Ctrl + Shift + P (Windows) to open the command palette
  2. Search for Open MCP settings
  3. Select Add custom MCP to open mcp.json
  4. Add the PayNext servers:
  1. In Cursor’s chat, ask “What tools do you have available?” to verify the connection

Quick connect

You can also connect the documentation server from any documentation page:
  1. Click the contextual menu (three dots) at the top of any page
  2. Select Connect to Cursor or Connect to VS Code for one-click installation
  3. Or select Copy MCP server URL to get the URL for other tools