Polygon
No exact public BUY row
Observed sandbox default: Polygon
Explore MATIC receiving details →Understand Polygon’s MATIC-to-POL distinction, the difference between Ethereum and Polygon PoS holdings, and what the Banxa selector does not prove.

Polygon’s official support documentation distinguishes MATIC held on Ethereum from the native asset on Polygon PoS. It describes automatic conversion on Polygon PoS, while Ethereum-held MATIC follows a separate migration process. A wallet can also retain an older display symbol after the network change.
This does not mean every provider has adopted the same labels. Banxa’s sandbox contains separate MATIC and POL selections. Our captured public BUY table has exact POL rows but no exact MATIC asset row. We preserve that discrepancy rather than merging the two entries or inventing production support.
READ THE EXACT RECEIVING ASSET
No exact public BUY row
Observed sandbox default: Polygon
Explore MATIC receiving details →2 documented BUY routes
Ethereum mainnet · Polygon
Explore POL receiving details →Provider-level documentation checked November 17, 2026. Route counts do not measure asset quality or prove customer eligibility. Banxa checkout here is upcoming.
Ask the receiving service which asset code and network its current deposit screen accepts. A Polygon project name, a MATIC network code or a legacy wallet symbol is not sufficient by itself. Do not send an asset to a different route in the hope it will automatically migrate.
POL documented routes · MATIC sandbox evidence. Direct Banxa checkout here is upcoming. This page does not connect to a wallet, request an approval or execute a migration.
Checked November 17, 2026: Polygon’s migration support article and Banxa BUY documentation. Consult current official instructions for your network and custody arrangement. Editorial responsibility: Abiola Babatunde. Report a correction.
Explore your purchase options and find guidance for the questions along the way.