docs
On this page

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.

What the customer sees

  • Your business name (dashboard → API → Invoice settings → Name on the payment page, else the business name), the invoice description.
  • Amount and address as text, each with a Copy button, the network warning ("send only USDT on Polygon PoS"), a countdown to expires_at, and a QR code.
  • Live status: Waiting for your payment → Received X of Y — send Z more to the same address (partial) → Payment received — confirming → Paid ✓ (then back to your redirect_url after 5 s, or a "Return to the merchant" button). Expired / cancelled / underpaid pages and the time after expiry hide the address ("do not send funds").
  • The page polls its own status every 5 s (every 15 s after 10 minutes) and reloads when something changes; without JavaScript it refreshes every 15 s and the copy buttons are hidden (the text can still be selected).

Privacy and security

  • The token in /pay/pt_… is 128 random bits, separate from the invoice id: it reveals neither the invoice nor the business. Anyone with the link can see that page, so treat it like the invoice itself (don't post it publicly).
  • The page and GET /pay/{token}/status show only: business display name, description, amount, address, network, expiry, state and received total. Never order_id, metadata, ids, payer addresses or keys.
  • Strict Content-Security-Policy (own scripts / styles / images only, no third-party requests, no web fonts); no cookies are read or set.
  • Embedding (iframe) is refused by default (frame-ancestors 'none'). To embed it in your shop, list your https origins in dashboard → API → Invoice settings → Allow embedding the payment page in (max 5).

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.