At a glance
Polygon on Paymos
Supported assets
- USDT Tether USD
- USDC USD Coin
Confirmation speed
A payment is confirmed once the network itself declares the block final — no confirmations to count.
Paymos enables merchants to accept USDT and USDC payments on Polygon. Each invoice receives a dedicated address, Paymos monitors the transfer and required confirmations, and the merchant receives the same stablecoin the customer sent—with no forced conversion and no markup hidden in the rate.
Supported payment assets on Polygon
Paymos accepts two assets on Polygon:
- USDT;
- USDC.
POL, formerly associated with the MATIC name, is not an invoice payment asset in Paymos. The sending wallet may require the network's native asset for gas, but that cost is separate from the stablecoin invoice.
A Polygon invoice must be paid on Polygon. USDT or USDC sent through Ethereum, BSC, Base, or another network is a different transfer even when the ticker is identical. The customer should copy both the asset and network shown at checkout.
How a Polygon payment works
- The merchant creates an invoice through checkout, a Payment Link, POS, a CMS plugin, the Low-Code SDK, or the REST API.
- The customer selects a supported stablecoin on Polygon.
- Paymos assigns a dedicated deterministic address to the invoice.
- The customer sends the displayed amount on the specified network.
- Paymos detects the transfer and waits for the required confirmations.
- The payment status changes and the same asset is credited to the merchant balance.
API integrations can receive HMAC-SHA256-signed webhooks for status changes. The merchant can connect the invoice to an order and fulfill it only when Paymos reports the appropriate final status.
Polygon confirms at network finality
There is no single guaranteed confirmation time for every Polygon payment. Polygon reaches network finality in roughly thirty seconds, so a payment is confirmed at that finality rather than at a depth that changes with the amount.
Do not treat a submitted wallet transaction as a completed order. Network conditions and wallet behavior decide when that finality arrives. The Paymos invoice status is the integration's source of truth.
Polygon gas and Paymos fees
The payer's wallet pays the Polygon network fee in POL. That fee belongs to the network and moves with demand for block space, so Paymos quotes no fixed transfer price. A wallet holding nothing but USDT or USDC cannot send it: POL has to be there first.
Paymos covers the network cost of accepting and consolidating the payment. Standard pricing is 1.0% per settled invoice, and Enterprise pricing is 0.3% on request. There are no setup or monthly fees, minimum volume, reserve, rolling reserve, or charge for an unpaid, expired, or cancelled invoice.
Settlement stays in USDT or USDC
USDT is credited as USDT and USDC as USDC. Paymos does not insert an automatic conversion into the payment path or conceal a processing charge in an exchange rate.
Balances are maintained per asset, not per chain. The same supported asset received over different networks contributes to that asset balance. For payout, the merchant selects an available network and a whitelisted destination.
Paymos adds no processing commission to withdrawals. Where the payout network carries a fee, you see the amount first, and it is smaller than the chain's own charge for that transfer.
When to offer Polygon
Offer Polygon when customers already hold supported stablecoins on that network and can pay its gas. It can sit beside Ethereum and other supported networks in the same Paymos checkout, giving the payer a choice without requiring separate merchant integrations.
Do not select Polygon for a customer solely from a generic fee or speed ranking. The best option is one the customer can actually send on: the correct stablecoin must be available on the correct network, with enough native asset for gas.
Integration and security controls
Hosted Checkout, Embedded Checkout, Payment Links and the Low-Code SDK handle customer-facing payment instructions. H2H API, POS and official CMS plugins support different merchant workflows while using the same invoice model.
Outgoing transactions are signed on isolated infrastructure. Withdrawal whitelisting separately restricts payout destinations.
Frequently asked questions
Which stablecoins can Paymos accept on Polygon?
Paymos supports USDT and USDC on Polygon.
Can a customer send USDC from Base to a Polygon invoice?
No. Base and Polygon are different networks. The customer must send USDC on the network specified by the invoice.
Who pays Polygon gas?
The payer's wallet pays the network fee for sending the stablecoin. The fee goes to the Polygon network, not to Paymos.
Does Paymos guarantee a fixed Polygon fee or confirmation time?
No. Network fees vary; the confirmation requirement does not, because Polygon confirms at network finality.
Is the payment converted after receipt?
No. USDT remains USDT and USDC remains USDC in merchant settlement.
How can I add Polygon to checkout?
Enable the supported Polygon assets in your Paymos integration. For a broader choice, compare the supported stablecoin networks and read how crypto gas fees work.