Skip to main content
POST
/
merchant
/
open
/
institution
/
v1
/
pay
/
fixedaddress
/
evm
/
save
Create EVM Chain Static Collection Address
curl --request POST \
  --url https://openplatform.gateapi.io/merchant/open/institution/v1/pay/fixedaddress/evm/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",
  "callbackUrl": "https://www.abc.com/callback",
  "chianCurrencyInfos": [
    {
      "chain": "ETH",
      "currencies": [
        "DAI",
        "USDT"
      ]
    }
  ]
}
'
{
  "status": "SUCCESS",
  "code": "000000",
  "errorMessage": "",
  "data": {
    "channelId": "susie",
    "address": "0xE74ac03A2d34A9cEce0A6547b1758C7A8fA10230",
    "callbackUrl": "https://www.abc123.com/callback",
    "chainInfos": [
      {
        "chainShowEn": "BSC/BEP20",
        "currencies": [
          "USDT"
        ]
      }
    ]
  }
}

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 /merchant/open/institution/v1/pay/fixedaddress/evm/save endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above. For the same customer, create a static collection address that can correspond to multiple networks, applicable only to EVM networks.

​
Notes

  • Under the same channelId, only one static collection address is allowed per network, and duplicate creation is not permitted.
  • 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, Only letters, numbers, underscores (_), and hyphens (-) are allowed. The maximum length is 50 bytes.

​
callbackUrl
string
required

Callback URL for collection notifications, The length must not exceed 128 bytes.

​
chianCurrencyInfos
object[]
required

Network and currency information.

Response

200 - application/json

Successful response

​
status
enum<string>

API response result, SUCCESS or FAIL.

Available options:
SUCCESS,
FAIL
​
code
string

Response error code.

​
errorMessage
string

Error description.

​
data
object