easyway
Log inGet started

Crypto payment integration guides

Task-by-task walkthroughs for adding easyway to your site or app. Each one uses the same REST API and webhooks as the API reference, with code you can copy.

  1. Step 1

    Test crypto payments in sandbox mode

    Test keys, simulated full, partial, over- and late payments, test webhooks, and what to set up before going live — the whole flow without real funds.

    • How the sandbox works
    • Simulate payments
    • Before you switch to live
    • What the sandbox cannot show you
  2. Step 2

    Accept USDT TRC-20 payments in Node.js, PHP or Python

    Create an invoice limited to USDT on Tron, send the customer to the payment page, fulfil the order on the webhook and go live.

    • Create an invoice
    • Redirect to the payment page
    • Fulfil on the webhook
    • Go live
  3. Step 3

    Handle underpaid and late crypto payments

    What happens when a customer sends too little, too much or too late: statuses, webhooks, tolerance and a handler that covers every case.

    • The rules in one table
    • Underpayment tolerance
    • Late payments
    • A handler that covers every case
  4. Step 4

    Verify crypto payment webhook signatures

    Check the HMAC-SHA256 signature on every webhook in Node.js, Next.js, PHP and Python, test it locally with openssl and curl.

    • What is signed
    • Code you can copy
    • Common mistakes
    • Retries and timeouts
  5. Step 5

    Crypto donation alerts in OBS: step-by-step setup

    A donation link, its alert widget in OBS Studio or Streamlabs, a test without real funds and a thank-you bot on the webhook.

    • Create the donation link
    • Add the widget to OBS
    • Test without real funds
    • Thank supporters by webhook

Which one first?

Start in the sandbox: with a sk_test_ key nothing touches a real chain, and you can make an invoice paid, underpaid or late on purpose to see every webhook your code has to handle. Then build the real flow with the USDT TRC-20 guide — the same code works for any other coin by changing allowed_assets, or by leaving it out so the customer picks. Add signature checks before you go live, so nobody can fake a "paid" webhook.

Taking donations on a stream? The OBS donation alerts guide needs no code at all; only its optional thank-you bot uses a webhook.

Reference

Every endpoint, field and error code is in the API docs, and the machine-readable spec is at /openapi.json. Minimum invoice amounts and confirmations for each coin are on the pricing page.

Create free accountRead the API docsAlready have an account? Sign in
Crypto payment integration guides | easyway