WHMCS · Global

Accept OxaPay
payments on WHMCS

Install the free PaymentHood module for WHMCS, connect your OxaPay account, and OxaPay appears as a payment option at checkout. No custom gateway code, and no second integration when you add another provider later.

  • BTC
  • ETH
  • USDT
  • USDC
  • BNB
  • DAI
  • TON
WHMCS 7.0+
2 payment methods
Free module
WHMCS
OxaPay
Platform
WHMCS 7.0+
Provider
OxaPay
Install via
Apps & Integrations
Billing
One-time & recurring
PaymentHood fee
None
Compatibility

OxaPay on WHMCS at a glance

WHMCS version
WHMCS 7.0+
Where you install it
WHMCS admin → Apps & Integrations
Coverage
Available globally. Onboarding is lighter than the incumbent processors, which is much of its appeal to smaller merchants.
Currencies
  • BTC
  • ETH
  • USDT
  • USDC
  • BNB
  • DAI
  • TON
Billing models
One-time checkout and recurring renewals — WHMCS generates both, and the module handles both.
Cost
The module is free and open source. You pay OxaPay's own fees, published on their pricing page (opens in new tab). PaymentHood adds nothing on top.

Coverage, currencies and payment methods as published by OxaPay, who set and update them. For the current list see OxaPay's own documentation (opens in new tab).

Payment methods

What WHMCS customers can pay with

Each method OxaPay supports appears in your WHMCS checkout. Enabling one is a PaymentHood dashboard setting — nothing changes on the WHMCS side.

Cryptocurrency

Bitcoin, Ethereum, BNB, TON and others

Stablecoins

USDT on TRC-20, ERC-20 and BEP-20, plus USDC and DAI

Setup

Connect OxaPay to WHMCS

Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.

1

Open a OxaPay account

Register with OxaPay and finish their onboarding. Funds settle from OxaPay to your own bank account.

2

Add it in PaymentHood

Paste your OxaPay credentials into the PaymentHood dashboard. They stay server-side and never reach your storefront.

3

Install the module

Download the WHMCS module and install it from Apps & Integrations in your WHMCS admin.

4

Enable and test

Paste your PaymentHood API key into the module settings, run a sandbox order end to end, then switch to live.

Why PaymentHood

Rather than a direct OxaPay module

A single-provider module works until you need a second provider. These are the parts you would otherwise build and maintain yourself.

Webhook security
Signed callback, validated before an order is released
Payment verification
Server-side invoice status re-check against the OxaPay API before fulfilment
Credentials
Merchant API key, held server-side in PaymentHood
  • Add a second provider without touching your WHMCS checkout
  • Automatic failover when OxaPay is unreachable, instead of a failed order
  • Idempotent charge creation, so a double-submitted order is not a double charge
  • One reconciliation view across every provider you run
  • Free and open source — read the module on GitHub (opens in new tab)
FAQ

Frequently Asked Questions

USDT exists on several blockchains and they are not interchangeable. TRC-20 transfers cost cents; ERC-20 transfers can cost several dollars at busy times. Offering the network your customers actually use is the difference between a completed and an abandoned payment.

Fewer than you think. USDT on TRC-20 plus one or two majors covers most real-world crypto payment volume. A long list adds checkout choice paralysis without adding conversions.

Only if you choose to be. These gateways quote the invoice in your pricing currency and lock the rate for a short window, then settle to you in either fiat or crypto depending on your setting. Settling in fiat removes the exposure; settling in crypto keeps it. Decide that before you switch it on.

No. OxaPay bills you directly for its own fees, and PaymentHood takes no percentage and no per-transaction cut at any volume. See PaymentHood pricing.

Accept OxaPay on WHMCS today

Free module, no PaymentHood transaction fee, and room to add another provider whenever you need one.