Skip to main content
GET
/
open
/
institution
/
otc
/
api
/
recharge
/
detail
Query OTC Deposit Order Detail
curl --request GET \
  --url https://openplatform.gateapi.io/open/institution/otc/api/recharge/detail \
  --header 'X-GatePay-Certificate-ClientId: <x-gatepay-certificate-clientid>' \
  --header 'X-GatePay-Nonce: <x-gatepay-nonce>' \
  --header 'X-GatePay-On-Behalf-Of: <x-gatepay-on-behalf-of>' \
  --header 'X-GatePay-Signature: <x-gatepay-signature>' \
  --header 'X-GatePay-Timestamp: <x-gatepay-timestamp>'
{
  "code": "0",
  "message": "success",
  "status": "success",
  "data": {
    "orderId": "71347515709194240",
    "status": "PENDING",
    "createTime": 1768973860523,
    "clientOrderId": "merchant-otc-deposit-20260415-001",
    "promoCode": "",
    "gate_bank_info": {
      "bankName": "Bank of Example",
      "bankAccountName": "Gate Pay OTC Collection",
      "countryId": 44,
      "country_name": "United Kingdom",
      "address": "1 Example Street, London",
      "iban": "GB11AAAA22223333444455",
      "swift": "ABCDEFGHXXX",
      "remittanceLineNumber": "021000021",
      "agentBankName": "",
      "agentBankSwift": "",
      "transfer_remark": "ORDER 71347515709194240"
    }
  }
}

​
Overview

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

​
Notes

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.

​
X-GatePay-On-Behalf-Of
string
required

Required delegated-subject header. Provide the initiating account ID for this request. For institution merchant APIs, this is typically the target sub-account ID; for institution charge and transfer APIs, it can be either an institution account ID or a sub-account ID.

Query Parameters

​
orderId
string
required

Gate OTC order ID.

Response

200 - application/json

Success

​
code
string

Business response code.

​
message
string

Business response message.

​
status
string

Top-level request status.

​
data
object

Deposit order payload.