Polysia

Hosted payment page

pay_url (https://<your domain>/pay/pt_…) is a ready-made page for the customer. Send them there (redirect or link), or build your own page from address + amount of the invoice.

အကျဉ်းချုပ် (မြန်မာ): စာမျက်နှာက ပမာဏနဲ့ လိပ်စာကို စာသား + Copy button နဲ့ ပြပါတယ် (QR ကို wallet တိုင်း နားမလည်လို့)။ English / မြန်မာ (?lang=my) ရပြီး မြန်မာစာက Unicode + ဖုန်း/ကွန်ပျူတာရဲ့ system font ကိုပဲ သုံးပါတယ် (web font မသုံး)။ Order id, metadata, invoice id တို့ကို customer မမြင်ရပါ။

What the customer sees

Privacy and security

Languages

English and Myanmar. ?lang=my / ?lang=en, otherwise the browser's first Accept-Language; a switch is on the page. Myanmar text is Unicode (not Zawgyi) and uses the system font (Android: Noto Sans Myanmar, Windows: Myanmar Text, iOS/macOS: Myanmar Sangam MN). Phones with only a Zawgyi font show broken text — that is a phone setting, not something the page can fix.

QR codes

Wallets differ in what they read from a QR, so the amount and address are always shown as text too.

QRcontentnotes
Address only (default)0x…every wallet; the customer chooses USDT on Polygon and types the amount
With amount (link "QR with amount (MetaMask only)", ?qr=eip681)EIP-681 ethereum:<USDT>@137/transfer?address=…&uint256=…fills token + amount in wallets that support it; only while nothing has been paid (a partial payment needs a different amount)

Test the QR with the wallets your customers use before launch. In our tests MetaMask mobile filled token and amount from the amount QR; SafePal understood only the address QR.

GET /pay/{token}/status (public, used by the page)

{"state":"partial","final":false,"amount":"25.00","received":"10.00","received_raw":"10000000",
 "remaining":"15.00","expires_at":"2026-11-18T12:30:00Z","seconds_left":1234}

state: waiting, partial, confirming, closing (expiry passed, final check running), paid, overpaid, underpaid, expired, cancelled. Your server should use the API / webhooks instead.