Secondary Payout Verification
Before the payout order is actually processed for payment, the platform will send a request to the verification endpoint provided by the merchant to conduct a secondary check on the order, enhancing transaction security. When receiving the request, returning true indicates successful verification and normal payout processing; returning false indicates verification failure, resulting in payout failure and refund of the deducted payout amount. If the API request encounters an error, it defaults to failure. Enabling this feature requires providing the API URL to platform personnel.
Request Specifications
- Request URL: Verification URL configured on the platform by the merchant
- Request Method:
POST - Content-Type:
application/json; charset=utf-8
Verification Logic
| Response / Status | Verification Result | Action Taken by Platform |
|---|---|---|
true | Success | Proceed with normal payout |
false | Failed | Payout failed; refund deducted amount |
| Timeout / Interface Error | Default Failed | Payout failed; refund deducted amount |
Request Header Parameters
| Parameter | Example | Required | Type | Description |
|---|---|---|---|---|
| merchantNo | M1639466186292 | Yes | string | Merchant Number |
| sign | e10adc3949ba59abbe56e057f20f883e | Yes | string | Signature (refer to Global Specification) |
Request Body Example
json
{
"timestamp": "1639466186292",
"merchantOrderNo": "ORDER_123456789",
"platOrderNo": "876324486452871168",
"amount": "100.00",
"bankCode": "BAC",
"accountNo": "111111111",
"accountName": "accountName"
}Request Body Field Definitions
| Field | Required | Type | Description |
|---|---|---|---|
| timestamp | Yes | string | Timestamp |
| merchantOrderNo | Yes | string | Merchant Order Number (letters + numbers, max length 32) |
| platOrderNo | Yes | string | Platform Order Number |
| amount | Yes | string | Amount |
| bankCode | Yes | string | Bank Code |
| accountNo | Yes | string | Bank Account Number |
| accountName | Yes | string | Bank Account Holder Name |
