DHRU Telegram bots

DHRU Telegram Bots connect your DHRU Fusion panel to Telegram. Your clients get a bot under your own brand, and you and your staff get a separate admin bot to run the panel from your phone. Both come with Telegram Mini Apps.

▶ New to Telegram bots? Watch the illustrated guide first. An animated walkthrough of @BotFather — /newbot, choosing a username, copying the token safely, the admin bot, and running the installer. Create your bot →

The add-on costs $3.99 / month or $39.99 / year and is included in the Enterprise plan. New accounts can try it free: every account starts with a 3-day Enterprise trial, no card needed.

What your clients get

• Account linking by email or username, confirmed with a login on your website, so nobody can link someone else's account.
• Instant notifications: order codes, completed and rejected orders, added funds and login alerts. Each client can turn each notification on or off.
• Balance, order history and order search, available at any time.
• Ordering from Telegram: the client picks a service, sees their own price (client-group discounts included), sends one or more IMEIs and confirms. DHRU places the order exactly as the website would, with the same balance check, validation and supplier routing. A double tap never creates a second order.
• Broadcasts: send a message to all linked clients from the dashboard.

What you and your staff get (admin bot)

• Add funds to or debit a client's balance.
• User lookup with balance and history.
• Today's report, orders review, providers and panel health.
• Several bot admins, so your staff can help.

Setup

1. Create a bot with @BotFather. In Telegram open @BotFather, send /newbot, enter your panel name and a username ending in bot, then copy the token it sends you. See every screen in the illustrated guide →
2. Paste the token and your panel URL. In the dashboard open Telegram & DHRU → DHRU client bot. Enter the panel name your clients will see, the address they use to log in (for example https://your-panel.com), the bot token, and optionally your support username and welcome message. Click Save.
3. Install the connector on your panel. Pick one:
   • File manager (easiest): download zyvopay_install.php, open your hosting panel (aaPanel, cPanel, Plesk, DirectAdmin…) → File Manager, upload it to your DHRU folder (the one that contains index.php and configs/) and press Run installer. The installer sets everything up, checks it and deletes itself. The download is made for your panel and works for 24 hours.
   • SSH: paste the one-line command shown on the same page into a terminal on your server.
   The status card turns Connected by itself. No cron job is needed: ZyvoPay syncs your panel every 30 seconds.
4. Turn on ordering. Under Ordering from Telegram switch on Clients can place IMEI orders from the bot. The installer already put the order adapter in place. In the same place, pick the notifications your clients receive and the copies you get as the owner.
5. Share the bot. Post the bot's link (t.me/your_bot) on your website, in your client area and in your channels. Clients press Start and link their account.

Admin bot setup

1. In @BotFather send /newbot again and create a second bot (for example "Team Unlock Admin"). See how →
2. Paste its token in Admin bot on the DHRU client bot page, choose your timezone (used for "today" reports) and a per-action limit for staff, then press Save.
3. Press Connect my Telegram as owner and open the one-time link — you are now the owner.
4. Invite staff from the bot: 👥 Bot Admins → Invite admin (one link per person, valid 24 hours). You can make a staff member read-only or remove them at any time, and you get a message every time staff add or debit funds.

Add funds and debit use DHRU's own Add credit and Rebate credit, so the client's statement shows them exactly like changes made in the admin area. Every change asks for confirmation, is checked against the balance afterwards and is recorded with the admin's name.

Migrating an existing bot

Already have a bot your clients use? Paste its token in step 2 instead of creating a new one. Your linked clients stay connected; they don't need to do anything.

Troubleshooting

Run the selftest

Over SSH (or your hosting panel's terminal), in your DHRU folder:

php zyvopay_bridge.php selftest

It checks PHP and its extensions, the config, the data folder, the database connection, the DHRU tables, the order adapter and a signed test call to ZyvoPay. Fix every FAIL line. WARN lines are about optional features. With ordering set up it prints Telegram ordering: DHRU order adapter installed.

Ordering fails: callback folder whitelist

Ordering uses modules/gateways/callback/zyvopay_bridge_core.php. DHRU's modules/gateways/callback/.htaccess only allows the files in its whitelist, so it must contain zyvopay_bridge_core:

<FilesMatch "^(zyvopay_bridge_core|zyvopay_callback|…)\.php$">

Without it the bot falls back to DHRU's reseller API, which only works for clients who have API access enabled.

"Test connection" returns 403: panel blocks unknown PHP files

Some panels ship a root .htaccess (or a Nginx rule) that only lets known PHP files run. Allow zyvopay_bridge.php by adding zyvopay_bridge to that whitelist:

<FilesMatch "^(index|viewinvoice|…|zyvopay_bridge)\.php$">

DHRU updates can restore the original file, so check it again after updating your panel. Behind Cloudflare or another WAF, allow POST /zyvopay_bridge.php or turn off the challenge for that path.

aaPanel / Nginx

Nginx ignores .htaccess. Keep the connector's folder private by adding this to the site's config (Website → Conf):

location ^~ /zyvopay_bridge/ { deny all; return 404; }

Security

• The connector only reads your DHRU database. Orders go through DHRU's own order functions, never direct database writes.
• Every request between ZyvoPay and your panel is signed with HMAC-SHA256 and expires after 5 minutes. The order adapter only answers signed requests from your own server, each with a one-time nonce.
• To cut access, delete zyvopay_bridge/config.php on your panel.