Skip to main content
POST
/
open
/
institution
/
otc
/
api
/
recharge
/
confirm
Confirm OTC Deposit Payment Completed
curl --request POST \
  --url https://openplatform.gateapi.io/open/institution/otc/api/recharge/confirm \
  --header 'Content-Type: multipart/form-data' \
  --header 'X-GatePay-Certificate-ClientId: <x-gatepay-certificate-clientid>' \
  --header 'X-GatePay-Nonce: <x-gatepay-nonce>' \
  --header 'X-GatePay-Signature: <x-gatepay-signature>' \
  --header 'X-GatePay-Timestamp: <x-gatepay-timestamp>' \
  --form orderId=71347515709194240 \
  --form file='@example-file'
{
  "code": "<string>",
  "status": "<string>",
  "errorMessage": "<string>",
  "data": {}
}

​
Overview

This page documents the POST /open/institution/otc/api/recharge/confirm endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above.

​
Notes

​
Supplemental Field Notes

  • client_order_id: merchant order ID retained for compatibility with the legacy confirm-paid request.
  • If both orderId and client_order_id are provided, prefer the current order-ID-based flow and upload the payment receipt file according to the latest OpenAPI definition.

​
Institution Notes

  • Institutional requests must include X-GatePay-On-Behalf-Of to specify the institutional sub-account to operate on.

Headers

​
X-GatePay-Certificate-ClientId
string
required

Merchant application client ID used to identify the calling app.

​
X-GatePay-Signature
string
required

HMAC signature generated from the request according to GatePay signing rules.

​
X-GatePay-Timestamp
string
required

Unix timestamp used for replay protection and signature verification.

​
X-GatePay-Nonce
string
required

Random nonce used together with the timestamp to prevent replay attacks.

Body

multipart/form-data
​
orderId
string
required

OTC deposit order ID to confirm.

​
file
file
required

Payment receipt file. Max 4 MB. Supported formats: jpg, jpeg, png.

​
client_order_id
string

Merchant order ID, retained for compatibility with the legacy confirm-paid request.

Response

200 - application/json

Success

​
code
string

Business response code.

​
status
string

Top-level request status.

​
errorMessage
string

Error message when the request fails.

​
data

Business response payload.