Subscription
—
Next billing: — · —/mo
Payments Used
—
Total Payments
—
Confirmed customer payments
Recent Account Activity
| Type | Amount | Description | Date |
|---|---|---|---|
| No transactions yet | |||
Add Balance
💳 Need more balance? Balance is added by a reseller. Click below to see available resellers and contact them via WhatsApp or their website — tell them your account email and the amount to add.
Billing History
Your top-ups and subscription charges
| Type | Amount | Description | Date |
|---|---|---|---|
| No transactions yet | |||
Confirmed Payments
—
All-time verified customer payments
Confirmed Volume
—
Total value processed
Customer Payments
| Order ID | Method | Amount | Status | Date |
|---|---|---|---|---|
| Loading… | ||||
—
Payment Methods
Enable the methods you want on your checkout. Only enabled methods appear to customers.
Binance Pay
Pay via Binance ID, email or QR code
⚠️ IP Whitelist Required — Add 23.88.55.180 to your Binance API trusted IPs.
Binance → Account → API Management → Edit key → Restrict access to trusted IPs
Binance → Account → API Management → Edit key → Restrict access to trusted IPs
Show this QR in checkout
TRC20 USDT
Direct USDT transfer on Tron network
Show this QR in checkout
BEP20 USDT
Direct USDT transfer on BSC network
Show this QR in checkout
ERC20 USDT
Direct USDT transfer on Ethereum network
Show this QR in checkout
Payment Mode
How on-chain (TRC20 / BEP20 / ERC20) & Binance payments are handled.
Auto-Detect RECOMMENDED
The customer sends any amount — PayGate reads the real amount received and credits exactly that. Network & exchange fees never cause a mismatch. This is the default.
Fixed Amount (secondary)
The customer must pay the exact invoice amount. A short/underpaid transfer is rejected as a mismatch. Use only if you specifically need strict exact-amount payments.
Auto-Detect is recommended for everyone. After changing this, re-download your gateway files and follow the Setup Guide.
$
Set this to match your DHRU add-funds minimum. The Auto-Detect popup then shows it, and blocks a below-minimum payment before DHRU rejects it. Leave blank to accept any amount. Applies live — no re-download needed.
Shows the floating “Add Funds” button on your storefront so customers can top up any amount from any page. Turn it off to hide the button — automatic mismatch correction on invoices keeps working either way. Applies live.
Download Gateway Files
Your API key is embedded automatically. Upload to DHRU and activate.
Need the full walkthrough? Open the Setup Guide →
Callback URL — Advanced
Only needed if your host (e.g. Hostinger) blocks the default DHRU callback path.
Move gatewaypro.php and gatewaypro_confirm.php to any public folder, enter its URL here, then Test.
Your PayGate Pro API Key
Embedded in your gateway files. Regenerate = old key stops working immediately.
1Binance API
2Wallet Addresses
3Enter Credentials
4Upload Files
5Activate & Test
1
Binance API Key Setup & IP Whitelist
⚠️ IP Whitelist is mandatory. Your API key will be rejected unless you whitelist the server IP first:
23.88.55.180- Log in to binance.com → Profile → API Management
- Click "Create API" → choose "System generated" → label it PayGatePro
- Under API Restrictions enable only: Enable Reading — that's all PayGate Pro needs to check your payment history. Do not enable withdrawals or transfers; your key never needs the ability to move funds, only to read it.
- Under IP Access Restriction select "Restrict to trusted IPs only" and add:
23.88.55.180 - Save and complete any 2FA Binance asks for. Copy your API Key and Secret Key
- Go to Profile → Payment → Binance Pay and note your Merchant ID (a numeric ID, e.g.
37436613— length varies by account, that's normal)
2
Wallet Addresses (TRC20 / BEP20 / ERC20)
PayGate Pro can accept USDT on three networks in addition to Binance Pay. You only need to set up the ones you want to offer — enable/disable each in Gateway Setup.
TRC20 (Tron network)- Binance → Wallet → Spot → Deposit → search USDT → network TRC20 (Tron)
- Address starts with
T, 34 characters. Any TRC20 wallet works (Trust Wallet, TronLink, etc.) — verified via tronscan.org
BEP20 (BNB Smart Chain)- Same Binance deposit flow — search USDT → network BEP20 (BSC)
- Address starts with
0x. Any BSC-compatible wallet works (Trust Wallet, MetaMask on BSC, etc.) — same address format as ERC20, but a different network, so don't mix them up
ERC20 (Ethereum network)- Same Binance deposit flow — search USDT → network ERC20 (Ethereum)
- Address also starts with
0x. Any Ethereum wallet works (MetaMask, etc.) — customers pay gas in ETH to send, but that's on them, not you
ℹ️ All three networks give customers a 30-minute window to submit their transaction ID after sending. Remind customers to submit promptly.
3
Enter Your Credentials in the Panel
- Go to Gateway Setup in the sidebar
- Enter your Binance Merchant ID from Binance Pay profile
- Enter your Binance API Key and API Secret from Step 1
- Enter whichever of the TRC20 / BEP20 / ERC20 wallet addresses from Step 2 you want to accept — toggle each method on or off with its switch
- Click Save Credentials — all values are encrypted at rest
4
Download & Upload Gateway Files to DHRU
- In Gateway Setup, click Download Gateway Files
- Extract the ZIP — you will see a
modules/folder inside - Upload the files to your DHRU installation via cPanel File Manager or FTP:
Upload destinations
gatewaypro.php→public_html/modules/gateways/These 3 go insidecallback/gatewaypro/(upload the whole folder):callback/gatewaypro/gatewaypro.phpcallback/gatewaypro/gatewaypro_confirm.phpcallback/gatewaypro/.htaccess - ✅ No .htaccess editing required. The
callback/gatewaypro/subfolder in the ZIP has its own.htaccessthat handles this automatically. DHRU updates will never overwrite it. - Confirm these 4 files exist on your server:
modules/gateways/gatewaypro.phpmodules/gateways/callback/gatewaypro/gatewaypro.phpmodules/gateways/callback/gatewaypro/gatewaypro_confirm.phpmodules/gateways/callback/gatewaypro/.htaccess
⚠️ On some managed hosts (e.g. Hostinger), the callback files will be blocked at the network/firewall level — re-uploading won't fix it. If customers see "Payment gateway is not set up for this store yet", don't keep retrying — instead:
- Create any public folder outside the blocked path, e.g.
public_html/pgpcb/ - Copy just
gatewaypro.phpandgatewaypro_confirm.phpinto it (leave the original in place — DHRU still needs it to show the gateway) - Go to Gateway Setup → Callback URL (Advanced) → enter that folder's URL (e.g.
https://yourstore.com/pgpcb) → click Test, then Save
5
Activate Gateway in DHRU & Test
- Log in to your DHRU Admin panel
- Go to Settings → Payment Gateways
- Find PayGate Pro and click Activate
- No API key entry needed in DHRU — it is already embedded in the PHP files
- Create a test order, select PayGate Pro, complete a small USDT payment
- Once confirmed, your gateway is live for all customers 🎉
6
Auto-Detect Mode RECOMMENDED
This is the recommended way to run PayGate Pro. The customer pays any amount first, PayGate reads the real amount that arrived (on-chain or Binance Pay), then creates the invoice for exactly that amount and marks it paid. No amount mismatches from network or exchange fees, and nothing to add manually. Works for Binance Pay and TRC20 / BEP20 / ERC20. (The alternative — Fixed Amount — makes the customer pay the exact invoice total, and is only for stores that specifically need that.)
🔄 Fully live. The steps below are a one-time install. After that, any change you make in this panel — wallet address, enabled methods, or Payment Mode itself — appears on your storefront immediately. No re-download, no re-paste, ever again.
- In Gateway Setup → Payment Mode, make sure Auto-Detect is selected — it's the recommended default.
- Download your gateway files. The ZIP contains two new files:
gatewaypro_detect.phpandgatewaypro_addfunds.php(both incallback/gatewaypro/), plusautodetect_addfunds_button.tpl(in the ZIP root). - Upload both PHP files into your
modules/gateways/callback/gatewaypro/folder — the same place as your other callback files. They're same-origin proxies (a direct browser call to PayGate is blocked by DHRU's security policy / CSP), and they never need touching again — future changes are fetched through them live. - Open your active theme's footer template —
templates/<your-theme>/footer.tpl— and paste the entire contents ofautodetect_addfunds_button.tpljust before the closing</body>tag, then save. This is the last time you'll ever need to touch the footer. - A floating "Add Funds" button now appears on your store. Customers pick a method, send USDT (or Binance Pay), paste their TxID / Order ID, and are credited the exact amount received. Only your enabled methods are shown — and that list, along with wallet addresses, updates live the moment you change it here.
✅ Fully reversible. Switch to Fixed Amount in Payment Mode and the button disappears automatically on next page load — no need to touch the footer snippet again.
ℹ️ After the customer pastes their TxID, the invoice is created and confirmed automatically — they don't re-enter anything. On some themes an invoice page appears first and the customer clicks Pay once; it then auto-confirms.
Troubleshooting
"Payment gateway is temporarily unavailable" ＋
- Your subscription is not active — go to Subscription and activate/renew a plan
- Your prepaid balance is $0 or negative — top up via Add Balance
"Payment gateway is not set up for this store yet" ＋
- Your callback file (Step 4) isn't reachable — usually a 403/404 from your host
- Confirm the 4 files from Step 4 exist at those exact paths
- If your host blocks PHP in the callback folder (common on Hostinger), use the Callback URL (Advanced) fallback at the end of Step 4
"Order ID already used" ＋
This isn't a bug — it's duplicate-payment protection working correctly. That exact Order ID/TxID was already confirmed before. Ask the customer to make a fresh payment and submit the new transaction ID.
"Transaction not found" after payment ＋
- Binance Pay: Order ID must match exactly what appears in your Binance Pay history
- TRC20: TxID must be the full 64-character hash from TronScan
- TRC20 transactions expire after 30 minutes — submit before the window closes
- Confirm IP 23.88.55.180 is whitelisted in your Binance API settings
Binance API returns authentication error ＋
- Confirm 23.88.55.180 is in your Binance API IP whitelist
- Re-check API Key and Secret — no extra spaces when copying
- API key must have Enable Reading enabled (transfers/withdrawals are not needed)
Auto-Detect: "Add Funds" button missing or not crediting ＋
- Button missing → confirm
gatewaypro_addfunds.phpis uploaded incallback/gatewaypro/, AND the footer snippet is pasted into your active theme'sfooter.tpl(Step 6). Once both are in place you never need to touch them again — enabled-method and wallet changes appear automatically. - Button stuck on "Verifying…" / detect fails → confirm
gatewaypro_detect.phpis uploaded in the same folder. A stuck spinner usually means that file is missing. - Same on-chain rules apply — correct network, sent to your wallet, within the time window, and Order IDs/TxIDs are single-use
Need help?
Contact your PayGate Pro admin for support with setup, billing, or credentials.
Auto Cron for your DHRU store
One click — we run your DHRU cron automatically so orders are sent and replied around the clock. No cron-job.org, no server cron, no setup.
Loading…
Change Password
Two-Factor Authentication
Google Authenticator (TOTP)