OxaPay vs Plisio 2026: Fees and the Better Fit for Your Shop

Plisio is our starting point if price is what matters for ordinary Bitcoin checkout, provided your business qualifies and you have a way to receive the money. OxaPay deserves a look despite the higher percentage if you need a payment link your staff can share or a way to take repeat deposits. Settle bank and returns questions before choosing either.

OxaPay

48/100

4 – 2

Plisio

49/100

5.0

Cost

8.3

0.0

Fiat cash-out

1.0

0.0

Licence

0.0

8.0

Coins and networks

6.0

10.0

Integrations and API

8.0

8.6

Features

4.3

5.0

Support and reliability

4.0

8.0

Onboarding

8.0

The money figures in the comparison cover ordinary OxaPay invoices and Plisio's BTC API only, with the merchant paying the commission. They leave out minimums, network and transfer fees, conversion and account costs; unknown isn't free. Both providers also have to accept your company, owners and activity before you can use either. Two labels need care: OxaPay's bank “No” is a finding, while Plisio's “Unknown” means we couldn't tell, and a licence “Unknown” isn't a finding of illegality. A custody label doesn't prove you hold the only keys. Ratings keep their older source dates.

	OxaPay	Plisio
Score	48/100 · #17	49/100 · #16
Payment fee	1.5%	0.5%
Cost on $10k/month	$150	$50.00
Pays out to bank	No	Not stated
Stablecoin networks	USDT: Ethereum, Tron, BSC, Solana, Polygon, TON · USDC: Ethereum, BSC, Solana, Polygon, Base · DAI: Not stated	USDT: ERC20, TRC20, BEP20, TON, Solana · USDC: ERC20, Base, BEP20, Solana · TUSD: Not stated · BUSD: BEP20
Coins	18	Not stated
Custody	Custodial or non-custodial	Custodial
Merchant KYC	Light	Light
Rolling reserve	Not stated	Not stated
Licence	Not stated	Not stated
Plugins	WooCommerce, WHMCS, ClientExec, Blesta, WISECP, PrestaShop	WooCommerce, Magento, PrestaShop, OpenCart, WHMCS, BigCommerce
Legal entity country	Not stated	Not stated
Founded	Not stated	Not stated

For detail on each provider, see the OxaPay review and the Plisio review.

Which should your kind of shop choose?

Choose by the payment job you need done, then check the offer covers it. A shop collecting its own sales needs each payment tied to an order and a way to handle returns. A platform taking customer top-ups or sending payments out needs a different agreement and process.

If the last row describes you, widen the shortlist before paying for an integration. The CoinGate review covers another way of receiving money, though CoinGate would have to accept you too.

How much cheaper is Plisio for ordinary Bitcoin checkout?

Plisio publishes the lower fee for ordinary BTC. Price matters, but a smaller fee won't help if customers can't use the checkout, you can't reconcile orders or you can't spend the proceeds.

These rates are only the commission on ordinary OxaPay invoices and on Plisio's BTC API, with the merchant paying it, and they come before the other costs mentioned above.

OxaPay publishes 1.5% for ordinary invoices and payment links.^[1] Plisio publishes 0.5% for BTC API processing.^[2] On a hypothetical $10,000 BTC-equivalent month of 100 orders at $100 equivalent, that's $150 versus $50 in fees. That $100 difference isn't your total saving.

The calculator below runs that same comparison at any volume and order size. Its annual figures assume twelve identical months, and none of its sliders switches on Receive, branding, static deposits or a negotiated rate.

Moving money out costs extra. Plisio describes variable network charges and Normal/Priority plans.^[23] Its cash-out percentage is a different charge from its checkout fee, so don't add it to every sale. OxaPay treats internal movement as free and charges for blockchain transfers, so sending to an outside wallet isn't free. If you plan to send proceeds elsewhere, ask which operation your account uses and how its service charge combines with the network fee.

The fee calculator guide explains what these subtotals leave out.

Do the same prices apply to stablecoins, branding and top-ups?

No. Choose the flow first: if you build around a branded screen or frequent top-ups and only later find the price differs from ordinary invoices, you'll have budgeted the right volume against the wrong product.

These products have their own prices, and the BTC calculator doesn't cover them. Branded BTC fees are 2% at OxaPay versus 1.5% at Plisio. Plisio's BSC USDT/USDC rows instead list 1% API or 2% white label. Its other token rows have minimum-fee and up-to wording, and we haven't tried to work out a formula or cap from it. OxaPay's reduced 0.4% comes with conditions and isn't every account's price. Its Receive 1% after total receipts exceed $20,000 is cumulative, not a monthly invoice discount.^[1][2]

Before you offer a token, find out which network it runs on and whether your account has it enabled. Plisio's appendix limits support to the choices in its Dashboard, so your account may not have every listed row enabled.^[17] OxaPay's logos and transfer rows don't give the full list of incoming assets either.

Do no-document claims mean either will approve your business?

No. Skipping documents at signup is one decision, and being allowed to use a particular product is another. Describe your business accurately, because you need an offer that covers the company, people, customers and activity involved, not just a quick registration. KYC and business verification can also affect access later.

OxaPay's help advertises no identification documents or KYC/KYB for merchants.^[7] Its current terms nevertheless limit service to the originally submitted and approved business.^[3] Plisio's plugin marketing says no KYC, while its mass-payout product explicitly requires business identity verification.^[14][15] Plisio's Terms also have an identity clause for suspected-compromised accounts. It isn't a blanket requirement for full business checks on every merchant.

Privacy is a different question. Plisio's linked policy lets it keep the identity information you supply, your account and transaction records, and data it has a qualifying legal or business reason to retain.^[16] Even with no-document signup, Plisio can hold your details, and a light application can be followed by a later review.

The contracts we checked on 15 October 2026 draw their lines differently. OxaPay excludes listed business-registration jurisdictions, including the US and its specified territories, which isn't a universal citizenship test. Plisio's Terms, still dated 12 March 2019, contain declarations about ownership and control, location, organisation, residence and export rules. They go beyond a country list, and they aren't a current statement of world law.^[3][4]

Neither source tells you the current signing company's jurisdiction or what permission it holds. Generic Company wording, an Inc. suffix or Manchester marketing doesn't settle that, and we found nothing linking a dissolved UK namesake to today's Plisio service. Ask each one who you'd be contracting with and what permission it holds. A site that markets to adult, gaming, forex or VPN businesses hasn't approved yours, so describe the real activity and customers. This is general information, not legal advice.

Will you control the proceeds and receive bank money?

We couldn't verify a complete way to usable bank cash from either provider. OxaPay describes a fully crypto-based service.^[6] Plisio's WooCommerce page specifies crypto-only receipt while its general FAQ makes broader conversion claims.^[14] So its bank position is unknown, not a confirmed “No”.

A dollar invoice, crypto credited to an account, an outside conversion and a bank credit are all different stages. If your supplier needs a bank transfer, find out who does the conversion, whether it approves you, what it charges and when the bank would be credited before you count a confirmed crypto payment as money that can cover the bill.

On who controls the money, OxaPay describes a hosted balance or configured onward routing, while Plisio markets direct wallets but also has service-wallet and account-control terms. Neither shows that only you hold the spending keys the whole way.

OxaPay's withdrawal guidance permits congestion delays and anti-money-laundering or security pauses.^[5] Plisio's access to a residual balance is subject to legal conditions, and we found no maximum release deadline.^[4] So a balance you can see may not be available when bills fall due.

What happens with short payments, expiry and returns?

Ship only on a confirmed payment for the amount that arrived. A redirect back to your site isn't proof, and returns need their own process. Before you dispatch goods, your order system should match the confirmed payment and received amount to the right order, leave any tolerated shortfall to a staff decision and stop the same order being fulfilled twice.

OxaPay describes a hosted invoice window, tolerance settings and a test-mode field.^[9] Its notification guide requires signature validation and treats Paying and Paid as different statuses.^[21] Plisio describes authenticated updates, confirmations, expiry and received amounts, and its shortfall rules qualify the simple “completed” and “full” wording.^[12]

OxaPay lets you accept or return some short payments by hand when coverage isn't enabled.^[8] Plisio permits configured tolerance and some manual completion after the waiting period, but none below 95%.^[13] Accepting a short amount leaves the value missing, so whoever does it should note the adjustment.

Expiry rules differ by product. OxaPay's branded-address documentation warns that funds sent after its lifetime are permanently lost.^[10] Static addresses are instead revoked after six inactive months, so a reusable address isn't permanent.^[11] The branded documentation also describes fee responsibility inconsistently, as commission versus network charges, so ask who pays which.

Plisio's refund wording doesn't give a complete ordinary merchant tariff.^[19] Its cancellation guidance is about sent transfers, so it doesn't rule out a customer refund.^[22] The customer relationship stays with your shop either way.

Which is easier to integrate, support and leave?

The easier choice depends on your store and who looks after it. A listing is only a starting point: your developer still has to test the plugin against your theme, checkout extensions and order process, and somebody has to own that work when an update changes how the store behaves.

Those are directory statements, not results from our own installation, security or maintenance checks.^[18][19] Neither a warning nor an older tag proves the plugin is abandoned.

OxaPay's help says replies depend on business hours and workload.^[20] Advertised availability at either service comes with no promise of a reply, a fix or a release deadline. The mixed reviews we've seen have older dates and unverified reviewer roles, so they aren't a measure of merchant reliability.

1. 
   01

   Confirm the new offer

   Get product and business approval, enabled networks, who controls receiving, the full price and the returns process confirmed before you schedule the switch.

2. 
   02

   Test your store

   Agree how you'll test confirmed, short, expired and repeated payment updates. OxaPay describes a test mode; don't assume Plisio has an equivalent.

3. 
   03

   Finish open orders

   Keep your order, payment, fee and customer-return records, and leave open invoices with their original provider for as long as you're still allowed to use it.

4. 
   04

   Close the old account

   Find out what you still owe and what the old account requires before it can close. Balances, saved addresses and subscription mandates don't transfer automatically.

Repeat deposits and scheduled outgoing payouts can't debit an outside customer's wallet automatically, so renewals need their own way of collecting. The processor selection guide can help you turn these requirements into a decision.

What changed, and which evidence is older?

When you review an account offer, compare the policy version that would govern your business with the published product descriptions. A page opened today may still show an older agreement.

OxaPay vs Plisio FAQ

Change log: 15 October 2026, first version, covering ordinary BTC fees, token and deposit pricing, returns, plugin evidence and switching.