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) and multi-channel local assets safely inside your custom applications or automated billing setups.

Production API Base Endpoint Node: https://paidfile.net/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 Template
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
// 🚀 Outbound Payment Dispatch Configuration Payload
$api_target = "https://paidfile.net/api/v1/payment/create";

$post_payload = [
    'amount'   => 25.50,
    'order_id' => 'BDP-ORDER-' . time(),
    'method'   => 'bep20' // Forces direct smart chain layout selection
];

$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) {
    // 🛰️ Route customer to the secure escrow checkout layout link
    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 BscScan network endpoints.

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..."
}

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."}