Knowledge Base
  1. Home
  2. Knowledge Base
  3. Developer guides
Developer guides

Crypto payment API without KYC or API keys: overview

How the PayGate.to crypto payment API works: one HTTPS call per order, no account or API key, signed callbacks, hosted checkout, 80+ coins and official SDKs.

3 min readUpdated Intermediate
On this page
  1. The whole integration in three calls
  2. Key properties
  3. Rules that prevent most bugs
  4. Official SDKs
  5. For AI assistants and code generators
  6. Frequently asked questions

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

text
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

AuthenticationNone. No account, key or token exists; don't invent one.
Hosthttps://api.paygate.to (hosted pages on checkout.paygate.to), or your free dedicated endpoint
Coins80+ coins and tokens: BTC, ETH, USDT and USDC on many networks, SOL, XMR, XRP, LTC, DOGE, ZEC, TON and more (coin list)
PayoutsForwarded to your wallet after confirmation; no balance held
Fees1% plus blockchain fees (pricing)
CallbacksRSA-2048 signed (X-PayGate-Signature, X-PayGate-Key-Id); verify against your registered URL + raw query
MinimumsPer coin, from GET /crypto/info.php or /crypto/{ticker}/info.php

Rules that prevent most bugs

  1. Unique callback per order. Add at least one unique parameter (an order ID). Reusing a callback returns the same receiving address.
  2. Never use placeholder domains as callbacks in production; they can be refused.
  3. Pass returned values back exactly. address_in, payment_token and ipn_token come URL-encoded where needed; re-encoding breaks them.
  4. Verify every callback before trusting it: Verify PayGate.to callback signatures.
  5. Credit each txid_in once. Callbacks repeat until you answer ok.
  6. Check coin and amount. Any token can be sent to an address; compare what arrived with what you expected.
  7. Respect minimums. Smaller payments can't be forwarded.

Official SDKs

LanguagePackageGuide
PHP 7.4+paygate-to/paygate-phpAccept crypto payments in PHP · SDK docs
Node.js 18+paygate-toAccept crypto payments in Node.js · SDK docs
Laravel 10 to 13paygate-to/paygate-laravelAccept 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.

This guide is also available as Markdown for AI assistants and offline reading.