SYSTEM ONLINE
GSM THEME : READY & SUPPORTED
BINANCE C2C : 99.99% UPTIME
USDT TRC20 : INSTANT SCAN
BEP20 NODE : BLOCKCHAIN SYNCED
BKASH TOKENIZED : ACTIVE
DHRU FUSION : API CONNECTED
GSM THEME : READY & SUPPORTED
BINANCE C2C : 99.99% UPTIME
USDT TRC20 : INSTANT SCAN
BEP20 NODE : BLOCKCHAIN SYNCED
Dashboard Login

API Introduction

Welcome to the BD Pay Developer API engine. Our high-performance REST API nodes allow you to route, process, and auto-verify automated Crypto payments (BEP20 / TRC20 / Binance Pay) and local payment methods safely inside your custom applications or automated billing setups.

Production API Base Endpoint Node: https://bdpay.co/api/v1

Authentication Loop

All outbound network security handshake queries require explicit verification layers passed directly inside your custom HTTP Request Headers arrays.

// đŸ›°ī¸ Internal Security Header Authentication Structure
GET /api/v1/balance
HTTP Headers:
X-API-KEY: your_merchant_api_key_string
X-API-SECRET: your_merchant_secret_key_hash

Create Payment Request Node

Use this specific route endpoint to dynamically declare a new system transactional record object and retrieve a secure checkout payment link session window for the target payee.

POST /payment/create
Parameter Type Description
amount float / numeric The expected transaction value in standard USD currency equivalent (Min 1.00).
order_id string Your unique alphanumeric internal order billing or reference ID (e.g. INV-1002).
method string Optional pre-set filter. Pass bep20, trc20, or binance to pre-select gateway mode.

PHP cURL Native Integration Example:

<?php
$api_target = "https://bdpay.co/api/v1/payment/create";

$post_payload = [
    'amount'   => 25.50,
    'order_id' => 'BDP-ORDER-' . time(),
    'method'   => 'bep20'
];

$ch = curl_init($api_target);
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_POST           => true,
    CURLOPT_POSTFIELDS     => http_build_query($post_payload),
    CURLOPT_HTTPHEADER     => [
        'X-API-KEY: your_merchant_api_key_string',
        'X-API-SECRET: your_merchant_secret_key_hash'
    ]
]);

$server_response = curl_exec($ch);
curl_close($ch);

$json_data = json_decode($server_response, true);
if (isset($json_data['success']) && $json_data['success'] === true) {
    header("Location: " . $json_data['checkout_url']);
    exit;
}
?>

Supported Crypto Ledger Protocols

The runtime engine natively monitors real-time transaction handshakes via distributed RPC endpoints across these specific chain protocol configurations:

BNB Smart Chain (BEP20)

Tracks ledger deposits automatically inside your designated BSC recipient address configuration using verified BscScan RPC nodes with block timestamp lock.

TRON Network (TRC20)

Synchronizes inbound token adjustments directly through persistent internal server cron jobs tied directly to TronGrid RPC infrastructure loops.

Instant Payment Notification (IPN / Callback)

Once blockchain metadata sync settles successfully, our engine issues an automated secure asynchronous POST hook back to your designated listener hook route containing signature data.

// đŸ›°ī¸ Sample Server-to-Server IPN Outbound Callback JSON Format
{
    "status": "success",
    "invoice_id": "API8F41A2D",
    "order_id": "INV-1002",
    "amount_received": "25.50",
    "crypto_method": "bep20",
    "signature_hash": "62e5b7c7b120f269c3a36237..."
}
NEW GUIDE

GSM Theme Integration Guide

GSM Theme (Laravel Platform) āĻ BD Pay āϗ⧇āϟāĻ“āϝāĻŧ⧇ āϝ⧁āĻ•ā§āϤ āĻ•āϰāĻžāϰ āϏāĻŽā§āĻĒā§‚āĻ°ā§āĻŖ āĻĒā§āϰāĻ•ā§āϰāĻŋāϝāĻŧāĻž āύāĻŋāĻšā§‡ āϧāĻžāĻĒ⧇ āϧāĻžāĻĒ⧇ āĻĻ⧇āĻ“āϝāĻŧāĻž āĻšāϞ⧋:

1 āϗ⧇āϟāĻ“āϝāĻŧ⧇ āĻ•ā§āϞāĻžāϏ āĻĢāĻžāχāϞ āφāĻĒāϞ⧋āĻĄ āĻ•āϰ⧁āύ

āφāĻĒāύāĻžāϰ GSM Theme āϏāĻžāĻ°ā§āĻ­āĻžāϰ⧇āϰ āĻĢāĻžāχāϞ āĻŽā§āϝāĻžāύ⧇āϜāĻžāϰ⧇ āϝāĻžāύ āĻāĻŦāĻ‚ āύāĻŋāĻšā§‡āϰ āϞ⧋āϕ⧇āĻļāύ⧇ Bdpay.php āĻĢāĻžāχāϞāϟāĻŋ āϤ⧈āϰāĻŋ āĻ•āϰ⧁āύ:

app/Services/Gateway/Bdpay.php

2 āϞ⧋āĻ—ā§‹ āφāĻĒāϞ⧋āĻĄ āĻ•āϰ⧁āύ

BD Pay āĻāϰ āϞ⧋āĻ—ā§‹āϟāĻŋ āĻĄāĻžāωāύāϞ⧋āĻĄ āĻ•āϰ⧇ āφāĻĒāύāĻžāϰ GSM Theme āĻāϰ āĻĒāĻžāĻŦāϞāĻŋāĻ• āĻĢā§‹āĻ˛ā§āĻĄāĻžāϰ⧇ āφāĻĒāϞ⧋āĻĄ āĻ•āϰ⧁āύ:

public/resource/bdpay_logo.png

3 āĻ…ā§āϝāĻžāĻĄāĻŽāĻŋāύ āĻĒā§āϝāĻžāύ⧇āϞ āĻ•āύāĻĢāĻŋāĻ—āĻžāϰ⧇āĻļāύ

  • GSM Theme āĻāϰ Admin Panel > Payment Gateways āĻ āĻĒā§āϰāĻŦ⧇āĻļ āĻ•āϰ⧁āύāĨ¤
  • BD PAY āϗ⧇āϟāĻ“āϝāĻŧ⧇āϟāĻŋ āϖ⧁āρāĻœā§‡ āĻĒā§‡ā§Ÿā§‡ Edit āĻŦāĻžāϟāύ⧇ āĻ•ā§āϞāĻŋāĻ• āĻ•āϰ⧁āύāĨ¤
  • āφāĻĒāύāĻžāϰ BD Pay āĻŽāĻžāĻ°ā§āĻšā§‡āĻ¨ā§āϟ āĻĄā§āϝāĻžāĻļāĻŦā§‹āĻ°ā§āĻĄ āĻĨ⧇āϕ⧇ āĻĒā§āϰāĻžāĻĒā§āϤ API Key āĻāĻŦāĻ‚ API Secret āĻŦāϏāĻŋā§Ÿā§‡ āĻĻāĻŋāύāĨ¤
  • Settlement Currency āĻĄā§āϰāĻĒāĻĄāĻžāωāύ āĻĨ⧇āϕ⧇ āφāĻĒāύāĻžāϰ āĻĒāĻ›āĻ¨ā§āĻĻ āĻ…āύ⧁āϝāĻžā§Ÿā§€ USD ($) āĻŦāĻž BDT (ā§ŗ) āϏāĻŋāϞ⧇āĻ•ā§āϟ āĻ•āϰ⧇ Save āĻ•āϰ⧁āύāĨ¤
DHRU MODULE

Dhru Fusion Integration Guide

Dhru Fusion GSM āϏāĻžāĻ°ā§āĻ­āĻžāϰ āϏāĻĢāϟāĻ“āϝāĻŧā§āϝāĻžāϰ⧇ BD Pay āĻĒā§āϞāĻžāĻ—āχāύ āχāύāĻ¸ā§āϟāϞ āĻ•āϰāĻžāϰ āύāĻŋāϝāĻŧāĻŽ:

1 āĻŽāĻĄāĻŋāωāϞ āĻĢāĻžāχāϞāϗ⧁āϞ⧋ āφāĻĒāϞ⧋āĻĄ āĻ•āϰ⧁āύ

āφāĻĒāύāĻžāϰ Dhru Fusion āϰ⧁āϟ āĻĢā§‹āĻ˛ā§āĻĄāĻžāϰ⧇ āύāĻŋāĻšā§‡āϰ āĻĄāĻŋāϰ⧇āĻ•ā§āϟāϰāĻŋ āĻ…āύ⧁āϝāĻžā§Ÿā§€ āĻĢāĻžāχāϞāϗ⧁āϞ⧋ āĻāĻ•ā§āϏāĻŸā§āĻ°ā§āϝāĻžāĻ•ā§āϟ āĻ•āϰ⧇ āĻĻāĻŋāύ:

📁 modules/gateways/bdpay.php
📁 modules/gateways/bdpay/bdpay_process.php
📁 modules/gateways/bdpay/logo.png

2 Dhru Fusion āĻ…ā§āϝāĻžāĻĄāĻŽāĻŋāύ āĻĒā§āϝāĻžāύ⧇āϞ āϏāĻ•ā§āϰāĻŋāϝāĻŧāĻ•āϰāĻŖ

  • Dhru Fusion āĻāϰ āĻ…ā§āϝāĻžāĻĄāĻŽāĻŋāύ⧇ āϞāĻ—āχāύ āĻ•āϰ⧇ Settings > Payment Gateways āĻ āϝāĻžāύāĨ¤
  • All Gateways āĻŸā§āϝāĻžāĻŦ āĻĨ⧇āϕ⧇ BD PAY āϗ⧇āϟāĻ“ā§Ÿā§‡āϟāĻŋ āϖ⧁āρāĻœā§‡ āĻŦ⧇āϰ āĻ•āϰ⧇ Activate āĻŦāĻžāϟāύ⧇ āĻ•ā§āϞāĻŋāĻ• āĻ•āϰ⧁āύāĨ¤
  • āϗ⧇āϟāĻ“ā§Ÿā§‡ āϏ⧇āϟāĻŋāĻ‚āϏ⧇ āĻ—āĻŋā§Ÿā§‡ āφāĻĒāύāĻžāϰ BD Pay API Key āĻ“ API Secret āĻĻāĻŋāύāĨ¤
  • Exchange Rate āĻ āĻŋāĻ• āĻ•āϰ⧁āύ (āϝ⧇āĻŽāύ: 1 USD = āĻ•āϤ BDT āĻšāĻŦ⧇) āĻāĻŦāĻ‚ Save Changes āĻĻāĻŋāύāĨ¤

💡 āĻĒā§āϰ⧋ āϟāĻŋāĻĒ: Dhru Fusion āĻ āĻŸā§‡āĻ¸ā§āϟ āĻĒ⧇āĻŽā§‡āĻ¨ā§āϟ āϏāĻĢāϞ āĻšāĻ“ā§ŸāĻžāϰ āĻĒāϰ āχāύāĻ­ā§Ÿā§‡āϏ āĻ…āĻŸā§‹āĻŽā§‡āϟāĻŋāĻ• āĻĒ⧇āχāĻĄ āĻšā§Ÿā§‡ āĻ•ā§āϞāĻžāϝāĻŧ⧇āĻ¨ā§āĻŸā§‡āϰ āĻŦā§āϝāĻžāϞ⧇āĻ¨ā§āϏ āĻĢāĻžāĻ¨ā§āĻĄ āĻ…ā§āϝāĻžāĻ•āĻžāωāĻ¨ā§āĻŸā§‡ āĻ¸ā§āĻŦ⧟āĻ‚āĻ•ā§āϰāĻŋ⧟āĻ­āĻžāĻŦ⧇ āĻ•ā§āϰ⧇āĻĄāĻŋāϟ āĻšā§Ÿā§‡ āϝāĻžāĻŦ⧇āĨ¤

System Exception & Error Declarations

Inbound request processing failure routes return specific standard JSON failure payloads:

{"success": false, "error_code": "AUTH_FAILED", "message": "Invalid Username or API Access Key! Access Denied."}

{"success": false, "error_code": "IP_RESTRICTED", "message": "API Request source IP does not match the protected host locker routing node configuration."}
Telegram WhatsApp