Edit Client

curl --request PUT \
  --url https://openplatform.gateapi.io/v1/pay/channelmanage/update \
  --header 'Content-Type: application/json' \
  --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>' \
  --data '{}'

{
  "status": "SUCCESS",
  "code": "000000",
  "errorMessage": ""
}

Customer Management

Update Customer

Users edit clients and record information through this interface. The name of a client is required and must be unique under the same merchant; other attributes are not required. If you need to save a wallet address, you need to confirm the network; if not, the network can be left blank. Spare fields are set by merchants according to actual business scenarios. You can use a spare field to save certain attribute of your clients, e.g., country/region/business type.

PUT

pay

channelmanage

update

Edit Client

curl --request PUT \
  --url https://openplatform.gateapi.io/v1/pay/channelmanage/update \
  --header 'Content-Type: application/json' \
  --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>' \
  --data '{}'

{
  "status": "SUCCESS",
  "code": "000000",
  "errorMessage": ""
}

Overview

This page documents the PUT /v1/pay/channelmanage/update endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above. Update Client

Notes

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

Merchant client ID, obtained from GatePay platform

Example:

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

X-GatePay-Signature

string

required

HMAC-SHA256 signature for request validation

Example:

"672d5650dcc9bb22ebf25fa16c28d03c0e159d742a9176d4340a5da326d75dc8a2ec24c97fa6fc5d1533dd6e968863747e1d86a45e562cbe899f9ed7e9ca7f77"

X-GatePay-Timestamp

string

required

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

Example:

"1672905655498"

X-GatePay-Nonce

string

required

Random nonce for replay attack prevention

Example:

"9578"

Body

application/json

merchantChannelList

object[]

Client list,currently only supports adding one client record each time

Show child attributes

Response

200 - application/json

success

status

string

response status

code

string

response code

errorMessage

string

Error message

Query Customer

Delete Customer

⌘I

​Overview

​Notes

Headers

Body

Response

Overview

Notes