Frequently asked questions
The questions we get most, before and after integration. If yours is not here, just reach out.
Which chains and tokens are supported?+
By default: TRC20, ERC20, BEP20, Polygon, Plasma, Solana, TON and Aptos, plus tokens such as USDT, USDC, TRX, SOL and TON. You can specify the token and network per order, and payers can switch on the checkout page; what your account can use is shown in the console.
Does the platform hold my funds?+
No. Payments go straight to the receiving wallets you configure — the platform never holds or collects them and takes no cut. Our job is creating orders, watching for the transfer and sending you the callback.
How are orders matched without mistakes?+
Each order locks a unique address-and-amount slot and is matched by exact amount and timing, so concurrent orders never interfere. The payer must transfer exactly the amount_due from the response.
What happens if a callback fails?+
Failed callbacks retry with backoff, and the same order may notify you more than once — just make your handler idempotent. Callback records are visible in the merchant console and can be resent by hand if needed.
How long does integration take?+
One server-side call creates an order; signing rules and sample code are in the integration docs. Dujiaoka, V2Board, WHMCS, WordPress and similar systems already have ready-made integrations — live in minutes.
What systems can I use it with?+
Any server that can make an HTTP request, in any language or framework. The EPay-compatible protocol means many card-selling, proxy-panel and website systems can connect as-is.
Where do I check quotas and invoices?+
The merchant console shows your current plan, this month's usage, invoices and the balance ledger. You are warned before reaching a limit, and an upgrade takes effect immediately.