--- title: "OxaPay Integration" description: "OxaPay is a cryptocurrency payment gateway with hosted invoices and static receiving addresses. Agents generate invoices and white label payments, track payment history, send crypto payouts, run currency swaps, and read balances and price feeds." url: https://flowrunner.ai/integrations/oxapay-crypto-pay-gtw date_modified: 2026-09-04T14:51:36-07:00 --- # OxaPay [Payments](https://flowrunner.ai/integrations/category/finance-accounting) OxaPay is a cryptocurrency payment gateway with hosted invoices and static receiving addresses. Agents generate invoices and white label payments, track payment history, send crypto payouts, run currency swaps, and read balances and price feeds. 23 actions · Custom auth · available [OxaPay website](https://oxapay.com/) · [Platform Documentation](https://docs.oxapay.com/) · Capability data verified 2026-08-25 1. A finance owner asks to retire a receiving address that has been published for months 2. Agent reads the address and its settings with List Static Addresses 3. Generate Static Address mints the replacement and the agent publishes it downstream 4. Agent confirms the new address is live and that any required memo traveled with it 5. List Payments filtered to the old address reports whether anything still arrives 6. Both addresses and the quiet period post to the treasury channel 7. The finance owner confirms the old address may stop crediting, and it is revoked ## What This Integration Enables Most gateways in this category hide the payment rail behind a hosted page. OxaPay lets you choose how much of it to hide. Generate Invoice gives you the hosted page, where OxaPay handles coin selection, rates, and confirmations. Generate White Label Payment gives you the raw address, exact amount, network, memo, QR payload, and expiry, so the payment happens entirely inside your own interface. Generate Static Address gives you something different again: an address that stays yours and credits you for anything sent to it, at any time, in any amount. That last shape is what makes OxaPay worth wiring into a flow rather than a checkout. A static address is a donation link, a topped-up customer wallet, or a recurring payer, and it has no amount and no expiry to reconcile against. FlowRunner agents generate the right shape for the situation, read balances and price feeds before quoting, send payouts, and run swaps between currencies you hold. Blockchain settlement is final, which is exactly why the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) moments on this connector sit at the operations that cannot be walked back. ### Without FlowRunner **Crypto handled outside the stack**: Invoices are pasted into chat and nobody can say which order a wallet payment belongs to **Callbacks trusted as settlement**: A notification is treated as confirmation, before the chain has actually confirmed anything **Address changes announced late**: A receiving address is retired and the update reaches payers after they have already sent ### With FlowRunner **Invoices carry their order**: An invoice is generated with the order reference and read back against it before fulfillment **Confirmed at the source**: Get Payment is the answer of record, and the callback is only the prompt to go and ask **Retirement follows publication**: The replacement is live and observed before anything stops crediting the old address ## Use Case Scenarios ### Priced in fiat, settled in crypto, confirmed at the source An order is approved in the storefront. The agent reads the current rate with Get Prices and confirms the coin the customer chose is one this merchant account actually accepts, using List Accepted Currencies rather than the wider platform list. It then calls Generate Invoice with the order reference and an auto withdrawal setting that sends what arrives straight to the company wallet. When the callback fires, the agent does not believe it. It calls Get Payment on the track identifier and reads the status, the coin, the network, and the transactions actually received. Only then does the order release in [Shopify](https://flowrunner.ai/integrations/shopify) and a line post to [Xero](https://flowrunner.ai/integrations/xero). ### A monthly close that adds itself up On the first of the month, the agent calls Get Payment Statistics for the period rather than paging every payment and summing the rows. It reads Get Account Balance across every currency, lists swaps for the period and separates the automatic conversions from the deliberate ones, since an auto-convert triggered by an invoice setting otherwise looks like an unexplained trade. The result appends to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and a summary posts into [Slack](https://flowrunner.ai/integrations/slack) with the balance, the take, and the fees side by side. ### A payout that checks the ground before it moves A supplier is due a payment in crypto. Before Generate Payout, the agent reads Get Account Balance, because a payout larger than the balance fails as an in-body error with an HTTP 200 status and a status-only reader would call that success. It reads List Supported Networks to confirm the chain, and it refuses to proceed on a memo network unless the memo is present. It then posts the address, the coin, the network, and the amount to the treasury owner for confirmation, because a blockchain transfer cannot be recalled and a wrong chain or a missing memo loses the funds permanently. After the send, Get Payout is polled until the status reads confirmed, which is the only state that means the money arrived. ## Human-in-Loop Highlight The obvious gate on a crypto connector is the payout, and this one has that too. The more interesting one is Revoke Static Address, because of how it fails. Revoking stops the address crediting you. It does not stop anyone sending to it. Every payer who saved the old address, every printed QR code, every invoice PDF in someone's downloads folder still works, and money that arrives after revocation is simply not credited. Nothing in this action list reverses that, and nothing tells you who still holds the address. So the agent runs the sequence and stops before the last step. It generates the replacement, publishes it, and watches List Payments filtered to the old address until it goes quiet. Then it asks the treasury owner: "The old address has received nothing in fourteen days and the replacement has taken three payments. Revoke the old address now?" A person answers, because the cost of guessing early is a payer's money landing nowhere. 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 23 actions ### Taking Payments 5 - **Generate Invoice** Creates an invoice and returns a hosted payment page the payer opens to choose a coin and pay. The simplest way to take crypto: you name an amount and OxaPay handles coin selection, rates, and confirmations. Auto withdrawal sends what arrives straight to your own wallet instead of your platform balance, and the link expires after the lifetime you set. - **Generate White Label Payment** Creates a payment and returns the raw details, including address, coin, exact amount, network, memo, QR code, and expiry, so the payment happens inside your own interface. The address is valid only for its lifetime, and crypto sent after that is permanently lost. On memo networks the returned memo must reach the payer or the funds are lost. - **Generate Static Address** Creates an address that stays yours and credits you for any payment sent to it, at any time and in any amount. The shape for a donation link, a topped-up wallet, or a recurring payer. There is no amount and no expiry, and the vendor retires an address after six months with no transactions. - **List Static Addresses** Lists the static addresses on the account, filtered by network, currency, address, order reference, email, or whether the address has ever received anything. Set the page size explicitly, since the vendor's default on this route is one row. - **Revoke Static Address** Retires a static address so it stops crediting you. Anyone who still has the address can send to it, and after revocation those funds are not credited, so the replacement should be published and observed first. ### Reading Payments 4 - **Get Payment** Reads one payment by its track identifier: amount, coin, network, address, status, rate, and the transactions received against it. This is the authoritative check after a callback, since a callback says something changed and this says what is true. - **List Payments** Lists payments across invoices, white label payments, and static addresses, filtered by type, status, coin, network, address, amount range, or date range. - **Get Payment Statistics** Reads totals rather than rows over a period, optionally narrowed to one payment type, coin, or network. Answers the monthly take in one request instead of paging every payment. - **List Accepted Currencies** Lists the cryptocurrencies this merchant account is set up to accept, which is a narrower set than the coins the platform supports overall. Check here before offering a coin, since one that is supported but not enabled is refused at invoice time. ### Payouts 3 - **Generate Payout** Sends cryptocurrency from your balance to an external address. This moves real money and a blockchain transfer cannot be reversed, so a wrong address is a permanent loss. The network is required for any coin that exists on more than one chain, and some networks require a memo. - **Get Payout** Reads one payout by its track identifier, with its status and transaction hash once it is on chain. The statuses run processing, pending, confirming, confirmed, and either canceled or rejected, and only confirmed means the money arrived. - **List Payouts** Lists payouts filtered by status, coin, network, amount range, or date range. The type field separates external payouts that went on chain from internal ones that moved between platform accounts. ### Swaps 5 - **Swap** Exchanges one currency in your balance for another. It executes immediately at the rate applied at that moment, which is not necessarily the rate just quoted, so treat a calculation as an estimate rather than a locked price. - **Calculate Swap** Works out what a given amount would fetch in another currency without swapping anything. An estimate, not a locked quote. - **Get Swap Rate** Reads the current exchange rate between two currencies, with no amount involved. Used to price something in crypto before an amount exists. - **List Swap Pairs** Lists the currency pairs the platform will actually swap between. Not every combination exists, so read this before offering a swap rather than discovering the gap when the call fails. - **List Swaps** Lists your swaps, filtered by currency, date range, or type. Worth reading the type, since automatic conversions made by an invoice setting otherwise look like unexplained trades. ### Balances and Reference Data 6 - **Get Account Balance** Reads your balance, either across every currency or for one. Check it before a payout, since a payout for more than the balance fails as an in-body error carrying an HTTP 200 status. - **Get Prices** Reads the current price for every supported cryptocurrency in US dollars. This route needs no API key, so a flow can price something in crypto before any credential exists. - **List Supported Currencies** Lists every cryptocurrency the platform supports, with its networks, minimum amounts, and withdrawal fees. This is the platform-wide list, wider than what a given account accepts. - **List Supported Fiat Currencies** Lists the fiat currencies an invoice may be priced in, with their current rates. Pricing in fiat does not mean settling in fiat: the payer still pays crypto and you still receive crypto. - **List Supported Networks** Lists the blockchain networks the platform operates on. Worth reading before a payout or a white label payment, because the wrong network on the right coin loses the funds. - **Get System Status** Reports whether the API is operating. Worth calling when a flow starts failing, because it distinguishes a vendor outage from a problem with the request. ## Frequently Asked Questions ### What can FlowRunner do with OxaPay? FlowRunner agents can run Generate Invoice, Generate White Label Payment, and Generate Static Address in OxaPay, plus 20 more actions. ### Does connecting OxaPay to FlowRunner require OAuth? OxaPay uses a custom authentication method to connect to FlowRunner. ### Can OxaPay trigger a FlowRunner workflow automatically? OxaPay doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at OxaPay?** This integration exposes OxaPay to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/oxapay-crypto-pay-gtw. Site index: https://flowrunner.ai/llms.txt