Query for the payment token of a binding
Query for the payment token of a binding
- application/json
- application/xml
- application/x-www-form-urlencoded
Request Body required
Agreement Query
- app_id int64 required
The unique ID of the application will be provided after the merchant registered successfully with Zalopay.
- app_trans_id string required
Unique transaction ID of application, format: yyMMddxxxxxxxxx. Max length is 40. For example: 180208181007242
- req_date int64 required
Current timestamp in milliseconds.
- mac string required
It is signature of request. It's calculated by following input: hmacinput = app_id +
|
+ apps_trans_id +|
+ req_date; and use sha256 with app's hmac key as sign key.Please refer to secure data transmission for detailed information.
Request Body required
Agreement Query
- app_id int64 required
The unique ID of the application will be provided after the merchant registered successfully with Zalopay.
- app_trans_id string required
Unique transaction ID of application, format: yyMMddxxxxxxxxx. Max length is 40. For example: 180208181007242
- req_date int64 required
Current timestamp in milliseconds.
- mac string required
It is signature of request. It's calculated by following input: hmacinput = app_id +
|
+ apps_trans_id +|
+ req_date; and use sha256 with app's hmac key as sign key.Please refer to secure data transmission for detailed information.
Request Body required
Agreement Query
- app_id int64 required
The unique ID of the application will be provided after the merchant registered successfully with Zalopay.
- app_trans_id string required
Unique transaction ID of application, format: yyMMddxxxxxxxxx. Max length is 40. For example: 180208181007242
- req_date int64 required
Current timestamp in milliseconds.
- mac string required
It is signature of request. It's calculated by following input: hmacinput = app_id +
|
+ apps_trans_id +|
+ req_date; and use sha256 with app's hmac key as sign key.Please refer to secure data transmission for detailed information.
- 200
- 405
OK
- application/json
- Schema
- Example (from schema)
Schema
- return_code integer
Return codes:
1 - SUCCESS
2 - FAILED
3 - PENDING
- return_message string
- sub_return_code integer
- sub_return_message string
data object
app_id int64The app id of the merchant.
app_trans_id stringThe merchant's unique id for the binding.
binding_id stringThe id of binding has been confirmed in the Zalopay system.
pay_token stringThe public token is used when doing auto-debit.
server_time int64Server timestamp in seconds.
merchant_user_id stringThe identifier field in bind request.
status integer1: Confirmed, 3: Cancelled, 4: Disabled
msg_type integerType of message: 1: The user confirms an agreement 2: The user updates the agreement
zp_user_id stringThe identifier of Zalopay user per merchant app_id.
masked_user_phone stringMasked user phone (Ex: masked_user_phone: "****6938")
{
"return_code": 0,
"return_message": "string",
"sub_return_code": 0,
"sub_return_message": "string",
"data": {
"app_id": 0,
"app_trans_id": "string",
"binding_id": "string",
"pay_token": "string",
"server_time": 0,
"merchant_user_id": "string",
"status": 0,
"msg_type": 0,
"zp_user_id": "string",
"masked_user_phone": "string"
}
}
Invalid input