Skip to main content
POST
Estimate Merchant Fees

Overview

This page documents the POST /payment/open/institution/payClearing/clearing/previewMerchantFee endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above.

Notes

  • Authentication uses the standard GatePay signed headers.
  • This page documents the institutional path version of the same endpoint.
  • Optional orderType and X-GatePay-Sub-MerchantId support revenue share preview.
  • Response adds institutionFeeAmount and settleAmount.
  • For shared signing rules, see /api-reference/version/100/en/common/securityAndSignature.

Headers

X-GatePay-Certificate-ClientId
string
required

Merchant ID

Example:

"mZ96D37oKk-HrWJc"

X-GatePay-Signature
string
required

Signature

Example:

"601d560c54d53412aca5901256f101e7078b5779f61f30bedfe9a5f0b92f049589952a151ea477371e4a99ac0e1c3cc8dec62654b3c6a1794ef981efe19232bc"

X-GatePay-Timestamp
string
required

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

Example:

"1726027137585"

X-GatePay-Nonce
string
required

Nonce

Example:

"2290830087"

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.

X-GatePay-Sub-MerchantId
string

Sub-merchant UID for institution sub-account. Optional; revenue share (markup) is calculated only when this header is provided.

Example:

"2124674730"

Body

application/json

Estimate merchant fee request parameters

orderCurrency
string
required

Order currency, e.g., USDT, USDC, etc.

Example:

"USDT"

accessMode
enum<integer>
required

Integration mode: 0=Gate Pay, 1=Web3 payment

Available options:
0,
1
Example:

0

scenario
enum<integer>
required

Transaction type (Scenario): 0=Collection

Available options:
0
Example:

0

orderAmount
string<decimal>
required

Order amount, must be greater than or equal to 0

Example:

"100.00"

orderType
enum<integer>

Order type. Optional values: 0-address payment, 1-checkout payment, 2-static QR code, 3-invoicing payment, 4-AI payment. If omitted, fallback rate applies.

Available options:
0,
1,
2,
3,
4
Example:

0

Response

Estimation successful

status
enum<string>

Response status: success/error

Available options:
success,
error
Example:

"success"

code
string

Response code, 000000 indicates success

Example:

"000000"

errorMessage
string

Error message, empty on success

Example:

""

data
object