Skip to main content
GET
/
payment
/
open
/
institution
/
v1
/
pay
/
address
/
supportedconvertcurrencies
Query Convert Supported Currencies
curl --request GET \
  --url https://openplatform.gateapi.io/payment/open/institution/v1/pay/address/supportedconvertcurrencies \
  --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>'
{
  "status": "SUCCESS",
  "code": "000000",
  "errorMessage": "",
  "data": {
    "currencies": [
      "BTC",
      "USD",
      "USDT",
      "ETH",
      "XRP",
      "ZEC",
      "GT",
      "BNB",
      "DOT",
      "SHIB",
      "LION"
    ]
  }
}

​
Overview

This page documents the GET /payment/open/institution/v1/pay/address/supportedconvertcurrencies endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above. Users can query the supported payment currency for the converted payment order, and then selects one to create an convert payment order

​
Notes

  • Authentication uses the standard GatePay signed headers.
  • This page documents the institution-path variant of the same API.
  • Except for sub-account creation and sub-account query APIs, institution requests should include X-GatePay-On-Behalf-Of.
  • For shared signing rules, see /api-reference/version/100/en/common/securityAndSignature.

Headers

​
X-GatePay-Certificate-ClientId
string
required

Merchant client ID, obtained from GatePay platform

​
X-GatePay-Signature
string
required

HMAC-SHA256 signature for request validation

​
X-GatePay-Timestamp
string
required

Timestamp in milliseconds, must not differ from server time by more than 5 minutes

​
X-GatePay-Nonce
string
required

Random nonce for replay attack prevention

​
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

​
currency
string
required

Currency of the order.

Response

200 - application/json

SUCCESS

​
status
string
​
code
string
​
data
object