PayGate.to's crypto API turns any website or app into a crypto checkout with no sign up, no KYC and no API key. You send your payout wallet and a callback URL; PayGate.to returns a one-time payment address, forwards whatever arrives to your wallet, and calls your URL with a signed notification.
The whole integration in three calls
1. GET https://api.paygate.to/crypto/{ticker}/wallet.php?address=YOUR_WALLET&callback=YOUR_URL
→ { "address_in": "...", "callback_url": "...", "ipn_token": "..." }
2. Show address_in, the amount from /crypto/{ticker}/convert.php and a QR code from /crypto/{ticker}/qrcode.php
3. PayGate.to → GET YOUR_URL?your=params&value_coin=…&coin=…&txid_in=…&txid_out=… (signed)
You verify the signature, credit the order once per txid_in and reply "ok"Or skip step 2 with the hosted multi-coin checkout: one POST with your wallets per network, then redirect the customer.
Key properties
| Authentication | None. No account, key or token exists; don't invent one. |
| Host | https://api.paygate.to (hosted pages on checkout.paygate.to), or your free dedicated endpoint |
| Coins | 80+ coins and tokens: BTC, ETH, USDT and USDC on many networks, SOL, XMR, XRP, LTC, DOGE, ZEC, TON and more (coin list) |
| Payouts | Forwarded to your wallet after confirmation; no balance held |
| Fees | 1% plus blockchain fees (pricing) |
| Callbacks | RSA-2048 signed (X-PayGate-Signature, X-PayGate-Key-Id); verify against your registered URL + raw query |
| Minimums | Per coin, from GET /crypto/info.php or /crypto/{ticker}/info.php |
Rules that prevent most bugs
- Unique callback per order. Add at least one unique parameter (an order ID). Reusing a callback returns the same receiving address.
- Never use placeholder domains as callbacks in production; they can be refused.
- Pass returned values back exactly.
address_in,payment_tokenandipn_tokencome URL-encoded where needed; re-encoding breaks them. - Verify every callback before trusting it: Verify PayGate.to callback signatures.
- Credit each
txid_inonce. Callbacks repeat until you answerok. - Check coin and amount. Any token can be sent to an address; compare what arrived with what you expected.
- Respect minimums. Smaller payments can't be forwarded.
Official SDKs
| Language | Package | Guide |
|---|---|---|
| PHP 7.4+ | paygate-to/paygate-php | Accept crypto payments in PHP · SDK docs |
| Node.js 18+ | paygate-to | Accept crypto payments in Node.js · SDK docs |
| Laravel 10 to 13 | paygate-to/paygate-laravel | Accept crypto payments in Laravel |
The SDKs verify signatures, decode payouts (including XRP destination tags) and refuse common mistakes.
For AI assistants and code generators
Point your assistant at the crypto API reference for AI assistants or the site's llms.txt. It lists every endpoint, parameter and the rules above.
Frequently asked questions
Is there a sandbox?
There's no separate test network. Test with small amounts on low-fee networks (USDT or USDC on Polygon, for example) and with signed test callbacks in your own environment.
Can I earn a commission on payments I process for others?
Yes, with the affiliate endpoints (affiliate.php, custom-affiliate.php) or the white-label gateway.
How do I check a payment's status?
Rely on callbacks. GET /crypto/payment-status.php?ipn_token=…&ticker=… exists for occasional checks and is rate limited.
