Skip to main content
POST
Create Fee Rule

Overview

This page documents the institution-only API for creating the first markup rule for a sub-account. Full fields, request payloads, and examples are rendered from the OpenAPI definition above.

Notes

  • Create the first markup rule for a specified sub-account. After creation, the sub-account is charged with the base rate plus the configured markup.
  • It uses X-GatePay-MerchantId to identify the main-merchant context and does not use X-GatePay-On-Behalf-Of.
  • If the sub-account already has an active or pending rule, use the upgrade endpoint instead.

Headers

X-GatePay-Certificate-ClientId
string
required

Application ClientId.

X-GatePay-Signature
string
required

HMAC-SHA512 signature generated with the Payment API Secret.

X-GatePay-Timestamp
string
required

Millisecond timestamp; the difference from server time must not exceed 30 seconds.

X-GatePay-Nonce
string
required

Random nonce used for replay protection.

X-GatePay-MerchantId
string
required

Main merchant ID. This header identifies the institution main-merchant context for this fee-setting API set.

Body

application/json
sub_merchant_id
string
required

Sub-account ID.

Example:

"123456789"

r_markup
number
required

Percentage markup. Must not be null; 0 is allowed.

Example:

0.001

effective_date
string
required

Effective time in yyyy-MM-dd HH:mm:ss format.

Example:

"2026-04-17 00:00:00"

f_markup
number

Fixed markup amount in USDT. Defaults to 0 when omitted.

Example:

0

due_date
string | null

Expiration time in the same format as effective_date. Omit for an open-ended rule.

Example:

"2026-12-31 23:59:59"

Response

200 - application/json

Successful response.

status
enum<string>

API processing status.

Available options:
SUCCESS,
FAIL
code
string

Business result code.

Example:

"000000"

errorMessage
string

Error message. Empty string on success.

Example:

""

data
object