# Recon API Auth Specification
The V2 Recon API uses MD5 signature authentication. Merchants must follow the specifications below when calling the API.
# Request Specification
# Request Headers
| Field Name | Variable Name | Required | Type | Description |
|---|---|---|---|---|
| Merchant No | mchNo | Yes | String | Merchant number, assigned by the platform |
| App ID | appId | Yes | String | Application ID, assigned by the platform |
| Request Time | reqTime | Yes | String | Request timestamp, 10-digit Unix Timestamp in seconds (e.g. 1716888859) |
| Sign Type | signType | Yes | String | Fixed as MD5 |
| Signature | sign | Yes | String | Request signature, see signing rules |
# Signing Rules
- Sort all request parameters (except sign) by parameter name in ASCII ascending order
- Concatenate into a string using URL key-value pair format
- Append &key=API_KEY to the end of the concatenated string
- Perform MD5 operation on the final string to get a 32-bit lowercase sign value
# Signature Example
String to sign: appId=dev&country=DE&mchNo=M1621873433953&reqTime=1716888859&signType=MD5&key=your_api_key
Signature result: md5(string_to_sign) = abc123def456...
# Request Validity
The deviation between the request time (reqTime) and the server time must not exceed 300 seconds. Expired requests will be rejected.
# Amount Unit
All amount fields in the V2 Recon API use USD micro-units, where 1,000,000 = $1.00 USD.
| Amount | Micro-units Value |
|---|---|
| $1.00 | 1000000 |
| $0.50 | 500000 |
| $0.01 | 10000 |
Note
The V2 Recon API uses micro-units (1,000,000 = $1.00), which differs from the V1 Payment/Transfer API that uses cents (100 = $1.00).
# Error Codes
| Code | Description |
|---|---|
| 0 | Success |
| 1001 | Parameter missing |
| 1002 | Signature error |
| 1003 | Merchant not found |
| 1004 | App not found |
| 1005 | Request expired |
| 2001 | No permission |
| 9999 | System error |