Skip to main content
GET
Get Fee Rule Configuration Detail

Overview

This page documents the institution-only API that returns the effective fee-setting snapshot for a sub-account at a specified time. Full fields, request parameters, and examples are rendered from the OpenAPI definition above.

Notes

  • Query the effective configuration for a sub-account at a specified time. If no time is provided, the current effective configuration is returned.
  • It uses X-GatePay-MerchantId to identify the main-merchant context and does not use X-GatePay-On-Behalf-Of.
  • For shared signing rules, see /api-reference/version/100/en/common/securityAndSignature.

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.

Query Parameters

sub_merchant_id
string
required

Sub-account ID.

effective_date
string

Query time in YYYY-MM-DD HH:mm:ss format. If omitted, the current effective configuration is returned.

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