TRON USDT checkout with clear payer-side energy and fee boundaries.
TRON USDT полезен для продавцов, чьи клиенты уже владеют USDT на TRON. Ключевой операционной деталью является прозрачность затрат на энергию/пропускную способность до того, как будет предпринята попытка оплаты.
TRON USDT checkout creates a payment session for the TRON rail, shows the merchant receiving setup, and lets the customer pay USDT from a compatible TRON wallet. TRON energy and bandwidth costs belong to the transaction signer or wallet flow.
Merchant enables a TRON USDT rail-wallet route.
XPayr creates a TRON USDT payment session and customer reference.
Customer pays from a compatible TRON wallet with enough TRX or energy.
XPayr records transaction hash, status, amount, and reconciliation fields.
Who pays gas?
TRON USDT transfers require TRX or energy/bandwidth from the payer side unless a separate sponsored model is explicitly configured.
Operational limit
Wrong-network USDT transfers are not equivalent. TRON USDT should be shown as TRC20 and kept separate from EVM or Solana stablecoin routes.
FAQ
What problem does this XPayr flow solve?
TRON USDT checkout creates a payment session for the TRON rail, shows the merchant receiving setup, and lets the customer pay USDT from a compatible TRON wallet. TRON energy and bandwidth costs belong to the transaction signer or wallet flow.
Who pays gas or network fees?
TRON USDT transfers require TRX or energy/bandwidth from the payer side unless a separate sponsored model is explicitly configured.
What should merchants not assume?
Wrong-network USDT transfers are not equivalent. TRON USDT should be shown as TRC20 and kept separate from EVM or Solana stablecoin routes.
Publicly auditable SDKs, cryptographic evidence envelopes, and MCP registries.
Официальный MCP-сервер с 21 инструментом
Registered as io.github.xpayrcom/xpayr-mcp-server on the Official Anthropic MCP Registry and published as @xpayr/mcp-server on NPM and ghcr.io/xpayrcom/xpayr-mcp-server:latest.
Merkle Payment Evidence & ES256 Tokens
Verify on-chain settlement envelopes with @xpayr/payment-evidence and offline-verifiable ES256 wallet licenses with @xpayr/extension-kit.
30 Open-Source Repositories & RFC 9116
Inspect all 20 REST API v1 schemas interactively at api-docs.xpayr.com, review our 30 repositories at github.com/xpayrcom, and check /.well-known/security.txt & /.well-known/jwks.json.
Необходимо доказать поток перед началом производства?
Используйте проверку тестовой сети, документацию по API, руководства по веб-перехватчикам и пояснения по работе, прежде чем запрашивать активацию основной сети.