Skip to main content

Introduction to PayerScan

PayerScan allows Merchants to integrate cryptocurrency payments (USDT, BNB, ETH, etc.) into their websites or applications. Customers pay with crypto wallets or exchange accounts, and the system automatically verifies transactions and notifies the Merchant via API and Webhooks.

Key Features​

  • Create payment invoices via API with amount (USD), expiry, callback URL.
  • Checkout page displaying QR code, wallet address, and the exact crypto amount to transfer.
  • Multi-network — supporting multiple payment methods:
    • EVM Chains: BSC, Ethereum, Polygon, Base, Arbitrum, ...
    • Tron: TRC20 tokens
    • Solana: SPL tokens
    • Exchange Platforms: Binance Pay, OKX, Bybit, MEXC, Gate.io, Bitget, ... (no gas fees, instant confirmation)
  • Auto-confirmation when a matching transaction is detected (correct address, correct amount, within time window).
  • Webhooks to notify the Merchant server on successful payment or invoice expiry.
  • Status lookup API for invoices by trans_id.

Workflow​

  1. Create invoice — Merchant calls POST /payment/crypto with merchant_id, amount, callback_url, and receives trans_id + url_payment.
  2. Redirect customer — Merchant redirects the customer to url_payment (the checkout page).
  3. Customer pays — Customer selects token/network, then transfers the exact amount to the displayed wallet address (or pays via an exchange platform).
  4. Auto-confirm — System detects and verifies the transaction → updates the invoice to completed → sends a POST webhook to the Merchant's callback_url.
  5. Invoice expires — If the customer does not pay within the time window, the invoice status becomes expired and a webhook is also sent to callback_url.
  6. Check status — Merchant can call GET /invoice/:trans_id to check the current status at any time.

Integration Requirements​

  • API Key: Each Store has an API Key, sent via the x-api-key header in every request.
  • Payment method: At least one wallet address or exchange platform must be configured in your Store before creating invoices.
  • Callback URL: A public HTTPS URL where the Merchant server receives POST (webhook) events for completed/expired invoices.
  • HTTPS: The PayerScan API uses HTTPS exclusively. Callback URLs should also use HTTPS to ensure secure data transmission.

Next Steps​