Skip to main content
molnpay

Accept payments ยท POL

Accept Polygon payments.

Invoice in the currency you sell in, and let your customer pay in Polygon. We give the invoice its own address on the chain they choose, watch it, and send you a signed webhook when the payment is final. Polygon's native coin, on a chain with cheap stablecoin transfers.

POL on 1 chain.

Your customer picks one at checkout. You choose which of them you are willing to accept.

PolygonERC-20

Taking a Polygon payment.

  1. Create the invoice

    One POST with an amount, a pricing currency and your own reference. You get back a checkout URL, one payment address per chain, and a locked amount in every coin you accept.

  2. They pay, at a rate that stays honest

    Your customer is never asked to commit to a chain first โ€” one address serves every EVM chain, so whatever arrives is attributable. Stablecoins are quoted once. A volatile coin is re-quoted every two minutes, and the figure it replaces is still honoured for five, so nobody who did as they were told is told they underpaid.

  3. You get a signed webhook

    HMAC-SHA256, retried for about 46 hours, replayable from the dashboard. The payment is credited to your balance per asset.

POST /v1/invoices
curl https://api.molnpay.com/v1/invoices \
  -H "Authorization: Bearer $MOLNPAY_SECRET_KEY" \
  -H "Idempotency-Key: order_8812" \
  -d amount="49.90" \
  -d currency="USD" \
  -d reference_id="order_8812"

What you do not have to do.

  • Hold a POL wallet, or guard a seed phrase for one. No address here has a private key.
  • Keep gas on hand. We pay the network fee on every chain POL settles on.
  • Ask your customer to make an account. The hosted checkout needs nothing from them but a payment.
  • Watch every block yourself, or reconcile a reorg by hand.

Holding POL for your users instead?

Same API, same keys, same balance โ€” the difference is whether the address belongs to an invoice or to one of your users.

Polygon deposit addresses

Accept another asset