Accept Polygon payments
Activity on Polygon is paid for in POL, the token many buyers still know as MATIC, its name before the migration. The property that matters to a merchant is cost: Polygon is an EVM chain where sending a payment costs the buyer almost nothing. POL is what cost-sensitive customers reach for when mainnet feels expensive.
How POL settles here
Each payment gets its own forwarding address whose destination is fixed to your treasury when the address is created, and where the setup allows it the payment settles into your treasury directly. NoHoldPay's job is narrow: watch the chain, match the transfer to your invoice, and sign the webhook that tells your store it confirmed. Custody never enters the picture.
| Network | Confirmation rule (live) | Typical time |
|---|---|---|
| Polygon | Payments confirm when the network finalizes the block that contains them. | varies |
Why merchants take Polygon
Accepting POL is a bet on volume rather than ticket size, and it is a sensible one. Polygon built its user base on the promise that trying things is cheap, so its wallets belong to people who transact often: game item buyers, NFT collectors, remittance-minded users in markets where fees decide everything. Those customers already keep POL for gas, which means an invoice in POL asks them for nothing they do not have. Each order gets a fresh payment address that routes to a wallet only you control, and if you run a storefront, the WooCommerce and OpenCart plugins drop this option into your existing store with nothing custom to build.
Worth knowing
Expect the old name to linger. Wallet labels, price trackers, and customer vocabulary caught up to the POL ticker at different speeds, so write your checkout copy with both names for now and nobody gets confused. The coin also lives a double life as Polygon's staking asset, which means part of many holders' POL sits locked with validators. What pays your invoice is the liquid balance in the buyer's wallet, and seasoned Polygon users keep some on hand because every action on the network needs it.
The platform fee is 0.5% per confirmed payment, prepaid. New accounts start with $50 of live credit, covering roughly the first $10,000 processed. Checkout ships hosted, or through the WooCommerce and OpenCart plugins.
Common questions
- My customer's exchange still shows MATIC. Can they pay a POL invoice?
- Almost certainly yes. The migration converted MATIC into POL at the network level, and balances labeled with the old ticker on lagging exchange screens are the same asset underneath. The customer withdraws on the network the invoice names, and the payment matches like any other POL transfer.
- Will buyers who know Ethereum find POL payments familiar?
- Completely. Polygon is EVM-based, so the wallets, address formats, and signing prompts match what an Ethereum user already knows. What changes is cost and tempo: the fee is negligible and confirmation comes quickly, so buyers send with less of the hesitation mainnet trains into people.
- A customer holds POL on Ethereum itself. Can they pay with it?
- Not directly. The invoice watches the network shown in the checkout, and tokens on a different network never arrive there. A holder with POL on Ethereum needs to bridge or trade it onto the invoice's network first, so it is kinder to steer such customers before they send anything.
Take your first POL payment
Add a wallet, create a payment, and watch it confirm on a testnet before going live.
Accept Polygon