docs
한국어

이 페이지는 아직 번역되지 않아 영어로 표시됩니다.

Currencies: USDT and USDC on Polygon

An install can accept USDT (always) and native USDC (when the operator configures it). Each token has its own PolysiaFactory, so deposit addresses, fee periods and sweeps are per token. Amounts are decimal strings with up to 6 decimals for both.

WhereFieldDefault
POST /v1/invoices"currency": "USDT" | "USDC"USDT
POST /v1/payment-links"currency" — every invoice created from the link uses itUSDT
POST /v1/addresses"currency" — one permanent address per customer and tokenUSDT
POST /v1/withdrawals"currency" — the token the Hot Wallet sendsUSDT
GET /v1/fees, /v1/fees/quote?currency=USDC — that token's 30-day fee periodUSDT

Responses carry "currency" and "token" (the token contract) on invoices, payments, addresses, payment links and withdrawals; webhooks the same. GET /v1/business lists every accepted token with its factory ("tokens"). An unknown or not-configured currency → 400 with param: "currency".

Payment page: shows the token badge and "Send only USDC on the Polygon PoS network — native USDC only, not the bridged USDC.e". A USDC transfer to a USDT address (or the other way round) is not a payment: the scanner logs it; the operator can recover it with the factory's rescueToken (it goes to the business Hot Wallet).

Fees: the same tier table applies separately per token (each factory has its own 30-day period volume).

Limits: withdrawal daily limits (business / customer / API key) are counted in dollars across both tokens.

Operator setup: USDC_ADDRESS + USDC_FACTORY_ADDRESS in .env (both or neither); the business must be created and its Hot Wallet accepted on the USDC factory too (Full mode: Polysia accepts it automatically once the operator proposed it there).