/api/v1/p2p/merchant/wallet/withdraw-feeСтейджRead-only estimate of the withdrawal fee that will be applied to
the authenticated merchant BEFORE submission: a counterparty-specific
override if one is set, otherwise the tenant base — resolved through
the SAME policy resolver the payment path uses, so the estimate can
never diverge from the fee actually charged. The optional
amount_usdt_cents (USDT cents; note that the create request takes
whole units) also yields the net amount.
Authorization
MerchantToken MerchantSignature MerchantTimestamp The merchant's public token (64 hex characters), issued at onboarding.
In: header
HMAC-SHA256 signature (a single scheme for all endpoints).
Format: t=<unix_seconds>,v1=<hex_hmac_sha256>
where hex_hmac = HMAC-SHA256(webhook_secret, "<unix_seconds>.<raw_body>").
Replay window: 5 minutes (a 60-second drift into the future is allowed).
In: header
Unix time of the request in seconds. Signature window: 5 minutes back / 60 seconds forward.
In: header
Query Parameters
Optional gross withdrawal amount in USDT cents (> 0 enables net_amount_usdt_cents).
int64Response Body
application/json
application/problem+json
curl -X GET "https://example.com/api/v1/p2p/merchant/wallet/withdraw-fee?amount_usdt_cents=100000" \ -H "X-Merchant-Token: <MERCHANT_TOKEN>" \ -H "X-Timestamp: <UNIX_TIMESTAMP>" \ -H "X-Signature: t=<UNIX_TIMESTAMP>,v1=<HEX_HMAC_SHA256>"{ "base_fee_usdt_cents": "150", "override_applied": false, "total_fee_usdt_cents": "150", "net_amount_usdt_cents": "99850"}{ "type": "../dictionary", "title": "string", "status": 0, "detail": "string", "instance": "../dictionary", "errors": [ { "field": "amount", "message": "must be greater than 0", "code": "POSITIVE_REQUIRED" } ]}Issue (or rotate) the merchant TRC-20 deposit address POST POST
Generates (first call) or rotates (subsequent calls) the merchant's TRC-20 deposit address for incoming USDT collateral. The scope is resolved from the authenticated merchant context (the canonical path, without `merchant_id` in the path). Atomically takes the next BIP44 derivation index, derives the address via tron-wallet-api, and stores the address + index in the merchant record. Rotation semantics: the new address immediately replaces the old one in the merchant record, while every previously issued address forever remains in the platform's eternal block-polling set — USDT sent to a replaced address is still detected and credited. Legacy alias with administrative impersonation: `POST /api/v1/p2p/merchants/{merchant_id}/deposit-address`.
Incoming TRC-20 deposits with custody statuses GET GET
The merchant's incoming TRC-20 deposits: ledger credit plus the receiving address lifecycle from DepositSweepWorker (CREDITED / SWEEP_PENDING / SWEEP_FAILED / SWEEP_STUCK / SWEPT). Keyset pagination (AIP-158): page_size 1–100 (default 20), page_token/next_page_token.