Resources · Make integration

OxaPay Crypto Payment Gateway Make integrationAutomate OxaPay Crypto Payment Gateway with Make.

Crypto payments coming in, and nobody wants to copy them by hand? The OxaPay Crypto Payment Gateway Make integration offers 28 modules: 2 triggers, 22 actions and 4 searches. This guide shows merchants how to link the account and build a first working scenario.

Try the OxaPay Crypto Payment Gateway integration on MakeSee the 28 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the OxaPay Crypto Payment Gateway Make integration do?

The OxaPay Crypto Payment Gateway Make integration links your OxaPay merchant account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. OxaPay can then create invoices, send payouts or report balances while you look after the rest of the business.

Invoices created from your order flow. When a sale is confirmed in another app, Generate an invoice asks OxaPay for a crypto invoice, and the next module can send it to the buyer. No more opening the OxaPay dashboard for every order.

A payment log kept up to date. Watch payment webhook starts the scenario for each payment it picks up, Get the payment information reads the details, and a sheet or CRM module stores them. Each payment travels as one bundle, the unit of data Make hands from one module to the next.

Payouts with a paper trail. Generate a payout sends funds out, and Search payouts finds earlier ones when accounting asks a question.

Keep one limit in mind: the Make documentation for this app is marked as AI-generated from the OxaPay docs, and it may contain mistakes. Check anything important with OxaPay, and run every money-moving step on a test first. The app has no generic Make an API Call module either, so you work with the 28 modules listed below.

New to Make? The Make review covers the basics, the Make pricing guide explains credits, and the n8n vs Make comparison helps if you are still choosing a tool.

Connect

How do you connect OxaPay Crypto Payment Gateway to Make?

  1. 01

    Generate your Merchant API Key

    In OxaPay, open the Merchant Service section, fill in the form it shows, then click Generate Merchant API Key. Copy the key that appears on screen. You need an active OxaPay merchant account for this.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any OxaPay Crypto Payment Gateway module and click Create a connection. A connection is your OxaPay account linked to Make once, then reused by every OxaPay module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps if you run several merchant accounts. Paste the API key you copied, or follow the on-screen instructions, and save. Make now lists what it can read from OxaPay.

First scenario

Your first scenario: log each OxaPay payment

GoalWhen OxaPay records a payment, Make fetches its full details and passes them to the next app.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, click Create a new scenario, then click the big + to place the first module on the canvas.

  2. 02

    Add the payment trigger

    Search for OxaPay Crypto Payment Gateway, pick Watch payment webhook, and choose your connection or create one with the Merchant API Key you generated earlier.

  3. 03

    Fetch the payment details

    Click the + on the right of the trigger and add Get the payment information. Map the payment data coming from the trigger into its fields, so each run reads the right payment.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open them to check that the payment you expected is really there.

  5. 05

    Schedule it and switch it on

    Click the clock on the first module to set the schedule. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan. Then turn the scenario on.

Triggers

What can start an OxaPay scenario?

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

OxaPay Crypto Payment Gateway1Watch payment webhook

Watch payment webhook

triggerIn the docs only

This trigger is the starting point for anything tied to incoming money: each payment it picks up becomes a bundle that the rest of your scenario can process, one at a time.

How it fires
scheduled, so Make checks OxaPay on the scenario's schedule, every 15 minutes by default, and then processes what it found.
When to use it
you want every paid order recorded in your books or announced to your team without logging in to OxaPay.
Watch out
the scheduled type in this page comes from the module name, because the Make directory was unavailable, so look at the badge on the module in the editor before you rely on timing.
OxaPay Crypto Payment Gateway2Watch payout webhook

Watch payout webhook

triggerIn the docs only

Outgoing money gets its own watcher here. Each payout the module picks up enters the scenario as a bundle, which lets you confirm, log or report on transfers you sent from OxaPay.

How it fires
scheduled, meaning Make checks the app on the scenario's schedule rather than waiting for OxaPay to call it.
When to use it
finance needs a line in a spreadsheet each time a supplier or partner is paid out.
Watch out
the scheduled type was inferred from the module name, so the badge in the editor is the final word. Each check uses an operation, one run of a module, counted on your plan.
Modules

Every OxaPay module, and when to reach for it

OxaPay Crypto Payment Gateway gives you 26 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

OxaPay Crypto Payment Gateway1

Calculate a swap

ActionIn the docs only

Here you get a quote before any money moves: the module works out what a swap between two cryptocurrencies would give you, without placing it.

When to use it
a buyer asks what they would receive, or you want to check the result before calling Generate a swap request.
Watch out
a quote is not a trade, so pair it with the request module when you actually want to swap.
OxaPay Crypto Payment Gateway2

Generate a payout

ActionIn the docs only

Sending crypto out of your OxaPay balance becomes one step of a scenario with this action, which creates the payout for you.

When to use it
an affiliate commission or a refund has been approved in another app and should be paid without a manual login.
Watch out
this moves real funds, so test it on a small internal case with Run once before switching the scenario on.
OxaPay Crypto Payment Gateway3

Generate a static address

ActionIn the docs only

A static address gives a customer a fixed place to send crypto, and this action creates one from your scenario instead of the dashboard.

When to use it
a new client account is opened in your CRM and needs its own deposit address stored on the record.
Watch out
save the address in the next module, otherwise you will have to look it up later with Search static address.
OxaPay Crypto Payment Gateway4

Generate a swap request

ActionIn the docs only

Once a quote looks right, this action places the swap itself, turning one currency in your OxaPay account into another.

When to use it
your treasury rule says received coins should be converted as soon as a payment is confirmed.
Watch out
put Calculate a swap or Get the swap rate just before it, and a filter between them, so the scenario only swaps when the numbers suit you.
OxaPay Crypto Payment Gateway5

Generate a white label

ActionIn the docs only

As the name suggests, this action generates a white label payment, meant to be shown under your own brand rather than on an OxaPay page. What it returns exactly is not documented here.

When to use it
your store or app has its own payment screen and you want the address and amount without sending buyers elsewhere.
Watch out
the page has no field list for this module, so open it in Make and read what it asks before mapping data.
OxaPay Crypto Payment Gateway6

Generate an invoice

ActionIn the docs only

An order turns into a crypto payment request with this action: it creates an OxaPay invoice you can pass to the buyer.

When to use it
a deal is marked won in your CRM or an order lands in your store, and the customer should get a way to pay in crypto.
Watch out
follow it with an email or messaging module, because creating the invoice does not by itself put it in front of the buyer.
OxaPay Crypto Payment Gateway7

Get accepted currencies

ActionIn the docs only

Your own settings come back here. The module lists the currencies your merchant account currently accepts for payment, so you work from what is switched on today.

When to use it
before you show payment options on a site or in a message, so buyers only see coins you really take.
Watch out
do not mix it up with Get supported currencies, which describes what OxaPay handles in general, not what you switched on.
OxaPay Crypto Payment Gateway8

Get prices

ActionIn the docs only

Current prices from OxaPay land in your scenario with this action, ready to be written to a sheet or used in a calculation.

When to use it
you want a price shown next to an order, or a record of the rate at the moment a payment arrived.
Watch out
prices move, so read them in the same run as the step that uses them rather than storing them for later.
OxaPay Crypto Payment Gateway9

Get supported currencies

ActionIn the docs only

This one answers a broad question: which cryptocurrencies OxaPay itself supports, whatever your account settings are.

When to use it
you are planning to accept a new coin and want to check it is available before changing anything.
Watch out
a supported currency is not necessarily accepted on your account; Get accepted currencies gives that second answer.
OxaPay Crypto Payment Gateway10

Get supported fiat currencies

ActionIn the docs only

Pricing in dollars, euros or another national currency starts here: the module returns the fiat currencies OxaPay supports.

When to use it
your shop sells in a local currency and you want to confirm OxaPay can express invoices in it.
Watch out
the result is a reference list, useful at setup; there is little point running it inside every scenario run.
OxaPay Crypto Payment Gateway11

Get supported networks

ActionIn the docs only

Many coins travel on more than one blockchain network, and this module tells you which networks OxaPay works with.

When to use it
a customer asks whether they can pay on a given network, or you build a payout and need to pick the right one.
Watch out
sending on the wrong network is a classic crypto mistake, so check this list before you map a network into a payout.
OxaPay Crypto Payment Gateway12

Get swap pairs

ActionIn the docs only

Not every coin can be swapped into every other, and this action returns the pairs OxaPay allows.

When to use it
before building an automatic conversion, to be sure the pair you have in mind exists.
Watch out
a swap request on a pair that is not listed will fail, so check here first rather than debugging the swap module later.
OxaPay Crypto Payment Gateway13

Get the account balances

ActionIn the docs only

What you hold in OxaPay, currency by currency, comes back from this module so another app can display or store it.

When to use it
a payout is about to go out and you want the scenario to confirm the funds are there first.
Watch out
balances change with every payment and payout, so read them right before the step that depends on them.
OxaPay Crypto Payment Gateway14

Get the payment information

ActionIn the docs only

One payment, fully described: give this module a payment reference and it returns what OxaPay knows about that payment.

When to use it
right after Watch payment webhook, or when a customer writes in about an order and support needs the status.
Watch out
it reads a single payment; to find several at once, Search payments is the better fit.
OxaPay Crypto Payment Gateway15

Get the payout information

ActionIn the docs only

Where a payout stands is the answer this action gives, for one payout you already have a reference for.

When to use it
a partner asks whether their transfer went out, and you want the status posted in your team chat.
Watch out
you need the payout reference first, usually mapped from Generate a payout or Watch payout webhook earlier in the scenario.
OxaPay Crypto Payment Gateway16

Get the swap rate

ActionIn the docs only

The rate between two currencies is what this module returns, which is handy when you only need the ratio and not a full quote.

When to use it
a filter should let a conversion through only when the rate crosses a level you chose.
Watch out
Calculate a swap gives the amount you would get; this module gives the rate, so pick the one your next step needs.
OxaPay Crypto Payment Gateway17

Get the system status

ActionIn the docs only

Is OxaPay up? This action tells your scenario, so a run can stop politely instead of failing halfway through a payout.

When to use it
as a first check in any scenario that moves money, followed by a filter that stops the run when the service reports a problem.
Watch out
it costs an operation each time, so keep it for scenarios where a failure would hurt.
OxaPay Crypto Payment Gateway18

Make an Common API Call

ActionIn the docs only

For a request the ready-made modules do not cover, this module lets you call the part of the OxaPay API the name calls common, with your connection already attached.

When to use it
you need a lookup that none of the ready-made modules on this page offers.
Watch out
the page has no detail on which endpoints this covers, so read the OxaPay API docs and test with Run once.
OxaPay Crypto Payment Gateway19

Make an General API Call

ActionIn the docs only

This is the catch-all option among the four API call modules, handy when a request fits none of the specialised modules on this page.

When to use it
the OxaPay API offers something useful and none of the 22 actions reach it.
Watch out
you write the request yourself, so an unfamiliar request should be tried on test data, never first on a live payout.
OxaPay Crypto Payment Gateway20

Make an Payment API Call

ActionIn the docs only

Payment requests that go beyond the invoice and payment modules can be sent from here, using the connection you already set up.

When to use it
you need a payment option or detail that Generate an invoice or Get the payment information does not expose.
Watch out
check the answer with Run once and read the returned bundle before mapping it further down the scenario.
OxaPay Crypto Payment Gateway21

Make an Payout API Call

ActionIn the docs only

On the payout side, this module sends your own request to the OxaPay API when Generate a payout and its companions are not enough.

When to use it
a payout detail your finance team needs is missing from the standard modules.
Watch out
payout calls can move money, so build them with the same care as a payout: a test case first, then activation.
OxaPay Crypto Payment Gateway22

Revoke static address

ActionIn the docs only

Closing a deposit address you no longer want customers to use is the job of this action.

When to use it
a client account is closed in your CRM, and its address should stop being a way to pay you.
Watch out
treat the revocation as final, and tell the customer before, so nobody sends funds to an address you just closed.
OxaPay Crypto Payment Gateway23

Search payments

SearchIn the docs only

Looking through past payments becomes automatic with this search, which can return zero, one or many payments, each as its own bundle.

When to use it
reconciling your books, or finding every payment linked to a customer before answering a dispute.
Watch out
several results mean the next modules run once per payment, and each run counts as an operation.
OxaPay Crypto Payment Gateway24

Search payouts

SearchIn the docs only

The outgoing counterpart of Search payments: it looks through payouts you already made and hands back each match as a bundle.

When to use it
accounting wants a list of transfers to one partner, or you need to check that a payout was not sent twice.
Watch out
an empty result is normal when nothing matches, so plan what the scenario should do in that case.
OxaPay Crypto Payment Gateway25

Search static address

SearchIn the docs only

Finding a deposit address you created earlier takes one search module instead of a trip through the OxaPay dashboard.

When to use it
a customer pays and you need to match the address to their account, or you want to review addresses before revoking one.
Watch out
the search may return several addresses, so add a filter if only one should continue.
OxaPay Crypto Payment Gateway26

Search swaps

SearchIn the docs only

Your conversion history is what this search returns: past swaps, each delivered as a separate bundle.

When to use it
you want every swap copied into a spreadsheet for tax records, or you need to check one conversion a colleague asked about.
Watch out
map the results into an aggregator if you want one summary row rather than one row per swap.
Need help

Need help automating OxaPay Crypto Payment Gateway with Make?

A person reads every message.

FAQ

Questions about OxaPay Crypto Payment Gateway and Make

01Is the OxaPay Crypto Payment Gateway Make integration free?
Yes, on the Make side. OxaPay Crypto Payment Gateway is a standard app, so it works on the Free plan along with the 3,000+ other standard apps. The Free plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes of run time and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the minimum interval down to 1 minute and count usage in credits each month. You still need an OxaPay merchant account, whose own terms are set by OxaPay.
02What does it take to connect OxaPay Crypto Payment Gateway to Make?
An active OxaPay merchant account and a Merchant API Key. You generate the key in OxaPay from the Merchant Service section by filling in the form and clicking Generate Merchant API Key, then copying the key shown on screen. In Make, add any OxaPay module, click Create a connection, give it a name if you like, and paste the key. That connection is then shared by every OxaPay module in your scenarios, so the setup happens once per account.
03Does the OxaPay Crypto Payment Gateway trigger fire instantly in Make?
No. Both triggers, Watch payment webhook and Watch payout webhook, are listed as scheduled: Make checks OxaPay on the schedule you set on the first module. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. Note that this type was inferred from the module names because the Make directory was unavailable, so the clock or lightning badge on the module in the editor is the thing to trust.
04What if a needed OxaPay module is missing in Make?
Try the API call modules first. Unlike many apps, OxaPay Crypto Payment Gateway has no generic Make an API Call module, but it ships four specific ones: Common, General, Payment and Payout API calls. They let you send your own request with the existing connection. If that is still not enough, check the OxaPay docs directly, since the Make help page for this app is marked as AI-generated and may contain mistakes. The team can also help you design the scenario.
05Is Make or n8n better suited to OxaPay Crypto Payment Gateway?
It depends on your criteria. On Make, OxaPay comes with 28 ready modules, including triggers for payments and payouts and searches across payments, payouts, addresses and swaps, and it runs on the Free plan. This page does not cover whether an n8n node exists for OxaPay, so check that before comparing. The deciding points are usually which tool your team already uses, how you want to pay for usage, and whether the exact modules you need exist on each side.
Same platform

Other docs you might need on this stack.

Browse all integrations