Bring Payment Gateway
to Claude Desktop
Learn how to connect Payrexx to Claude Desktop and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Payrexx MCP Server?
Connect your Payrexx account to any AI agent and take full control of your payment orchestration and checkout flows through natural conversation. Payrexx is the leading payment provider in Switzerland and Europe, and this integration allows you to create payment gateways, monitor real-time transaction metadata, and manage recurring subscriptions directly from your chat interface.
What you can do
- Gateway & Link Orchestration — Create custom payment gateways and multi-use payment links programmatically to ensure your sales flow is always synchronized.
- Transaction Lifecycle Management — Access and monitor real-time transaction statuses and retrieve detailed financial metadata directly from the AI interface to track revenue health.
- Subscription & Recurring Control — Manage recurring billing cycles and list active subscriptions via natural language to drive better customer retention.
- Payout & Invoice Oversight — Access organizational payouts and list invoices to maintain a clear overview of your cash flow using simple AI commands.
- Operational Monitoring — Track system responses and manage webhook metadata to ensure your automation workflows are always optimized.
How it works
1. Subscribe to this server
2. Enter your Payrexx Instance Name and API Secret from your merchant settings
3. Start managing your payment operations from Claude, Cursor, or any MCP-compatible client
No more manual status checks in the dashboard. Your AI acts as a dedicated payments coordinator or finance coordinator.
Who is this for?
- Swiss & European Merchants — quickly retrieve payment summaries and monitor transaction status without switching apps.
- Finance Operations Teams — automate the retrieval of payout metadata and track organizational billing via natural conversation.
- Developers — integrate real-time payment data and gateway management directly within the chat.
Built-in capabilities (11)
Verify API connectivity and signature
Create a new payment gateway (hosted payment page)
Get details of a specific gateway
Get details of a specific transaction
List all payment gateways
List invoices
List available payment methods
List payouts
List recurring subscriptions
List recent transactions
List configured webhooks
Why Claude Desktop?
Claude Desktop is the definitive way to connect Payrexx to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Payrexx in Claude Desktop
Payrexx and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Payrexx to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Payrexx in Claude Desktop
The Payrexx MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Payrexx for Claude Desktop
Every tool call from Claude Desktop to the Payrexx MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.