This guide is for IPTV services and resellers that sell monthly, quarterly or yearly subscriptions through a website, a Telegram bot or their own resellers and want to take crypto. Getting paid is only half of it: the order should be marked paid by itself, so you can hand out access right away instead of matching transfers in a wallet by hand.
Why crypto: IPTV is seen as a high-risk niche, and card acquirers often turn such projects down or keep part of the money in a reserve. IPTV customers also come from many countries. SnapEX Pay asks for no KYC, from you or from your customers, has no country restrictions and keeps no reserves. What can't be paid for through SnapEX Pay is listed in the merchant rules; if you're not sure your service fits, ask in the support chat before you connect. Rules on accepting crypto and on showing content differ from country to country, so check with a lawyer how they apply to your business.
- 1%fee per payment, no monthly costs — taken from the amount or added on top for the customer
- 0holds or reserves: withdraw USDT from the cabinet at once, with no service fee
- 70+coins on the payment page, USDT and USDC on Polygon included; you receive everything in USDT
How an IPTV subscription gets paid
From picking a plan to getting access
The module doesn't trust the webhook body alone: before marking an order paid, it reads the invoice again from the SnapEX Pay API. The same payment is never applied twice, even if the notification arrives again. SnapEX Pay doesn't create the line in your IPTV panel: your site, bot or manager does that from the order status, just as with any other payment method.
Step 1. Pick how to connect
- Plugin
The customer picks "Crypto" at checkout and pays on the SnapEX Pay page; the order becomes Processing, or Completed right away for a virtual product. Prices in euros and other currencies are converted to USD automatically.
WordPress 6.2+ · WooCommerce 8.2+ · PHP 7.4+
- Gateway
If you sell subscriptions as WHMCS services: Pay Now leads to the payment page, the invoice turns Paid by itself, and billing automation takes it from there.
WHMCS 8.x and 9.x · PHP 7.4+ with cURL
- API
One REST API call creates an invoice and returns a payment page link for the bot's button. A signed webhook reports the status.
Same docs and test mode as the modules
- Fixed addresses
Each reseller or customer gets a top-up address that never changes. Every transfer to it is credited to your balance, with a webhook for each one.
USDT TRC20, ERC20, BEP20, Polygon, USDC Polygon, BTC, LTC, ETH, TRX
Step 2. Create a merchant account and an API key
- Sign up at pay.snapex.pro. A snapex.pro exchange account works too: it's the same account. No documents needed.
- Create an API key with the
invoices.readandinvoices.writescopes. - Add a webhook URL; for WooCommerce and WHMCS the module shows it in its settings. The
whsec_…signing secret is shown once, so save it right away. - Every notification is signed with HMAC-SHA256 and a timestamp. If your server doesn't respond, SnapEX Pay retries delivery, up to 5 attempts in total.
Step 3. Install the module or connect the API
- WooCommerce: Plugins → Add New → Upload Plugin with the archive from the module page, then WooCommerce → Settings → Payments → SnapEX Pay (crypto): paste the API key and the webhook secret. If a webhook gets lost, the plugin checks the order itself every 5 minutes, so a paid order never stays unpaid.
- WHMCS: unpack the archive into the WHMCS root, then System Settings → Payment Gateways → All Payment Gateways → activate SnapEX Pay (Crypto).
- Bot or your own site: when the customer taps "Pay", create an invoice through the API and send them the payment page link. Hand out access once the invoice is
paid, and read the invoice from the API first rather than trusting the webhook body alone.
Step 4. Test a purchase with a test invoice
Turn on test mode and buy a plan yourself. A test invoice confirms itself about 10 seconds after you pick a coin, and no real money moves. Regular customers don't see the payment method meanwhile: in WooCommerce only shop managers see it, in WHMCS only a logged-in admin. Check that the order was marked paid once and access went out, then turn test mode off. In WooCommerce, test payments are never applied once test mode is off. More in the guide How to test crypto payments without real money.
Step 5. Go live and set up withdrawals
- 1% fee, taken from your amount or added on top for the customer, your choice. No monthly fee and no setup fee.
- Coins for cheap plans. USDT on TRC20, ERC20 and BEP20, plus LTC, ETH and TRX, from $0.50 per invoice, enough for a monthly plan at a couple of dollars. Other coins and networks work for invoices from $8.
- SnapEX Pay invoice lifetime is 30 minutes by default, adjustable from 1 minute to 24 hours.
- Withdrawals: your balance is in USDT, withdrawn from the cabinet to a crypto address at once, with no holds, reserves or upper limit. No service fee, only the network fee; the minimum is $0.50 to $10 depending on the coin.
Minimum invoice amount by coin
- USDT TRC20 / ERC20 / BEP20, LTC, ETH, TRXfrom $0.50
- Other coins and networksfrom $8
Scale: $0 to $10. A monthly plan at $3–10 is paid in the coins of the first row.
Resellers: topping up credits without invoices
A lot of IPTV is sold through resellers who top up a balance and hand out subscriptions themselves. Issuing them an invoice for every top-up is awkward; a fixed address is simpler. The address is created through the API with the reseller's or customer's customer_id and never changes: every transfer to it is credited to your balance.
A fixed top-up address
- OnceAn address per reseller. One API call with their
customer_refreturns an address on the network you need: USDT, USDC Polygon, BTC, LTC, ETH or TRX. - Transfer seenWebhook
static_deposit.detected. You can show the reseller the payment is on its way. - CreditedWebhook
static_deposit.credited. The amount in USDT minus the usual fee: add the credits.
Minimum top-up: $0.50. USDT and USDC are credited 1:1; BTC, LTC, ETH and TRX at the rate at confirmation, minus the coin's network buffer.
Tokens the address doesn't support are not credited automatically; they are returned through support. So show the network and coin next to the address.
If the customer sent less
Exchanges often deduct their withdrawal fee from the amount sent. If the customer paid less than the invoice, they can top up to the same address within 72 hours; otherwise the invoice is marked partly paid, and the amount received is credited to your balance. WooCommerce puts such an order On hold with a note: access isn't handed out automatically, the call is yours. If the customer paid more, the invoice counts as paid. More in the guide What happens when a crypto payment is short.
Pre-launch checklist
Before you open crypto payments to customers
- Method chosen: WooCommerce, WHMCS, the API for a bot, or fixed addresses for resellers.
- API key with
invoices.readandinvoices.writepasted in, webhook set,whsec_…secret saved. - Access goes out only for a paid order or an invoice with the
paidstatus. - Test purchase done: the order was marked paid once and access went out.
- Fee: decided who pays the 1%, you or the customer.
- Test mode is off, every customer sees the payment method.
- USDT withdrawal address ready, and you know the minimum for your coin.
If you already take payments another way
No need to drop it: SnapEX Pay can sit next to it as a second option, and the customer picks how to pay. Step-by-step guides: WooCommerce and WHMCS; how webhook signatures and retries work is in Crypto payment webhooks.