POL is the native gas and staking token associated with Polygon’s current network documentation, replacing the earlier MATIC naming. Coinvay’s Polygon route uses native POL for coin payments and recognizes only its separately configured token contracts for stablecoin payments.
Use the current asset and network labels
Coinvay’s Polygon configuration uses chain ID 137 and a native POL asset. An older wallet or exchange screen may still show legacy naming, so the payer should confirm the actual network and asset before sending. A familiar address shape alone cannot resolve the ambiguity.
For example, a merchant collecting a deposit in POL should generate a fresh checkout quote. The buyer follows the quoted POL amount and recipient address. Sending a token called POL on Ethereum is not automatically a native Polygon payment, even if the same business controls the address on both chains.
Keep payment and gas requirements distinct
A customer paying USDC or PYUSD on Polygon may need POL for the transaction fee, but their invoice is still requesting the stablecoin transfer. Conversely, a native POL invoice must receive POL itself. Explain both the requested asset and the network’s fee asset.
Avoid fixed promises about transaction costs. A wallet’s current estimate is more useful than a permanent low-fee claim. Check that using a withdrawal platform or Send Max option does not change the exact amount arriving at the merchant.
Apply the configured confirmation policy
Coinvay currently requires 128 confirmations on its Polygon route and validates chain identity, successful receipt, recipient, quantity and quote timing. This threshold is a product setting, not a statement that all types of finality or bridge withdrawals are completed at the same moment.
Once received, POL remains in the merchant wallet until the merchant authorizes another transaction. A gateway receipt does not perform a MATIC migration, token swap or bank conversion. Those are separate operations that should not be hidden inside checkout instructions.
Practical checklist
- Use Polygon mainnet chain ID 137 for this route.
- Distinguish native POL from tokens on other networks.
- Review gas requirements and the exact recipient amount.
Common questions
Can an old MATIC-labeled balance pay a POL invoice?+
Check the wallet’s actual chain and asset handling using current Polygon guidance. A display label is insufficient; only the expected native transfer can complete the quoted Coinvay payment.
Does enabling POL enable USDC automatically?+
No. Accepted coins and token contracts must be configured separately. Merchant-facing network support does not imply unrestricted acceptance of every asset on that blockchain.
Sources and further reading
Primary references and Coinvay product documentation. Check the linked pages for current details.
AI-assisted drafting, published by Coinvay. Examples are illustrative. Read our editorial approach.