Payrexx

Payrexx is a Swiss online payment gateway with paylinks, gateways, and card terminals. Agents create gateways and paylinks, charge, capture, and refund transactions, tokenize cards, run subscriptions, issue merchant invoices, and drive ECR terminals.

Verified 59 actions API key available

Payrexx website Platform Documentation Capability data verified 2026-08-25

A customer comes back to the counter asking for money back on a card payment taken there

List Transactions and Get Transaction find the original sale and report its current status

Get Terminal Pairing confirms the device is still paired, and the terminal family decides which reversals exist at all

Agent works out whether the sale is still unsettled, which is what separates a clean void from a refund

The available options and the amount at stake are posted to the counter tablet

The supervisor picks void, full refund, or a manual credit, and the agent runs only the option they chose

What This Integration Enables

Payrexx is a Swiss gateway that reaches both sides of the counter. The same instance issues hosted checkouts and emailed paylinks, runs standing storefront and donation pages, raises numbered merchant invoices, and drives physical ECR card terminals, with TWINT and Swiss QR codes treated as first-class payment surfaces rather than afterthoughts. FlowRunner agents create the checkout, watch the transaction, settle or reverse it, run the subscription behind it, and reconcile the payout that eventually reaches the bank.

Reaching both sides is also where the sharp edges are, because the same word means different things in different places. A reservation is released, a confirmed charge is refunded, an abandoned checkout is canceled, and a terminal sale is voided only while it is unsettled. FlowRunner agents can carry those distinctions correctly at machine speed. What they do not do is decide which one a customer standing at the counter is owed. That call reaches a person, which is the human-in-the-loop default this platform ships with rather than a workflow you have to remember to build.

Without FlowRunner

Refund rules live in someone's head Whether a void, a full refund, or neither is available depends on the hardware and on how long ago the sale settled

Two ledgers to reconcile Counter takings and web checkout takings arrive separately and get matched by hand

Deposits arrive as one number A payout lands in the bank with no breakdown of which orders it settled

With FlowRunner

The constraint is stated before the promise The agent reports which reversal the terminal actually supports before anyone tells a customer what will happen

One transaction ledger Gateways, paylinks, pages, subscriptions, and terminal taps all resolve to the same transaction record

Deposits tied back to orders Payout details name the individual transactions behind a deposit, so the bank line reconciles to sales

Use Case Scenarios

A printed QR code that becomes a real amount

A market stall or a table tent carries a printed Payrexx QR code. A customer scans it, and Payrexx records the scan with its own session id. The agent picks that session up, works out what this particular customer owes from the open order in Shopify or the point of sale record, and calls Create Gateway carrying the scan's session id so the static code becomes a checkout for a specific amount. If the order is canceled before the customer pays, Delete QR Code Scan releases the pending scan rather than leaving their phone waiting on a payment that is never coming.
Request to pay, then reconcile the deposit

An invoice is approved upstream. The agent decides which object fits: Create Paylink for a hosted page that can carry an expiry date and attachments, or Create Invoice for a real numbered bill with line items, terms, and reminders that finance can put in the ledger. Either way the link goes out, and the transaction that results is watched rather than assumed. Later, when Payrexx pays the collected money into the bank, Get Payout Details lists the individual transactions inside that deposit, and the agent writes them back to Xero so a single bank line resolves into the orders that produced it.
Subscription billing without a password

A recurring customer needs to change something. Rather than building a portal, the agent calls Create Subscriber Login Link, which issues a short-lived token and a URL that logs that subscriber straight into their own subscription view. The link is generated at the moment it is sent, because the token carries its own expiry. Where the change is a price rather than a card, Update Subscription applies it, and the agent tells the customer plainly that the new amount takes effect on the next interval rather than the current one, because that is what Payrexx actually does.

Human-in-Loop Highlight

Refund Terminal Payment is the operation that will not do what a counter conversation assumes. Payrexx supports two terminal families and they behave differently. On a NexGo device the vendor has not implemented terminal refunds at all, and the call answers 501. On a Newland device the refund routes through the same reversal mechanism as a void, so only a full refund works and a smaller amount is rejected. Neither family can give a customer back part of their money through this route. So when a customer asks for a partial refund at the counter, the agent does not attempt it and report a failure afterwards. It posts to the supervisor's tablet: "Terminal N910-04, sale CHF 148.00 taken 11:42 today, still unsettled. Void for the full CHF 148.00 is available now. Partial refund is not supported on this device. Void and re-charge CHF 96.00, or handle the CHF 52.00 difference as a manual credit?" The supervisor answers, the customer gets a straight answer at the counter rather than a call back, and the agent runs exactly one of the two paths.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

59 actions

Account

Check Credentials Confirms the instance name and API secret are accepted. It reads and changes nothing, which makes it the cheapest way to tell a wrong credential from a missing record.

Gateways

Create Gateway Creates a hosted checkout and returns the link to send a customer to. Pre-authorization and reservation both produce a checkout that holds money without taking it.
Get Gateway Reads a gateway's status, its checkout link, the contact fields it collects, and any invoices raised against it.
Delete Gateway Deletes a gateway and invalidates its checkout link. Payments already taken through it are untouched.

Transactions

List Transactions Lists the actual money movements behind gateways, paylinks, pages, and subscriptions, with a filter that separates traffic created by this key from the instance's own.
Get Transaction Reads one transaction in full: status, amount, payment method and brand, the contact captured at checkout, and the provider that processed it.
Charge Transaction Takes the money on a transaction that was authorized or reserved, in full or in part.
Capture Transaction Settles the full authorized amount on a transaction sitting in authorized status.
Refund Transaction Refunds a confirmed transaction, in full or in part. A refund can come back pending, so status matters more than the call succeeding.
Delete Transaction Releases a reservation or removes a tokenization, freeing a hold on the customer's card. Not a refund.
Cancel Transaction Cancels a transaction still in waiting status, which is the checkout a customer opened and never finished.
Pre-Authorize Tokenization Places a new authorization on an already tokenized card with the customer absent, which is the merchant-initiated half of tokenization.
Update Pre-Authorization Changes the amount held by an existing pre-authorization when an order total moves before settlement.
Update Tokenization Changes the VAT rate recorded on a tokenization so later charges against the stored card carry the right rate.
Update Transaction Contact Replaces the contact details stored on a pre-authorization or tokenization. The field set replaces rather than merges.
Send Transaction Receipt Emails a receipt to any address, which is how a copy reaches accounts payable or a bounced address gets a second attempt.

Subscriptions

Create Subscription Creates a subscription for a contact who has already paid once on this instance, since it collects no payment method of its own.
List Subscriptions Lists subscriptions with status, start and end dates, billing interval, and the invoice attached to each.
Get Subscription Reads one subscription with its dates, validity, interval, and invoice.
Update Subscription Changes a subscription's amount, currency, purpose, or VAT rate. The new amount applies from the next interval, not the current one.
Cancel Subscription Stops further intervals billing. The record stays readable with its status set to cancelled, and money already collected is not returned.
Create Subscriber Login Link Issues a token and a URL that logs a subscriber into their own subscription view without a password. Generate it when you send it, because it expires.

Paylinks

Create Paylink Creates a hosted payment page with its own title, description, and contact form. Unlike a gateway it can carry an expiry and file attachments, which is what an emailed request to pay needs.
Get Paylink Reads a paylink's status, its link, the reference you gave it, and the transactions raised against it.
Delete Paylink Stops a paylink working. Payments already taken through it are unaffected.

Invoices

Create Invoice Creates a real numbered merchant invoice with line items, terms, and reminders. Leave it in draft for review, complete it to finalize numbering, or send it to email the recipient.
List Invoices Lists merchant invoices with status, payment status, number, date, and total.
Get Invoice Reads one invoice. Document status covers the lifecycle, payment status covers the money, and they are not the same question.
Update Invoice Updates an invoice. Positions replace the whole line item set, so send every line you intend to keep.
Delete Invoice Deletes a merchant invoice.

Payouts

List Payouts Lists the transfers of collected money to your bank account, each with its amount, fees, and whether it is live or test.
Get Payout Reads one payout's summary figures.
Get Payout Details Reads a payout together with the individual transactions it settled, which is what reconciles a bank deposit to orders.
Create Manual Payout Moves collected money to the bank on demand rather than on the automatic schedule. It has to be enabled for the instance by Payrexx first.

Payment Discovery

List Payment Providers Lists the payment service providers configured on the instance, with the methods each carries and, where supported, its balance.
List Payment Methods Lists the methods currently active, filtered by payment type. A method that works for a one-time charge may not support a subscription or a reservation.
Get Payment Method Reads one payment method with its translated labels and logos.

QR Codes

Create QR Code Creates a static QR code that sends a scanner to a webshop URL and records the scan with a session id.
Get QR Code Reads one QR code with the URL it points at and the scans recorded against it.
Delete QR Code Deletes a QR code, which stops any printed copies working.
Delete QR Code Scan Discards a recorded scan without charging anything, so a customer's phone is not left waiting on a payment the flow decided against.

Designs

List Designs Lists the look and feel designs controlling how checkouts, paylinks, and invoices render.
Create Design Creates a design. Colors are hex codes without the leading hash, and images are set in the Payrexx administration rather than here.
Update Design Updates a design. Name is required on every update, so pass the current value through when it is not changing.
Get Design Reads one design with every color, font, and image setting on it.
Delete Design Deletes a design. Anything that referenced it falls back to the instance default.

Terminals

Pair Terminal Pairs a card terminal with the instance so it can be driven from a flow. NexGo devices need the pairing code on their screen, Newland devices authorize from stored credentials.
Get Terminal Pairing Reads whether a terminal is currently paired. Worth calling before pushing a payment, because an unpaired device simply does not respond.
Unpair Terminal Unpairs a terminal, after which it no longer accepts payments pushed from a flow.
Start Terminal Payment Pushes a payment onto a paired terminal so the customer taps or inserts their card there. Tip is added to the total rather than contained in it.
Get Terminal Payment Reads the state of a payment running on a terminal, which is how a flow learns whether the customer completed, canceled, or failed the tap.
Cancel Terminal Payment Clears a payment the terminal is still prompting for. It applies only before completion.
Void Terminal Payment Reverses a completed terminal payment before it settles, so the charge never reaches the customer's statement.
Refund Terminal Payment Refunds a completed terminal payment, with sharply different behavior per terminal family. This is the operation this page's human gate exists for.
List Terminal Payment Methods Lists the methods a terminal can take. It answers for NexGo devices only, and a Newland device returns an empty list as a limitation rather than a configuration.
Get Terminal Config Reads a terminal's currency, tipping behavior, receipt printing, and accepted methods. It currently answers with defaults on both families and is shipped because the route is published.

Frequently Asked Questions

What can FlowRunner do with Payrexx?

FlowRunner agents can run Check Credentials, Create Gateway, and Get Gateway in Payrexx, plus 56 more actions.

Does connecting Payrexx to FlowRunner require OAuth?

No. Payrexx connects to FlowRunner with an API key, no OAuth flow required.

Can Payrexx trigger a FlowRunner workflow automatically?

Payrexx doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Payrexx

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us