Integration

Payrexx integration

Payrexx is a Swiss online payment platform. Create payment gateways and paylinks that return a hosted payment page link, list and manage transactions (charge or capture a pre-authorization or reservation, refund, cancel, send a receipt), create, send and update invoices, manage subscriptions, read payouts, payment providers and payment methods, create QR codes, and start, cancel, void or refund payments on a paired POS card terminal. Not exposed: the subscription customer login link (it returns a login token), terminal pairing and unpairing, and creating or updating payment page designs (file uploads). Authentication: your instance's API secret, sent in the X-API-KEY header, plus your instance name (example for example.payrexx.com), sent as the instance query parameter.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Payrexx.Built from the 49 Payrexx tools below, on the connection you add once.

What you can do with Payrexx

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Bill, 5 operations

  • create_invoiceCreate invoicePOSTCreates an invoice in a given language and currency with a recipient and line positions (amounts in the smallest currency unit). Set complete to complete it and send to send it.
  • delete_invoiceDelete invoiceDELETEDeletes an invoice; an invoice that can no longer be changed answers an error (merchant_invoice_locked). The answer confirms deleted and the invoice uuid.
  • get_invoiceGet invoiceGETReturns one invoice with its status, payment status, total, recipient, positions, transactions, reminders and payment link.
  • list_invoicesList invoicesGETLists the invoices (bills) of the instance with their status, payment status, total, recipient, positions, reminders and payment link.
  • update_invoiceUpdate invoicePATCHUpdates an invoice; every field is optional. An invoice that can no longer be changed answers an error (merchant_invoice_locked).

Subscription, 5 operations

  • cancel_subscriptionCancel subscriptionDELETECancels (removes) a subscription; the answer returns its id with status cancelled.
  • create_subscriptionCreate subscriptionPOSTCreates a subscription for an existing contact (userId from a Payrexx webhook) and payment provider. Intervals use PHP date interval strings such as P1M. The vendor marks this documentation as experimental.
  • get_subscriptionGet subscriptionGETReturns one subscription with its status, dates, payment interval, charged products and amounts, and the subscriber's contact details.
  • list_subscriptionsList subscriptionsGETLists subscriptions with status, start and end dates, payment interval, charged products and amounts, and the subscriber's contact details.
  • update_subscriptionUpdate subscriptionPUTChanges a subscription's amount (in cents), currency, purpose or VAT rate; the new amount applies from the next payment interval.

Transaction, 5 operations

  • charge_transactionCharge transactionPOSTCharges a pre-authorized or reserved transaction, optionally with another amount in cents, a purpose and a reference id that the transaction webhook carries.
  • delete_reserved_transactionDelete reserved transactionDELETEDeletes a reserved transaction or a tokenization.
  • get_transactionGet transactionGETReturns one transaction with its status, time, amounts, payment brand, provider, mode, reference id, invoice products, refund state and the payer's contact.
  • list_transactionsList transactionsGETLists transactions with status, time, amounts, payment brand, provider, reference id, invoice products and the payer's contact, filterable by UTC date range and sortable by time.
  • update_transaction_contactUpdate transaction contactPUTUpdates the contact details stored on a pre-authorization or tokenization (fields such as forename, surname, email, each as an object with a value).

Design, 3 operations

  • delete_designDelete designDELETEDeletes a payment page design.
  • get_designGet designGETReturns one payment page design (fonts, colors, images, default flag).
  • list_designsList designsGETLists the payment page designs (look and feel) of the instance: name, default flag, fonts, colors and header and background images.

Gateway, 3 operations

  • create_gatewayCreate gatewayPOSTCreates a payment gateway for an amount in cents and a currency; the answer's link is the hosted payment page to send the shopper to. Supports a basket, redirect URLs, pre-authorization, reservation and subscriptions.
  • delete_gatewayDelete gatewayDELETEDeletes a payment gateway.
  • get_gatewayGet gatewayGETReturns one payment gateway with its status (waiting, confirmed, authorized or reserved), link, amount, currency, contact fields and invoices.

Invoice, 3 operations

  • create_paylinkCreate paylinkPOSTCreates a paylink: a hosted payment page with a title, description, purpose, amount in cents and currency. The answer's link is the page URL to share or embed (Payrexx's modal box needs this link or its hash, not referenceId).
  • delete_paylinkDelete paylinkDELETERemoves a paylink.
  • get_paylinkGet paylinkGETReturns one paylink with its status (waiting, confirmed, authorized or reserved), link, amount, contact fields and invoices.

Payout, 3 operations

  • create_manual_payoutCreate manual payoutPOSTCreates a manual payout of an amount in cents from a Payrexx payment provider (pspId 44 Payrexx Pay, 36 Payrexx Pay Plus). Only available once manual payouts have been activated by the Payrexx team.
  • get_payoutGet payoutGETReturns one payout without its transaction details: amount, fees, currency, date, statement, status and destination.
  • list_payoutsList payoutsGETLists payouts with amount, fees, currency, date, statement, status, destination bank account and transfers.

Qr code, 3 operations

  • create_qr_codeCreate qr codePOSTCreates a QR code that sends whoever scans it to your webshop URL; the answer carries its uuid and the image as PNG and SVG data URIs.
  • delete_qr_codeDelete qr codeDELETEDeletes a QR code.
  • get_qr_codeGet qr codeGETReturns one QR code with its webshop URL and the image as PNG and SVG data URIs.

Cancel, 2 operations

  • cancel_terminal_paymentCancel terminal paymentPOSTCancels a terminal payment that has not completed yet.
  • cancel_transactionCancel transactionPATCHCancels a transaction that is still waiting for payment; the answer shows status cancelled.

Payment, 2 operations

  • create_terminal_paymentCreate terminal paymentPOSTStarts a card payment on a paired POS terminal for an amount in cents and a currency, optionally with a tip, purpose, reference id, shop items and a printed slip. get_terminal_payment returns its status.
  • get_terminal_paymentGet terminal paymentGETReturns a terminal payment's status (PAYMENT_REQUESTED, IN_PROGRESS, SUCCESS, DECLINED, TERMINATED, REVERTED, ...), type, amounts, payment method and card brand.

Payment method, 2 operations

  • get_payment_methodGet payment methodGETReturns one payment method with its labels, logo and, per payment service provider, the mode, payment types and currencies it supports.
  • list_payment_methodsList payment methodsGETLists the payment methods active on the instance, optionally filtered by currency, payment type or payment service provider, with the modes, payment types and currencies each provider supports.

Refund, 2 operations

  • refund_terminal_paymentRefund terminal paymentPOSTRefunds a completed terminal payment, in full or (where supported) partially. Newland terminals accept only a full refund; NexGo terminals answer 501 Not Implemented for now.
  • refund_transactionRefund transactionPOSTRefunds a transaction, in full or for a custom amount in cents.

Capture, 1 operation

  • capture_transactionCapture transactionPOSTCaptures a reserved transaction; the answer shows status confirmed.

Config, 1 operation

  • get_terminal_configGet terminal configGETReturns a POS terminal's configuration (name, currency, tipping, receipt printing, accepted payment methods). Payrexx notes it currently answers empty defaults for NexGo and Newland terminals.

Detail, 1 operation

  • get_payout_detailsGet payout detailsGETReturns one payout with the transfers it contains, pageable with offset and limit (Payrexx recommends a limit of 100).

Pair, 1 operation

  • get_terminal_pairingGet terminal pairingGETReturns a POS terminal's pairing status, cashier name and configuration (language, tipping, point of sale name, currency).

Payment provider, 1 operation

  • list_payment_providersList payment providersGETLists the payment service providers connected to the instance with their id, name, available balance per currency, and their supported and active payment methods.

Pre authorize, 1 operation

  • pre_authorize_tokenizationPre authorize tokenizationPOSTPre-authorizes an amount in cents on a tokenization; the answer shows status reserved.

Qr code scan, 1 operation

  • delete_qr_code_scanDelete qr code scanDELETEDeletes a QR code scan by its session id (used with static Twint QR codes, whose scan session id is passed to create_gateway as qrCodeSessionId).

Receipt, 1 operation

  • send_transaction_receiptSend transaction receiptPOSTEmails the receipt of a transaction to the given address.

Signature check, 1 operation

  • check_credentialsCheck credentialsGETChecks whether Payrexx accepts the request's authentication for the instance; status success means the instance name and API secret work.

Update tokenization, 1 operation

  • update_tokenizationUpdate tokenizationPATCHChanges the VAT rate (percent) of a tokenization.

Void, 1 operation

  • void_terminal_paymentVoid terminal paymentPOSTVoids (reverses) a terminal payment.

Use Payrexx from Claude Code, Cursor or Codex

Connect Payrexx in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Payrexx operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Payrexx

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Payrexx once

    Add your Payrexx connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Payrexx integration FAQ

What can you do with the Payrexx integration?

LiveContext exposes 49 operations on Payrexx, covering bill, subscription, transaction and design.

Popular integrations

Browse the whole catalog