Payment Submit API¶
Tip
- All requests are
Postrequests, and the data format isjson
Brief Description¶
- P2P-H2H: Requires the payment API and the current API to work together.
- After completing the payment, the user needs to submit the transaction ID on the checkout page.
Request URL¶
/v1/vexora/payInSubmit
Request Method¶
- Method: POST
- Content-Type: application/json
Header¶
| Header | Required | Type | Description |
|---|---|---|---|
| merchantNo | Yes | String | None |
Body¶
| Parameter Name | Required | Type | Description |
|---|---|---|---|
| sign | Yes | String | Except for sign, the remaining fields should be sorted by the first letter to form key1=value1key2=value2, and then use the app secret as salt to perform MD5 encryption. The final sign should be in lowercase. |
| timestamp | Yes | long | Timestamp (e.g., 1715941383720) |
| platFormTradeNo | Yes | String | Unique platform order number |
| utr | Yes | String | Transaction ID |
Example of Request Parameters¶
{
"sign": "0be92a962072b1786a01a2cab4891a1d",
"timestamp": "1728609257212",
"platFormTradeNo": "test_00000008",
"utr": "11111111"
}
Response Result¶
Tip
You can use the code parameter to determine the status: - code = 0000: The submission was successful. Await a subsequent callback or query for the final result. - For any other code value: The order is being processed. Await a subsequent callback or query for the final result.
| Parameter Name | Required | Type | Description |
|---|---|---|---|
| msg | Yes | String | Request result (when returning "success", it only indicates that this request was successful; it should not be used for merchant-side logic judgment) |
| code | Yes | String | Request response code (when returning "0000", it only indicates that this request was successful; it should not be used for merchant-side logic judgment). |
| timestamp | Yes | String | Transaction time |
| success | Yes | Boolean | Transaction result |
| data | Yes | Boolean | Submit Results |