🔧 T3 Admin - API Settings & Logs

NBN Management System (T3 User) v1.0

GET /api/t3systemadmin/api-keys
POST /api/t3systemadmin/api-keys/generate-qr

🔐 Secure Payment Gateway

Signature Method: SHA512(payload + api_key + secret_key + merchant_key)

Payload Format: Sorted key-value pairs as query string (key1=value1&key2=value2)

Note: secret_key is NOT sent in request - backend looks it up from database using api_key. merchant_key must be sent and must match the API key's merchant_key.

📤 Request Payload Structure

Field Description Type Required
api_key Your API key for authentication string Yes
merchant_key Merchant key that matches your API key string Yes
signature SHA512 hash of (payload + api_key + secret_key + merchant_key) string Yes
data.amount Payment amount number (float) Yes
data.currency Currency code (USDT, USD, SGD) string No
data.type Payment type (fixed, custom) string No
data.markup_percentage Optional markup percentage number (float) No
data.network bsc, polygon, or tron string No (default bsc)
data.asset_id Enabled payment asset id (disambiguates multi-token chains) string No

🔐 Signature Generation Example

Complete Signature String Format:

api_key=test_key&data.amount=100&data.currency=USD&data.type=fixed&merchant_key=merchant_key

Step-by-Step Breakdown:

  1. Build Payload: Sort the data object keys alphabetically and create query string:
    amount=100¤cy=USD&type=fixed
  2. Concatenate for Signature: Combine in this exact order (no separators):
    payload + api_key + secret_key + merchant_key
    amount=100¤cy=USD&type=fixedtest_keyyour_secret_key_heremerchant_key
  3. Generate SHA512 Hash:
    signature = SHA512("amount=100¤cy=USD&type=fixedtest_keyyour_secret_key_heremerchant_key")

âš ī¸ Note: Replace "your_secret_key_here" with your actual secret key. The secret_key is NOT sent in the request - it's only used locally to generate the signature.

âš ī¸ Important: The payload keys (from data object) must be sorted alphabetically. The signature string concatenates in this exact order: payload + api_key + secret_key + merchant_key (no separators between them).

API Credentials

Used locally for signature generation only - NOT sent in request

Payment Details

Chain for the deposit QR (must match merchant deposit addresses).
When set, must match an enabled payment asset on the selected network (see PAYMENT_ASSETS_JSON / merchant supported-assets).
POST /api/t3systemadmin/api-keys/check-payment-status

🔐 Check Payment Status

Signature Method: SHA512(api_key + secret_key + merchant_key + session_id)

Purpose: Check if a payment is completed or pending using the session_id from QR generation

Note: secret_key is NOT sent in request - backend looks it up from database using api_key.

📤 Request Payload Structure

Field Description Type Required
api_key Your API key for authentication string Yes
merchant_key Merchant key that matches your API key string Yes
session_id Session ID returned when you generate a QR payment string Yes
signature SHA512 hash of (api_key + secret_key + merchant_key + session_id) string Yes

API Credentials

Used locally for signature generation only - NOT sent in request
This is the session_id returned when you generate a QR payment
POST /api/t3systemadmin/api-keys/cancel-order

🔐 Cancel Order

Signature Method: SHA512(api_key + secret_key + merchant_key + session_id)

Purpose: Cancel an order by setting it to expired and canceled status. The order will be marked as canceled and expires_at will be set to current time.

Note: secret_key is NOT sent in request - backend looks it up from database using api_key. Cannot cancel already completed or canceled orders.

📤 Request Payload Structure

Field Description Type Required
api_key Your API key for authentication string Yes
merchant_key Merchant key that matches your API key string Yes
session_id Session ID of the order to cancel string Yes
signature SHA512 hash of (api_key + secret_key + merchant_key + session_id) string Yes

API Credentials

Used locally for signature generation only - NOT sent in request
The session_id of the order you want to cancel
GET /api/t3systemadmin/api-logs
PUT /api/t3systemadmin/callback-settings