Introduction to PolyPay

PolyPay is a modern cryptocurrency payment gateway that helps merchants easily accept USDT, USDC, and other digital currency payments.

Why Choose PolyPay?

🔗 Multi-Chain and Multi-Currency

Support for Ethereum, Tron, Solana, Polygon, BSC, Base, Arbitrum One, Optimism, and TON. Available currencies vary by network; for example, Base supports bridged USDT, USDC, and ETH, while TON supports USDT and Gram (GRAM). Base USDT uses the canonical Base bridge contract, so integrations must use the exact contract shown by PolyPay.

Gram (GRAM) is the native coin of the TON network. Use network=TON and currency=GRAM in API requests. Orders, wallet settings, and webhook currency values use GRAM; TON is no longer accepted as a currency code.

⚡ Real-Time Settlement

PolyPay detects transfers and updates the order after the required blockchain confirmation. In non-custodial mode, the transfer goes directly to the merchant receiving wallet.

🔒 Secure and Reliable

Non-custodial mode - funds go directly to your wallet
Industry-standard API signature verification
Comprehensive callback notification system

Wallet Receiving Preferences

When adding or editing a wallet, the selected network must match the address format; for example, a Tron address cannot be saved as an Ethereum wallet. Validation accepts network names and common aliases.

Exchange and custodial addresses are not supported because their unrelated transaction volume interferes with payment monitoring. If an address is blocked after review, Wallet Management shows the review summary in the current dashboard language and provides an appeal or support option.

In Wallet Management, merchants can configure how new orders select a receiving wallet from enabled compatible wallets: off keeps the default wallet priority, balanced receiving prefers wallets with fewer historical orders for the same network and currency, and random wallet selects a compatible wallet randomly for each order.

On the dashboard Orders page, the More menu keeps order details and less-common actions together. A wait-pay order can be updated with a new USD amount, currency, and network; PolyPay recalculates the payable amount and safely replaces its receiving-address payment slot while preserving the trade ID and payment link. An unpaid order can also be expired manually after confirmation; any reserved payment slot is released as part of the normal expiration flow.

The dashboard Transaction Records page reads directly from the block-chain service to show income and expense activity for added wallet addresses, with filters for transaction hash, address, network, and direction. An unposted incoming transfer can be linked to a pending or expired order. Before confirmation, the dialog lists and marks every check, including order status, direction, receiving address, network, currency, transaction time, transaction and order availability, and amount. A failed required check blocks confirmation; an amount mismatch is shown as a warning and remains linkable. Once confirmed on-chain, linking marks the order as paid and sends its payment-success Webhook.

Multi-Merchant Management

One account can manage multiple merchants. The top-left dashboard shows the PolyPay brand and a merchant switcher; click the current merchant to change or add a merchant. Orders, wallets, API keys, webhooks, plugins, and developer settings are scoped to the selected merchant. After a switch, dashboard requests carry the selected merchant ID, and the backend verifies that it belongs to the signed-in account. Merchant selection is stored independently per browser tab, so different tabs can manage different merchants while displayed context and request data remain consistent. The account balance can pay for subscriptions and metered usage for any merchant under the account. The current merchant can be archived from the bottom of Merchant Management. Archiving preserves historical orders and subscriptions and does not affect the account balance or withdrawals. It hides the merchant from the regular switcher, stops its business features, and disables subscription auto-renewal. Archived merchants can be viewed and restored in Account Settings; auto-renewal can be enabled again manually after restoration.

🛠 Easy Integration

Use the REST API, JavaScript or PHP SDK, hosted checkout, and supported plugins such as WHMCS.

Getting Started

Register Account — Sign up for a merchant account on PolyPay
Get API Keys — Generate API Key in the merchant dashboard
Integration Testing — Follow the API Key and Hosted Checkout guides
Go Live — Start accepting payments after integration

Key Guides

Payment subscriptions, order quotas, and receiving-wallet usage belong to each merchant. Wallet-monitoring plans, monitored addresses, and notification allowances belong to the account; switching merchants does not create another monitoring allowance.