Payrexx MCP for AI. Manage payments, billing, and gateways from your chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
Payrexx connects your Swiss payment gateway to any AI client. You use it to manage entire checkout flows—creating custom gateways, tracking real-time transactions, listing subscriptions, and pulling financial metadata—all through natural conversation instead of logging into multiple dashboards.
What AI agents can do with Payrexx Automation
Check api status
Verifies if your API connection is active and correctly signed.
Create gateway
Generates a new, dedicated payment gateway (hosted page) for a specific purpose.
Get gateway
Retrieves detailed information about one specific payment gateway you've created.
Generate new hosted payment pages or links programmatically, allowing you to direct specific customer payments.
Retrieve full details for a single transaction by ID, giving you immediate visibility into its status and metadata.
Get a comprehensive list of all payment gateways associated with your merchant account.
Fetch a list of active subscriptions and manage recurring billing details via natural language commands.
Retrieve lists of all outstanding invoices or processed payouts to keep a clear overview of cash flow.
Ask an AI about this
Waiting for input…
What AI agents can do with Payrexx MCP Server: 11 Tools for Global Payment Orchestration
These tools allow you to programmatically create gateways, track detailed transactions, manage subscriptions, list invoices, and monitor webhooks from within your AI agent.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Payrexx on VinkiusCheck Api Status
Verifies if your API connection is active and correctly signed.
Create Gateway
Generates a new, dedicated payment gateway (hosted page) for a specific purpose.
Get Gateway
Retrieves detailed information about one specific payment gateway you've created.
Get Transaction
Fetches all details for a single transaction based on its unique identifier.
List Gateways
Lists every payment gateway configured under your account.
List Invoices
Retrieves a list of all generated invoices for financial review.
List Payment Methods
Shows which payment methods (Visa, TWINT, etc.) are available to your customers.
List Payouts
Lists all historical payouts made from your merchant account.
List Subscriptions
Provides a list of current and past recurring billing subscriptions.
List Transactions
Shows recent transactions, giving you an overview of your payment activity.
List Webhooks
Lists all webhooks configured for system notifications and monitoring.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Payrexx integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Payrexx, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Payrexx. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 11 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Checking transaction status shouldn't require switching between five browser tabs., Solved with Vinkius AI Gateway
Today, if a client calls about a payment failure, you open your dashboard. You navigate to 'Transactions.' You filter by date. Then you click on the ID. You check the notes section for the reason. If it's a subscription issue, you have to open another tab and run a separate report to see their active plan. It’s clicking, filtering, copying, and pasting.
With this MCP server, your AI agent handles the entire workflow. Instead of manual steps, you simply ask: 'What happened with transaction XYZ?' The agent runs `get_transaction` and returns everything—status, date, failure reason, method used—in one clean block of text. You get the answer instantly.
Payrexx MCP Server: Manage gateways and billing from chat.
Setting up a temporary payment link for an event is usually a multi-step process: create product > select gateway > generate link > copy URL. Each step requires logging in, confirming credentials, and managing metadata fields manually.
Now? You just tell your agent: 'Create a payment link for 50 CHF titled Event Ticket.' The server runs `create_gateway` and gives you the ready-to-share URL, complete with expiration dates and accepted methods. It's that simple.
What your AI can actually do with this
You connect Payrexx to your AI agent and ditch those payment dashboards. This setup gives your agent full hands-on control over every part of your checkout process, from creating a new sales link to reconciling cash flow—all through natural conversation instead of clicking around in ten different tabs.
Your AI client acts like your dedicated payments coordinator, giving you programmatic access to core financial operations that usually require jumping between multiple systems and running manual API calls. It’s not just reading data; it lets you execute actions.
Setting Up Payment Channels
The check_api_status tool verifies if the connection is active and properly signed, letting you instantly confirm your payment gateway access. You can use list_gateways to pull a full rundown of every single payment gateway configured under your account. If you need a specific new hosted page or link for a targeted sale, you run create_gateway, which generates the dedicated payment gateway; then, if you need details on that new setup, get_gateway pulls all the necessary info about it.
You can also retrieve detailed information about any existing payment channel using get_gateway.
Handling Transactions and Payments
To monitor sales, your agent first uses list_transactions, which gives you a quick overview of recent payments activity across your entire account. If you need to deep-dive into one specific sale, running get_transaction lets you pull every single detail for that transaction using only its unique ID. You can check what payment methods are available to your customer base anytime with list_payment_methods, showing everything from Visa to TWINT.
This coverage lets you know exactly which options the buyer is going to have.
Managing Billing and Revenue Streams
Managing subscriptions doesn't mean logging into a separate billing portal. You can get a list of all recurring charges using list_subscriptions, whether they’re current or past due. For bookkeeping, running list_invoices gives you a comprehensive rundown of every outstanding invoice ready for review. To track the money that actually hits your bank account, use list_payouts; this pulls a list of all historical payouts made from your merchant account.
This combination allows you to keep a crystal-clear picture of incoming revenue and outgoing funds.
System Oversight
For system maintenance, running list_webhooks shows every webhook configured for system notifications, letting you monitor where Payrexx sends automated alerts. When all these tools work together—from establishing a new payment link via create_gateway, to tracking the flow with get_transaction, and finally reconciling the money using list_payouts—you keep your entire financial operation visible and controlled right in the chat window.
You'll never have to switch tabs or write boilerplate API calls again.
019dd138-4195-72c4-b399-0bf5a7a2a0bb 
Here's how it actually works
The bottom line is: Your AI client becomes your single point of access for all payment operations, eliminating manual dashboard navigation.
First, subscribe to the server and input your Payrexx Instance Name and API Secret credentials in the required fields.
Next, prompt your AI client (Claude, Cursor, etc.) with a specific payment request, like 'List all payouts from last month.'
The agent invokes the necessary tool (e.g., list_payouts), retrieves the structured data, and presents it to you in plain language.
Who is this actually for?
This is for the finance ops engineer who's tired of logging into 3 different dashboards just to reconcile cash flow. It’s for e-commerce developers needing real-time transaction data in their code, and merchants who need immediate billing oversight without context switching.
Manages recurring billing cycles and runs reconciliation reports by using tools like list_payouts and list_subscriptions to verify cash flow.
Integrates real-time payment data into checkout flows by calling create_gateway or checking transaction status via get_transaction.
Quickly checks the overall health of their payments and reviews outstanding invoices using simple commands like 'list invoices'.
What Changes When You Connect
Immediate Financial Oversight: Stop manually checking dashboards. You can call list_invoices or list_payouts to get a clear cash flow summary in seconds—no log-ins required.
Programmatic Gateway Creation: Need a new payment link for an event? Use create_gateway. It builds the necessary hosted page and gives you a shareable link, all from your prompt.
Deep Transaction Visibility: Instead of just seeing 'Success,' use get_transaction to pull deep metadata—like which specific card or method was used—for better auditing.
Billing Lifecycle Control: Forget confusing billing cycles. You can list active recurring payments using list_subscriptions, making customer retention checks simple and direct.
Operational Debugging: Developers gain peace of mind by listing configured endpoints with list_webhooks. You instantly verify that your automation triggers are set up correctly.
Full Method Awareness: If you're debugging a payment failure, running list_payment_methods tells you exactly which options (like TWINT or PostFinance) the system supports.
See it in action
Reconciling Quarterly Subscriptions
The finance manager needs to reconcile all revenue streams for the quarter. Instead of running reports in the dashboard, they ask their agent: 'list subscriptions.' The agent runs list_subscriptions and provides a structured list, showing which customers are active and when their next billing date hits.
Creating an Event Payment Funnel
A marketing team needs to sell tickets for a one-day event. They prompt the agent: 'Create a payment gateway for 99 CHF, titled 'Event Ticket'. The agent runs create_gateway, gives them a secure link, and confirms acceptance of multiple methods.
Investigating Failed Payments
A customer reports their card was declined. Instead of calling support and waiting for an investigation, the developer uses get_transaction with the transaction ID. The agent pulls the details, showing if it was a 'declined' status or something else.
Auditing Payouts
The team needs to verify that all payouts from last month were processed correctly. They prompt: 'list payouts for May.' The agent executes list_payouts and gives a summary of the total amount, date range, and status.
The honest tradeoffs
Manual Dashboard Status Checks
Logging into the Payrexx website to manually scroll through recent transactions just to find out if a payment cleared. This is slow and error-prone.
Don't browse; ask your agent. Use list_transactions or, for deep dives, use get_transaction with the specific ID. It gets you the data instantly.
Assuming Connectivity
Relying on a payment flow that suddenly breaks because an API key expired or the endpoint changed. You won't know until sales stop.
Always run check_api_status first. It verifies connectivity and signatures immediately, so you catch issues before they cost money.
Listing Everything Pointlessly
Just running 'list everything' when you only care about one type of record (e.g., subscriptions). You get a massive data dump with irrelevant info.
Be specific in your prompt. If you need recurring income, ask for list_subscriptions. If you need historical cash flow, ask for list_payouts.
When It Fits, When It Doesn't
Use this Payrexx MCP Server if your main bottleneck is moving payment data from disconnected financial systems into one single conversation. It's perfect when you need to programmatically create links, check billing cycles (list_subscriptions), or pull immediate transaction details for debugging.
Don't use this if your core problem is complex accounting (like tax filing or GAAP compliance). For that, you still need dedicated ERP software (like SAP or NetSuite). This tool handles the transaction mechanics—the gateway layer—but it isn't a full ledger system. If you only need to check API health, running check_api_status is sufficient; don't bother with anything else.
Questions you might have
How do I check if Payrexx is connected properly using check_api_status? +
Running check_api_status validates your API credentials and connectivity signature. It confirms that the server can talk to Payrexx, so you know right away if there's a credential issue before any payments fail.
Can I list all my invoices using list_invoices? +
Yes. list_invoices retrieves an organized summary of all your generated invoices. This is useful for quick reconciliation checks without diving into the full financial portal.
What does get_transaction do exactly? +
get_transaction pulls granular details for one specific transaction ID. You use this when you need to know why a payment failed or verify specific metadata about a successful charge.
How can I check my recurring payments using list_subscriptions? +
You call list_subscriptions to get a comprehensive overview of all active and past billing cycles. This helps you track customer revenue health and identify potential churn risks.
How do I use `get_gateway` to check the current status of a specific payment gateway? +
It returns all configuration details for one named gateway. You can confirm its unique ID, active status, and setup parameters without having to list every gateway first. This is efficient when you know exactly which gateway you need.
When I use `list_transactions`, what filters should I apply for reporting? +
You can specify start and end dates, allowing precise filtering of transaction data. This lets you calculate revenue metrics for specific accounting periods or audit a certain timeframe's activity.
How do I manage or audit my payment webhook configurations using `list_webhooks`? +
This tool lists every configured endpoint and the last status of those webhooks. You can confirm which external services are receiving transaction updates, making troubleshooting much faster than checking your dashboard.
What kind of financial data does `list_payouts` provide? +
It gives a detailed view of payout records, including the recipient account and the date funds were disbursed. You track when money actually leaves Payrexx to reach your bank, giving you full visibility into cash flow timing.
Can my AI automatically find the status for a specific transaction by its ID? +
Yes! Use the get_transaction tool with the Transaction ID. Your agent will respond with complete metadata, including payment method, currency, amount, and final status in seconds.
How do I find my Payrexx API Secret and Instance Name? +
Log in to your Payrexx merchant dashboard, navigate to Settings > API, and you will find your unique secret key and instance name (e.g., yourname.payrexx.com) there.
Does this work for recurring payments? +
Absolutely. You can use the list_subscriptions tool to monitor active recurring billing cycles and orchestrate multi-use gateways for recurring customer payments.
We've already built the connector for Payrexx. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 11 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.