Checkout

Tip

• All requests are Post requests, and the data format is json

Brief Description

Request URL

• /v1/vexora/checkout

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 the sign, concatenate the remaining fields in alphabetical order to form key1=value1key2=value2, then use the app secret as salt to perform MD5 encryption. The sign should be in lowercase letters.
timestamp	Yes	String	Timestamp (e.g., 1715941383720)
amount	Yes	String	Payment amount (amounts with decimals are not recommended)
tradeNo	Yes	String	Transaction number (should be unique; suggested format: YYYYMMDDHHMMSS + random number)
name	Yes	String	Payer's name
mobile	Yes	String	Mobile number of the payee (10 digits beginning with 6, 7, 8, or 9; omit the 91 country code).
email	Yes	String	Payer's email (should use gmail.com domain, e.g., abc@gmail.com)
ipAddress	Yes	String	Payer's ipAddress
remark	No	String	Remarks; this field will be returned as is
notifyUrl	Yes	String	Asynchronous callback URL (e.g., https://www.abc.com/); if not provided, the system will redirect to the default success page
returnUrl	Yes	String	Redirect page after successful payment

Request Parameter Example

{
  "sign": "f53ee692f15d0329a1461373b67ff25a",
  "timestamp": "1724142041682",
  "tradeNo": "00000007",
  "amount": "300",
  "name": "abc",
  "mobile": "918234567890",
  "email": "123@qq.com",
  "ipAddress": "14.155.28.59",
  "remark": "000000",
  "notifyUrl": "https://google.com",
  "returnUrl": "http://abc.com/callback_page"
}

Response 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). For specific error codes, please refer to the business error code enumeration.
timestamp	Yes	String	Transaction time
success	Yes	String	Transaction result
data	Yes	Object	Returned object
data.platFormTradeNo	Yes	String	Platform order number, unique
data.status	Yes	String	Transaction results,Merchants can process subsequent workflows based on the returned status in the transaction result. For details, please refer to the status code reference table.
data.desc	Yes	String	Error description
data.remark	Yes	String	Content returned from the request (returned as is)
data.paymentLink	Yes	String	Payment link, i.e., the cash register

Example of Successful Return

{
    "msg": "success",
    "code": "0000",
    "timestamp": 1729945579983,
    "success": true,
    "data": {
        "platFormTradeNo": "8h7kold1d6g8fbmm",
        "status": "0015",
        "desc": "CREATED",
        "paymentLink": "https://www.kaixin199.info/payment/Maya/PHP60801Maya061484533"
    }
}

---