Resources · Make integration

Payrexx Make integrationAutomate Payrexx with Make.

What if every Payrexx payment could update the rest of your tools on its own? The Payrexx Make integration gives you 36 modules, including 3 instant triggers. This page shows how to link your account, build a first scenario and pick the right module for each job.

Try the Payrexx integration on MakeSee the 36 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Payrexx Make integration do for you?

The Payrexx Make integration links your Payrexx merchant account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Payrexx events can start a scenario, and Make can create, read, update or delete invoices, paylinks, subscriptions and transactions for you.

Payouts that land in your books. Watch Payouts starts a scenario whenever Payrexx makes a new payout. Add Retrieve a Payout with details and your finance sheet gets the full picture without anyone copying numbers from the dashboard.

Paylinks created from your orders. A quote accepted in your CRM can feed Create a Paylink, so the customer gets a payment page right away. Create an Invoice and Create a QR Code cover the same need when you prefer an invoice or a code printed on a flyer.

Subscriptions kept in step. Watch Subscriptions reacts to every new or changed subscription, and Update a Subscription changes amount, currency, purpose or VAT rate when your pricing table moves. Login a Subscription Customer sends members a link to manage their plan themselves.

The Make documentation for Payrexx lists no specific limit, and it flags its own content as AI-generated: check important details with Payrexx. For anything the 36 modules skip, Make an API Call reaches the rest of the Payrexx API. If you are still weighing tools, the n8n vs Make comparison sets out the criteria, and the Make pricing guide explains how operations are counted.

Connect

How do you connect Payrexx to Make?

  1. 01

    Create an API key in Payrexx

    In the Payrexx merchant dashboard, open API and Plugins and click Add API Key. Give the instance a name you will recognize, click Add, then copy the key that appears in the list.

  2. 02

    Add a Payrexx module in Make

    In your scenario, search for Payrexx, pick any module and click Create a connection. A connection is your Payrexx account linked to Make once, then reused by every Payrexx module you add later.

  3. 03

    Paste your credentials

    Type a label in Connection name if you run several Payrexx accounts; it is optional. Paste the credentials copied from Payrexx, or follow the instructions on screen, and save. Make can now read and write in your account.

First scenario

Your first scenario with Payrexx

GoalWhen Payrexx makes a new payout, Make fetches that payout with its full details so you can pass them to your accounting.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + to place the first module. This first module is the one that starts everything.

  2. 02

    Add Watch Payouts

    Search for Payrexx and choose Watch Payouts. Click Create a webhook, then Create a connection and paste your API key. The lightning badge tells you Payrexx will call Make itself.

  3. 03

    Chain Retrieve a Payout with details

    Click the + on the right of the trigger and pick Retrieve a Payout with details. For the payout ID, map the identifier that Watch Payouts received, so each run looks up the right payout.

  4. 04

    Test with Run once

    Click Run once, then wait for a payout in Payrexx. Read the bundles each module received and check that the details match your dashboard.

  5. 05

    Switch the scenario on

    Turn the scenario on. Because the trigger is instant, it runs whenever Payrexx sends a payout instead of waiting for the 15 minutes default schedule of polling triggers.

Triggers

Payrexx triggers in Make

3 modules start a scenario when something happens in Payrexx. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Payrexx as soon as it happens.

Payrexx1Watch Payouts

Watch Payouts

Instant trigger

In Make“Receives Payout information on every new payout made”

Every new payout from Payrexx starts your scenario, and its information travels to the next module as a bundle, meaning one item passed along the chain. You get a clean entry point for bookkeeping without opening the merchant dashboard.

How it fires
instant. Payrexx calls Make through a webhook as soon as the payout happens, which is why the module carries a lightning badge.
When to use it
your accountant wants each payout logged in a spreadsheet or finance tool the moment it leaves Payrexx.
Watch out
click Create a webhook before Create a connection, or the trigger never hears from Payrexx.
Payrexx2Watch Subscriptions

Watch Subscriptions

Instant trigger

In Make“Receives Subscription information on every new or changed Subscription”

This trigger keeps you informed about recurring customers: it hands your scenario the subscription data whenever one is created or changed in Payrexx. Your member list or CRM can follow along without manual exports.

How it fires
instant. Payrexx warns Make through a webhook as soon as the subscription is created or edited.
When to use it
a gym or online course tags a contact as active the day a member signs up, and updates the record when the plan changes.
Watch out
changes fire too, so the same subscription can reach the scenario several times; update the existing record rather than creating a new one each time.
Payrexx3Watch Transactions

Watch Transactions

Instant trigger

In Make“Receives Transaction information on every new or changed transaction”

Payments are where most Payrexx automations begin, and this trigger delivers each new or changed transaction to your scenario. From there you can ship an order, thank a buyer or alert your team.

How it fires
instant. Payrexx calls Make through a webhook as soon as the transaction appears or changes.
When to use it
an online shop that prepares a parcel only once the payment has come through in Payrexx.
Watch out
a transaction that changes after creation comes back as a second bundle, so plan what your scenario does on repeat before sending emails or creating records.
Modules

What the Payrexx modules do

Payrexx gives you 33 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Payrexx1

Cancel a Waiting Transaction

Action

In Make“Cancel a waiting transaction by ID”

Closes a Payrexx transaction that is still waiting, so an abandoned or cancelled order does not stay open in your account. You only need its ID.

When to use it
a customer cancels an order in your shop before paying, and you want Payrexx to reflect that straight away.
Watch out
the ID usually comes from Watch Transactions or Retrieve Transactions earlier in the scenario, so place one of them first.
Payrexx2

Charge a Pre-Authorized/Reserved Transaction

Action

In Make“Debit an amount based on a previous Tokenisation or Reservation by the previous Transation ID”

With this module you collect money that was set aside earlier: it debits an amount on the basis of a previous tokenization or reservation, referenced by that transaction ID.

When to use it
a rental business reserves an amount at booking and charges it when the equipment comes back.
Watch out
keep the ID of the original reservation somewhere your scenario can read, a sheet or a CRM field, since the charge depends on it.
Payrexx3

Create a Cash Transaction

Action

In Make“Create a new cash transaction which will be added to the transaction history in your Payrexx account”

Records money received in cash inside Payrexx, so the transaction history in your account covers every sale and not only card payments.

When to use it
a shop takes cash at a market stall and logs each sale in a form; Make turns every form entry into a cash transaction.
Watch out
this module writes to your real history, so test on a single entry with Run once before letting a whole list through.
Payrexx4

Create a Manual Payout

Action

In Make“Create a new Manual Payout”

Triggers a payout by hand instead of waiting for the regular one, straight from a scenario. It gives finance teams a button they can press from their own tools.

When to use it
someone approves a payout request in a project board or a form, and Make sends the order to Payrexx.
Watch out
money moves for real; add an approval step before this module rather than running it on every event.
Payrexx5

Create a New Subscription

Action

In Make“Create a new subscription which will be recurringly billed to the user you provide”

Sets up a subscription that Payrexx will bill on a recurring basis to the customer you provide. You skip the dashboard and start billing from the tool where the deal was closed.

When to use it
a signed membership form or a won deal in your CRM should start the recurring payment automatically.
Watch out
check that the scenario cannot run twice for the same signup, or the customer ends up with two subscriptions.
Payrexx6

Create an Invoice

Action

In Make“Create a New Payrexx Invoice”

Produces a new Payrexx invoice from data already sitting in another app, so nobody retypes names and amounts. The invoice lives in Payrexx like any invoice created by hand.

When to use it
a consultant logs a finished job in a spreadsheet row, and the matching invoice is created in Payrexx.
Watch out
map the amount and customer carefully during the first Run once, then compare the result with an invoice you made yourself.
Payrexx8

Create a QR Code

Action

In Make“Create a new QR Code”

Makes a new Payrexx QR code that people can scan to pay, and returns it to the scenario so you can place it wherever it is needed.

When to use it
an event organizer creates one code per stand or per ticket batch listed in a spreadsheet.
Watch out
each QR code gets a UUID; store it next to the code if you plan to retrieve or delete it later with the other QR modules.
Payrexx9

Create Gateway

Action

In Make“Create a new Payment Gateway”

Builds a new payment gateway in Payrexx, the checkout that collects a given payment, directly from your scenario data.

When to use it
your booking tool needs a dedicated checkout for each reservation, created when the booking is confirmed.
Watch out
keep the gateway ID in your records; Retrieve a Gateway and Delete a Gateway both work from it.
Payrexx10

Delete a Gateway

Action

In Make“Delete a Payment Gateway by ID”

Removes a payment gateway by its ID so old checkouts do not pile up in your Payrexx account once they have served their purpose.

When to use it
a booking is cancelled in your scheduling tool and its dedicated checkout should disappear with it.
Watch out
a deletion cannot be undone from Make; test on a gateway you created for the purpose before mapping real IDs.
Payrexx11

Delete an Invoice

Action

In Make“Delete an Invoice by ID”

Erases a Payrexx invoice by its ID, keeping your invoice list in line with what really happened in your sales tool.

When to use it
a draft order is abandoned in your shop and the invoice created for it was never meant to be paid.
Watch out
nothing brings the invoice back afterwards, so double-check which IDs reach this module when the scenario handles many invoices.
Payrexx13

Delete a QR Code

Action

In Make“Delete a QR Code by UUID”

Retires a Payrexx QR code identified by its UUID, useful once a campaign or an event is over and the code should stop accepting payments.

When to use it
an event ends and every code created for its stands should be cleaned up from a list.
Watch out
codes already printed stay on paper, so take them down when you retire the code in Payrexx.
Payrexx14

Delete a QR Code Scan

Action

In Make“Delete a QR Code Scan by Session ID”

Removes a single scan of a QR code, found by its session ID, rather than the code itself. The code keeps working for everyone else.

When to use it
a test scan made during setup should not stay in the data you later review.
Watch out
this module needs the session ID of the scan, not the UUID of the code; the two are easy to mix up when mapping.
Payrexx15

Delete a Reserved Transaction

Action

In Make“Delete a Reserved Transaction by ID”

Drops a reserved transaction by its ID, releasing a reservation you no longer intend to charge.

When to use it
rented equipment comes back undamaged and the deposit held at booking should simply be cleared.
Watch out
once deleted, the reservation cannot be charged with Charge a Pre-Authorized/Reserved Transaction, so settle which of the two modules fits before you map the ID.
Payrexx16

Delete a Subscription

Action

In Make“Delete a subscription by ID”

Ends a Payrexx subscription by its ID, so recurring billing stops when a customer leaves.

When to use it
a cancellation request arrives through your help desk or a form, and the subscription should go without anyone logging in to Payrexx.
Watch out
when only the price or VAT changes, reach for Update a Subscription instead; deleting forces you to set everything up again.
Payrexx17

Login a Subscription Customer

Action

In Make“Create a new authentication link for your subscription users to login and manage their subscriptions”

Produces an authentication link that lets a subscriber log in and manage their own subscription, which saves your team many small support requests.

When to use it
a member asks your support inbox how to change their plan, and the reply includes a fresh link created by Make.
Watch out
the module returns the link only; send it through an email or chat module placed right after.
Payrexx18

Make an API Call

Action

In Make“Make a custom API Call to the Payrexx Rest API”

Reaches any endpoint of the Payrexx REST API with the connection you already set up. It is the way to cover a need the listed modules do not handle.

When to use it
you need a Payrexx feature missing from the module list and do not want a second tool for it.
Watch out
you write the request yourself, so keep the Payrexx API reference open and test with Run once before going live.
Payrexx19

Refund a Transaction

Action

In Make“Create a new refund for a previoulsy made Transaction by ID”

Sends money back on a transaction that was already paid, identified by its ID, without anyone opening the Payrexx dashboard.

When to use it
a return is approved in your shop or help desk, and the buyer should get the refund as soon as the decision is made.
Watch out
a refund is real money; keep a human approval step before this module and log each refund in a sheet.
Payrexx20

Retrieve a Gateway

Action

In Make“Retrieve a Payment Gateway by ID”

Reads one payment gateway by its ID and returns what Payrexx knows about it, so the next modules can act on current data.

When to use it
before reminding a client, you check the state of the checkout created for their booking.
Watch out
this module looks up one gateway at a time; it does not list gateways, so you must already hold the ID.
Payrexx21

Retrieve an Invoice

Action

In Make“Retrieve an Invoice by ID”

Fetches one Payrexx invoice by its ID when you need its current content in the middle of a scenario.

When to use it
a customer writes about a bill, and your help desk ticket gets the invoice data attached automatically.
Watch out
without an ID, use Retrieve Invoices to search the list first, then pass the right ID to this module.
Payrexx23

Retrieve a Payout with details

Action

In Make“Retrieve a Payout by ID with detailled information”

Returns a payout by its ID together with its detailed information, which is what reconciliation work usually needs.

When to use it
right after Watch Payouts, to push the full breakdown of each payout into your accounting sheet.
Watch out
if a summary is enough, the lighter Retrieve a Payout without Details keeps the bundle smaller and easier to map.
Payrexx24

Retrieve a Payout without Details

Action

In Make“Retrieve a Payout by ID without detailled information”

Gets a payout by its ID in a short form, without the detailed information, for when you only need the headline data.

When to use it
a team chat message announcing each payout needs the essentials, not every line behind it.
Watch out
for reconciliation, pick Retrieve a Payout with details instead; the short version leaves out the breakdown.
Payrexx25

Retrieve a QR Code

Action

In Make“Retrieve a QR Code by UUID”

Reads one Payrexx QR code from its UUID, so a scenario can check or reuse a code that already exists.

When to use it
a partner asks for the code of their stand again, and Make fetches it from the UUID stored in your sheet.
Watch out
a QR code is identified by UUID, not by an ID like invoices; map the right field.
Payrexx26

Retrieve a Transaction

Action

In Make“Retrieve a Transaction by ID”

Brings back one transaction by its ID so you can read its latest state before acting on it.

When to use it
before shipping a high-value order, the scenario confirms the payment one more time in Payrexx.
Watch out
to find transactions without knowing the ID, start with Retrieve Transactions, which returns several bundles.
Payrexx27

Send a Transaction Mail Receipt

Action

In Make“Send a receipt by E-Mail for a transaction”

Asks Payrexx to email a receipt for a transaction, so the buyer gets proof of payment without you writing the message.

When to use it
after Watch Transactions, when a buyer asks for proof of payment again, or when your scenario should confirm each paid transaction by email.
Watch out
Watch Transactions also fires on changed transactions, so guard against sending the same receipt twice.
Payrexx28

Update an Invoice

Action

In Make“Update an Invoice by ID”

Changes an existing Payrexx invoice by its ID, which keeps the invoice aligned when the order behind it evolves.

When to use it
a customer adds a service to an order in your CRM and the invoice should follow before they pay.
Watch out
run a test on one invoice first and compare it with the original before letting the scenario touch real bills.
Payrexx29

Update a Subscription

Action

In Make“Change existing subscription configuration like amount, currency, purpose or vat rate”

Adjusts an existing subscription, such as its amount, currency, purpose or VAT rate, without ending it and starting over.

When to use it
your price list changes and every affected member should move to the new amount from one sheet.
Watch out
test on a single subscription first; a wrong mapping here changes what real customers pay.
Payrexx30

Update Pre-Authorization/Tokenization Contact Details

Action

In Make“Update the contact details of a Pre-Authorization or Tokenization transaction”

Corrects the contact details attached to a pre-authorization or tokenization transaction, so Payrexx holds the same details as your other tools.

When to use it
a client updates their address or email in your CRM after a card was saved, and Payrexx should hold the same data.
Watch out
this only touches contact details; to charge the reserved amount, use Charge a Pre-Authorized/Reserved Transaction.
Payrexx31

Retrieve Invoices

Search

In Make“List all Invoices”

Lists the invoices in your Payrexx account and returns them as separate bundles, one per invoice, ready for the next module.

When to use it
an end-of-period export of all invoices into a spreadsheet for your accountant.
Watch out
as a search, it can return zero, one or many bundles, and every module after it runs once per invoice, each run counting as an operation.
Payrexx32

Retrieve Payouts

Search

In Make“Retrieve a list of Payouts made in your Payrexx account”

Pulls the list of payouts made in your Payrexx account, handy when you want past payouts and not only the next one.

When to use it
you connect Payrexx to Make for the first time and want to backfill a finance sheet with earlier payouts.
Watch out
each payout becomes one bundle, so a long history uses many operations in the modules that follow.
Payrexx33

Retrieve Transactions

Search

In Make“Retrieve Transactions made through Payrexx”

Searches the transactions made through Payrexx and hands them over one bundle at a time for sorting, reporting or checks.

When to use it
a sales report on demand, or finding the transaction ID you need for a refund or a cancellation.
Watch out
an empty result is possible; the scenario simply stops there, which is worth knowing when a run seems to do nothing.
Need help

Need help automating Payrexx with Make?

A person reads every message.

FAQ

Payrexx and Make: frequent questions

01Is the Payrexx Make integration free?
Yes, Payrexx is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations each month, one per module run on one bundle. You still need a Payrexx account, which follows its own pricing.
02What do you need to connect Payrexx to Make?
An active Payrexx account and an API key. In the Payrexx merchant dashboard, open API and Plugins, click Add API Key, name the instance, click Add and copy the key from the list. In Make, add any Payrexx module, click Create a connection, optionally fill Connection name, and paste the key. For the three Watch modules, Make asks you to click Create a webhook before Create a connection. The same connection then serves every Payrexx module in your scenarios.
03Do Payrexx triggers in Make fire in real time?
Yes. Watch Payouts, Watch Subscriptions and Watch Transactions are all instant triggers: Payrexx calls Make through a webhook as soon as the event happens, and the module shows a lightning badge. There is no polling interval to wait for, unlike scheduled triggers that run every 15 minutes by default on a new scenario. Keep in mind that Watch Subscriptions and Watch Transactions also fire when an existing item changes, so one subscription or payment can reach your scenario more than once.
04What if a Payrexx module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Payrexx REST API with the connection you already created, so you can reach features the 36 listed modules do not cover. You write the request yourself from the Payrexx API documentation, then test it with Run once. The Make documentation for Payrexx gives no specific limit, but it states that its content is AI-generated and may contain mistakes, so check important details directly with Payrexx before relying on them.
05Make or n8n for Payrexx?
It depends on the tool your team already uses. On Make, Payrexx comes with 36 modules, including 3 instant triggers, an API call module and a visual editor where each run can be tested with Run once. Many apps also have an n8n node, so check whether one exists for Payrexx and which operations it offers before deciding. Compare the two on the modules you actually need, the way usage is counted and who will maintain the scenarios. The n8n vs Make comparison linked above sets out those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations