Accept OxaPay
without building the integration
OxaPay is a crypto payment gateway aimed at small and mid-sized online businesses, supporting the major cryptocurrencies including USDT across the TRON, Ethereum and BNB chains. Its appeal is low friction: no lengthy onboarding, and ready-made plugins for the common e-commerce and hosting platforms.
- BTC
- ETH
- USDT
- USDC
- BNB
- DAI
- TON
- Region
- Global
- Methods
- 2
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
OxaPay in summary
- Coverage
-
Available globally. Onboarding is lighter than the incumbent processors, which is much of its appeal to smaller merchants.
Among the markets OxaPay serves — their own list is authoritative (opens in new tab).
- Currencies
-
- BTC
- ETH
- USDT
- USDC
- BNB
- DAI
- TON
Among those supported. Which ones your account can charge in depends on its registered country.
- Fees
- Set and billed by OxaPay, who publish current rates on their own site (opens in new tab). PaymentHood adds nothing on top, at any volume.
- Official resources
- Website (opens in new tab) · Developer docs (opens in new tab)
Written against OxaPay's own documentation on . This page deliberately states no fees, no counts and no completeness claims, because those change without notice — for anything you are about to build on, OxaPay's own documentation (opens in new tab) is the authority.
What your customers can pay with
Every method below runs through the same PaymentHood checkout. Turning one on or off is a dashboard setting, not a code change.
Cryptocurrency
Bitcoin, Ethereum, BNB, TON and others
Stablecoins
USDT on TRC-20, ERC-20 and BEP-20, plus USDC and DAI
What PaymentHood handles for you
A direct OxaPay integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- Merchant API key, held server-side in PaymentHood
- Webhook security
- Signed callback, validated before an order is released
- Payment verification
- Server-side invoice status re-check against the OxaPay API before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when OxaPay is unreachable
- One reconciliation view across OxaPay and every other provider you run
- Provider credentials never reach the storefront or the customer's browser
- Adding or switching a provider later is a dashboard change, not a re-integration
Use OxaPay on your platform
Install the free PaymentHood plugin for your store, then enable OxaPay in your dashboard.
Connecting OxaPay takes three steps
Open your OxaPay account
Register directly with OxaPay and complete their onboarding. Funds settle from OxaPay into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your OxaPay API credentials into the PaymentHood dashboard. They are stored server-side and never exposed to your storefront.
Enable it at checkout
Install the PaymentHood plugin for your platform, paste your PaymentHood API key, and OxaPay appears as a payment option. Test in sandbox, then switch to live.