Skip to main content
POST
/
payment
/
open
/
institution
/
v1
/
pay
/
fixedaddress
/
save
Create Static Collection Address
curl --request POST \
  --url https://openplatform.gateapi.io/payment/open/institution/v1/pay/fixedaddress/save \
  --header 'Content-Type: application/json' \
  --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>' \
  --data '
{
  "channelId": "smart_shop",
  "chain": "ETH",
  "currencies": "DAI,USDT",
  "callbackUrl": "https://www.abc.com/callback"
}
'
{
  "status": "SUCCESS",
  "code": "000000",
  "errorMessage": "",
  "data": {
    "channelId": "smart_shop",
    "chain": "ETH",
    "address": "0x2EBa11a702F1d53c6e2F08278819e26E6e4a63ae",
    "currencies": [
      "DAI",
      "USDT"
    ],
    "callbackUrl": "https://www.abc.com/callback",
    "desc": "",
    "ChainShowEn": "ETH /ERC20"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.gate.com/llms.txt

Use this file to discover all available pages before exploring further.

Overview

This page documents the POST /payment/open/institution/v1/pay/fixedaddress/save endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above. Generates a static collection address based on the specified currency and network.

Notes

  • If a static collection address already exists for channelId + chain, the currencies and callbackUrl in the request update the existing bound information.
  • Authentication uses the standard GatePay signed headers.
  • This page documents the standard merchant endpoint.
  • For shared signing rules, see /api-reference/version/100/en/common/securityAndSignature.

Headers

X-GatePay-Certificate-ClientId
string
required

The clientId assigned when the merchant registers an application in the Gate merchant console.

Example:

"4186d0c6-6a35-55a9-8dc6-5312769dbff8"

X-GatePay-Signature
string
required

Request signature. GatePay uses this signature to verify whether the request is valid.

X-GatePay-Timestamp
string
required

UTC timestamp in milliseconds when the request is generated. GatePay will not process requests where the difference from the receive time exceeds 10 seconds.

Example:

"1672905655498"

X-GatePay-Nonce
string
required

Random string. Must comply with HTTP header rules; recommended length is within 32 characters, composed of digits and letters.

Example:

"9578"

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.

Body

application/json
channelId
string
required

Merchant channel ID, supports only letters, numbers, underscores, and hyphens, with a maximum length of 50 bytes

chain
string
required

Network name

currencies
string
required

Currencies to be earned at this static address, separated by commas (e.g., USDT,BTC)

callbackUrl
string
required

Callback URL for this channel, with a maximum length of 128 bytes

Response

200 - application/json

Successful response

status
enum<string>

Response result, SUCCESS or FAIL

Available options:
SUCCESS,
FAIL
Example:

"SUCCESS"

code
string

Response error code

errorMessage
string

Error description

data
object