Polymarket deposits: assets, networks and transfer status

A bridge guide or a working website does not establish eligibility for trading features. Check current geographic conditions and account state. A Russian-language interface does not establish deposit availability from Russia or remove any restrictions applying to the particular product.

If a feature is restricted, clarify permitted actions with official support. Closing an existing position, reading data and adding funds serve different purposes. Permission for one operation cannot be assumed to authorize another merely because the buttons or balances appear related.

USDC is a source asset, USDC.e its bridged version, and pUSD is Polymarket trading collateral on Polygon. The current deposit description says supported incoming USDC or USDC.e is converted to pUSD through the Collateral Onramp. These are distinct assets and steps rather than interchangeable destination instructions. Another network requires its own token and route-support check.

Record source network, exact asset, recipient and expected resulting balance when interpreting destination details. The network is part of the requirement. An identical address string in two interfaces does not automatically make all assets and transfer routes interchangeable or supported.

A network-and-token pair's minCheckoutUsd specifies its USD-equivalent minimum. The published table checked on October 11, 2026 gives examples of USD 7 for Ethereum, USD 2 for Polygon, and USD 9 for Bitcoin and Tron. This is a dated reference, not a live response for every asset; check the specific route's current minimum before an operation.

Documentation says deposits below the minimum are not processed. That is no promise of an automatic refund; unsupported tokens can cause loss.

A bridge quote estimates receipt and expenses. In a practice example, a sent value of 20 and estimated receipt of 19.70 differ by 0.30; that is arithmetic, not a Polymarket tariff. Compare complete estimates and units rather than one isolated percentage.

Sending, network confirmation, route processing and balance credit are separate stages when reading an operation. An outgoing transaction record cannot establish final receipt. Retain transaction identifier, network, time and status instead of repeatedly sending funds to test whether a delayed operation works.

For a delay, reconcile the original operation with the official status, then provide those records to support if needed. Never disclose a seed phrase or private key. OddsAtlas supplies no payment destination, receives no funds and promises no receipt time.