USDŦUSDŦUSD PAY AI
USDŦ · USD PAY AI

Developer Documentation

Technical reference for prospective integrators

Ethereum ERC-20 reference

Contract: 0x36Aa1e496B7EBEe2dBF854F0485D908F5764e2cC. Inspect source code, token name, symbol, decimals, transfer behavior and permissions in Etherscan before integration.

TRON TRC-20 reference

Contract: TEhXmFxTV1g7Ba56q9VLT78YKhQvrtxyd2. Explorer metadata previously showed UDST; do not assume it matches the Ethereum token.

Integration checklist

Verify chain ID, full contract address, on-chain metadata, token decimals, contract privileges, transfer confirmations and finality. Test with small amounts. Never rely on ticker text alone.

API status

No official USDŦ payment API, SDK, merchant plugin or cross-chain bridge is publicly offered by this website.

Integration checklist

Practical steps for engineers evaluating a future integration.

Network and token identity

Validate the chain ID, exact contract address, contract source, name(), symbol(), decimals() and totalSupply() against independent explorers or RPC calls. Do not assume the same metadata on Ethereum and TRON.

Transaction validation

Verify the receiving address, token contract, chain, transaction status, amount in base units and confirmation policy. Avoid trusting a transaction hash submitted by a user without independent verification.

Decimal-safe accounting

Store amounts as integers in smallest token units and convert for display using each contract’s verified decimals. Avoid floating-point rounding in payment logic.

Monitoring and support

Plan for chain congestion, reorg or confirmation anomalies, RPC outages, duplicate notifications and customer disputes.

Reference architecture

A conceptual implementation pattern, not a deployed USDŦ API.

Checkout service

A backend generates a short-lived quote, identifies the accepted network and recipient, and records an internal order ID. No private keys are requested from customers.

Blockchain watcher

An independently operated watcher checks relevant token transfer events and applies a documented confirmation threshold before order fulfillment.

Service fulfillment

After validation, the service grants access or triggers an automation task. Failed fulfillment should create an auditable support event.

Security boundary

A production integration needs secret management, least-privilege roles, audit logging, rate limits and incident response. These are recommendations, not claims of existing deployment.