At 17:02 UTC on October 7, 2026, Polygon announced that TRON was live on Polygon Open Money Stack, or OMS. The accompanying product post says TRON carries more than $94 billion in circulating $USDT, representing over half of the stablecoin’s supply across all chains.
The integration gives businesses a single product flow for money entering through a bank transfer, card, cash or crypto and leaving through a bank account, card, cash pickup or wallet. Between those endpoints, OMS can create a TRON deposit address, hold $USDT in a custodial or embedded wallet, convert fiat, and route stablecoins to Polygon or other supported chains.
The release adds TRON support to an existing payments stack; no new bridge or stablecoin is announced. TRON remains the customer-facing chain, while Polygon OMS coordinates the wallet, conversion, routing and payout services beneath the application. Businesses can use the full stack or retain an existing wallet, compliance provider or ledger and connect only the OMS components they need.
Polygon frames those components as the difference between holding a stablecoin and operating a payment product. A business still needs a repeatable destination for each customer, a wallet model, deposit identification and reconciliation, routes to other assets or chains, and a path back to local currency. OMS puts those functions in one control layer. TRON can remain the network where the customer holds funds even when a payment begins or ends outside it.
How the TRON payment flow works
Polygon’s product announcement starts with pay-ins. A business can accept a bank transfer, card payment, cash or crypto and convert fiat into TRC-20 $USDT. Each customer receives a persistent TRON deposit address that can be reused. OMS attributes incoming $USDT to that customer and exposes the balance for the next step, removing the need to issue a fresh address for every payment or build a separate deposit-reconciliation system.
The wallet layer supports two custody models. Under the custodial option, a licensed custodian holds the keys, while identity checks, screening and transaction monitoring sit within the flow. Under the embedded option, the user controls the keys and signs in through the application’s normal authentication. Polygon says that path does not require a browser extension or seed-phrase prompt during onboarding.
That choice changes who controls the funds and where operational controls sit. The custodial model places key management and the listed screening controls with a licensed custodian. The embedded model leaves transaction signing with the user while hiding the usual extension and seed-phrase steps from onboarding. Payment teams still have to decide which model fits their product instead of inheriting one custody arrangement from the integration.
Routing uses Polygon Trails. The announcement says Trails can move $USDT and other supported assets between TRON and EVM chains in a single transaction. One example accepts $USDT from a TRON wallet and settles $USDC to an Ethereum user. Neither party has to interact with a bridge directly. The post also names Polygon, Base, Arbitrum, Avalanche and Optimism as possible destinations in its routing diagram.
The last step converts $USDT on TRON back into US dollars for delivery to a bank account, card or cash pickup location inside the business’s product. A company can therefore run a bank-to-wallet flow in one direction and a wallet-to-bank flow in the other without coordinating a different provider for each stage.
What changes for payment operators
The immediate benefit is operational. Polygon contrasts the OMS setup with a stack in which a business manages separate on-ramp, wallet, bridge and off-ramp vendors, each with its own contract, API and service-level agreement. OMS packages on-ramps, wallets, orchestration and off-ramps behind one integration. A team can still select individual parts instead of replacing its entire payments stack.
The intended users are fintechs, remittance services and payout products whose customers already hold or transfer $USDT on TRON. Polygon specifically points to the Philippines, Mexico, Argentina and Nigeria as markets where those users are active. Its examples include a remittance application that holds a sender’s $USDT and pays a recipient through a local bank, and a gig platform that gives workers a reusable TRON address for exchange withdrawals.
The $94 billion supply figure explains the choice of network. Polygon’s premise is that many intended customers already receive, hold and transfer $USDT on TRON. Requiring them to change chains before entering an application would add another user action. OMS instead lets a business accept the balance where it already sits, then select a destination asset, chain or fiat payout after the deposit has been attributed. That sequence is especially relevant to repeated remittance receipts and exchange withdrawals because the same deposit address can be reused.
For customers, the design keeps chain routing out of the payment interface. A user sees a balance, transfer or payout while OMS handles the route. The underlying bridge stays outside the user flow, including when a payment begins on TRON and settles as another supported asset on an EVM chain. For operators, the persistent address and automatic attribution cover deposit intake, while the two wallet models leave custody with either a licensed custodian or the user. Each business remains responsible for choosing the custody and compliance setup that fits its product.
TRON is the next chain supported by OMS, according to Polygon, and the company says it plans to extend the stack to more chains where money already moves. The open question is geographic availability. Polygon’s disclaimer says the described features and use cases may not be available in every jurisdiction and that users and institutions remain responsible for compliance with local law.
