Deposit Confirm

Used for scenarios such as pay-to-account where the merchant needs to submit a payment receipt or voucher. If the upstream counter is used, the API can be ignored.

Endpoint

POST /v1/api/deposit/confirm

Request

Parameters

Key	Required	Type	Example	Description
`mcode`	Yes	string	`M10086`	Merchant ID
`sn`	Yes	string	`D202608020001`	Platform order number
`ref`	Yes	string	`1234567`	Passed-back tracking code (typically short; max 10 chars)
`ts`	Yes	string	`1785138705251`	Request milli timestamp len 13
`sign`	Yes	string	`c380be...`	Signature value

Example

{
  "mcode": "M10086",
  "sn": "D202608020001",
  "ref": "1234567",
  "ts": "1785138705251",
  "sign": "8jPS6eaid00qyRtJoMt4kE0ZFIv8vL6xauAbQmY27HA"
}

Response

Parameters

Field	Key	Type	Description
Status code	`code`	number	Response code, `0` means success
Response data	`data`	object	Response payload object
─ Merchant code	`data.mcode`	string	Merchant ID
─ Platform order no.	`data.sn`	string	Platform order number
─ Merchant order no.	`data.tno`	string	Merchant order number
─ Order status	`data.sts`	string	Order status
─ Ref data	`data.ref`	string	Ref data
─ Message	`data.msg`	string	Message
─ Extra data	`data.data`	object	Extra data. May not be present
─ Signature	`data.sign`	string	Response signature

Example

{
  "code": 0,
  "data": {
    "mcode": "M10086",
    "sn": "D202608020001",
    "tno": "T202608020001",
    "sts": "DS_SUCCESS",
    "data": {
      "ref": "REF202608020001"
    },
    "sign": "xxxx"
  }
}

Notes

If the order has already passed back a ref (already confirmed), the API returns the message already confirmed and makes no upstream call.
ref is the tracking code the merchant passes back; after the upstream confirms successfully it is also written to the order.