USDT Recharge API Documentation: CrossingPay Integration Guide

Overview

This documentation outlines the USDT recharge API process for CrossingPay's merchant integration. The interface enables seamless cryptocurrency deposits for user accounts.

Important Note:
This V1 interface has been deprecated and upgraded to a higher-performance V2 version for dedicated network solutions.

API Specifications

1. Basic Parameters

Endpoint:
POST /api/merchant/TraderRechargeorder

Purpose:
Processes user cryptocurrency deposits to merchant accounts.

2. Request Parameters

Parameter	Required	Description
username	Yes	Platform username (e.g., a123456)
appid	Yes	Merchant API key
localusermark	Yes	Unique user identifier for callback processing
address	Yes	Generated deposit address (must match user-specific address for tracking)
orderid	Yes	Merchant order ID (50-character limit)
amount	Yes	Expected deposit amount (system accepts actual transferred amount if mismatch occurs)
notify_url	No	Asynchronous notification URL (overrides default callback if provided)
sign	Yes	Request signature

3. Response Parameters

Parameter	Description
status	1 = Success, 0 = Failure
err	Error description (when status = 0)
data	Order details (when status = 1)
data.ordersn	System-generated UUID (50-character limit)

Success Example:

{
    "status": 1,
    "data": {
        "msg": "Operation succeeded",
        "ordersn": "cz-7773c1e0*****fc698d2"
    }
}

4. Callback Process

Notification Method:
Asynchronous POST request to merchant's specified URL

Callback Parameters:

array (
  'orderid' => 'sh-56073d***8a2ff5521a', // Original merchant order ID
  'localusermark' => '1', // User identifier
  'amount' => '30000', // Actual received amount (divide by 10000 for precision)
  'appid' => 'VunT***h1l8', // Merchant API ID
  't' => '1662299838', // UNIX timestamp
  'sign' => '237A3D3EEFE6***F408EA7EFFB1F2' // Verified signature
)

Verification Requirement:
Always validate callback signatures using CrossingPay's signature guide

FAQ Section

Q1: What happens if the deposited amount differs from the requested amount?

The system will accept the actual transferred amount while logging the discrepancy for merchant review.

Q2: How should merchants handle callback notifications?

Implement server-side validation of the sign parameter before processing any deposit confirmations.

Q3: What's the maximum order ID length?

50 characters maximum—we recommend using UUID v4 formats.

Q4: Why was my deposit not detected?

Ensure the deposit address matches the exact generated address for the specific user transaction.

👉 Explore advanced payment solutions for high-volume merchants needing dedicated infrastructure.

Q5: How frequently are callbacks retried?

The system attempts delivery 6 times over 30 minutes before marking the notification as failed.

Q6: What precision does the amount field use?

Divide callback amounts by 10,000—a value of 30000 represents 3.0000 USDT.

Best Practices

Address Management: Generate fresh deposit addresses for each transaction
Callback Security: Always verify signatures before updating balances
Error Handling: Implement transactional logging for all API responses

👉 Learn about enterprise-grade crypto solutions suitable for institutional trading platforms.

Note: This interface supports mainnet USDT-ERC20 deposits only. For other chains or tokens, consult CrossingPay's multi-chain documentation.