easyway API

Accept crypto payments in a few lines of code. One REST API, JSON in and out, and signed webhooks that tell your server when the money has arrived.

Machine-readable spec: /openapi.json (OpenAPI 3.1) — import it into Postman, Insomnia or a client generator.

Overview

A payment on easyway is an invoice. You create one from your server with the amount your customer owes, redirect them to its payment_url, and easyway does the rest: the customer picks a coin and network, gets a one-off address (or a shared address plus a memo on TON and XRP), and the on-chain watchers credit the payment the moment it is final. Your server learns about it from a webhook — never by trusting the browser.

Amounts are always decimal strings ("149.00", never 149) so nothing is lost to floating point. Ids are prefixed and unguessable: inv_… invoices, po_… payouts, evt_… webhook events. Timestamps are ISO-8601 in UTC.

Store plugins (no code)

Run a shop or a billing system? Download the plugin for your platform, upload it, paste your API key and webhook secret from the dashboard, and "Pay with crypto" appears at checkout. Orders are marked paid by the signed webhook. Install steps for each one are on the plugins page.

Authentication

Create keys in Dashboard → Developers. A key is shown once. Send it as a bearer token:

Authorization: Bearer sk_live_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
# (X-Api-Key: sk_live_… is accepted too)

Quickstart

Three steps: create an invoice, send the customer to it, act on the webhook. A full walk-through for one coin, with sandbox testing and a go-live checklist: accept USDT TRC-20 payments.

1. Create an invoice

curl -X POST https://api.easyway.cash/v1/invoices \
  -H "Authorization: Bearer $EASYWAY_API_KEY" \
  -H "Idempotency-Key: order-2048" \
  -H "Content-Type: application/json" \
  -d '{"amount":"149.00","currency":"USD","order_id":"2048","description":"Order #2048","customer_email":"jane@example.com","success_url":"https://shop.example.com/thanks","cancel_url":"https://shop.example.com/cart","metadata":{"cart":"c_81f2"}}'

Response 201:

{
  "id": "inv_7Q2mN4kL8pR1sT9uV3wX0y",
  "status": "pending",
  "mode": "live",
  "order_id": "2048",
  "description": "Order #2048",
  "amount": "149",            // trailing zeros dropped
  "currency": "USD",
  "pay_asset": null,          // filled once the customer picks a coin
  "pay_amount": null,
  "pay_address": null,
  "pay_memo": null,
  "pay_network": null,
  "rate": null,
  "received_amount": "0",
  "remaining_amount": "0",
  "fee_amount": "0",
  "net_amount": "0",
  "customer_email": "jane@example.com",
  "metadata": { "cart": "c_81f2" },
  "payment_url": "https://easyway.cash/pay/inv_7Q2mN4kL8pR1sT9uV3wX0y",
  "expires_at": "2026-09-23T13:15:00.000Z",
  "paid_at": null,
  "created_at": "2026-09-23T12:15:00.000Z"
}

2. Send the customer to the payment page

// Server-side redirect (Express)
res.redirect(303, invoice.payment_url);

// …or a button in your own page
<a href={invoice.payment_url}>Pay with crypto</a>

After paying, the customer is offered a button back to your success_url. Don't treat that visit as proof of payment — the webhook is.

3. Fulfil on the webhook

# Webhooks are pushed to YOUR server — there is nothing to curl.
# The header looks like this:
#   X-Webhook-Signature: t=1758470400,v1=5f1c…e2a9
# expected = HMAC_SHA256(secret, "<t>.<raw request body>")
# Compare v1 with expected in constant time, and reject if |now − t| > 300 s.

Invoices

Create an invoice

Pricing in a coin instead of USD:

curl -X POST https://api.easyway.cash/v1/invoices \
  -H "Authorization: Bearer $EASYWAY_API_KEY" \
  -H "Idempotency-Key: topup-7731" \
  -H "Content-Type: application/json" \
  -d '{"amount":"25","currency":"USDT_TRC20","order_id":"topup-7731","lifetime":30}'

The invoice object

Lifecycle

Retrieve an invoice

curl https://api.easyway.cash/v1/invoices/inv_7Q2mN4kL8pR1sT9uV3wX0y \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

List invoices

curl https://api.easyway.cash/v1/invoices?page=1&pageSize=50&order_id=2048 \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

{ "data": [ { …invoice… } ], "total": 1, "page": 1, "page_size": 50 }

Cancel an invoice

curl -X POST https://api.easyway.cash/v1/invoices/inv_7Q2mN4kL8pR1sT9uV3wX0y/cancel \
  -H "Authorization: Bearer $EASYWAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Once a payment has been detected the invoice can't be cancelled (409 invoice_not_pending).

Coins & networks

Every (coin, network) pair has its own id — USDT on TRON and USDT on Ethereum are different balances, because they are different things to withdraw. Use these ids in currency, allowed_assets, pay_asset and payouts.

Minimum payouts are about half a dollar on every network. “Confirmations” is how many blocks a payment must be buried under before it is credited: seconds on Solana, TON, XRP and Avalanche; about a minute on TRON and BSC; a few minutes on Ethereum, Polygon, Litecoin, Dogecoin and Dash; ~20 minutes on Bitcoin. On TON and XRP all payments arrive at one address and are told apart by the memo / destination tag in pay_memo.

Webhooks

Running several projects? Give each API key its own webhook (Dashboard → Developers → API keys → Create / Edit): events of invoices created with that key go to that URL only, signed with that endpoint's own secret. Everything else — payouts, invoices made in the dashboard or with payment links, and keys without a webhook of their own — goes to the account webhooks (Developers → Account webhooks). Billing a SaaS? The crypto payments for SaaS guide shows a renewal flow built on these events. Either way, pick the events and copy the signing secret. easyway POSTs a JSON body to it:

{
  "id": "evt_5Gz2Kq8Lm1Np4Rs7Tv0Wx3",
  "type": "invoice.paid",
  "mode": "live",
  "created": 1758630900,
  "data": {
    "invoice": { …the invoice object, exactly as GET /v1/invoices/:id returns it… }
  }
}

Verify the signature

Every delivery carries X-Webhook-Signature: t=<unix seconds>,v1=<hex> where v1 = HMAC-SHA256(secret, t + "." + raw_body). Recompute it over the raw request body, compare in constant time, and reject anything older than five minutes. Without this check anyone who finds your URL can mark their own orders as paid. Step-by-step guide with a Next.js handler, a local test and common mistakes: verify webhook signatures.

# Webhooks are pushed to YOUR server — there is nothing to curl.
# The header looks like this:
#   X-Webhook-Signature: t=1758470400,v1=5f1c…e2a9
# expected = HMAC_SHA256(secret, "<t>.<raw request body>")
# Compare v1 with expected in constant time, and reject if |now − t| > 300 s.

Delivery rules

Balances, rates & assets

curl https://api.easyway.cash/v1/balances \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

{ "data": [
  { "asset": "USDT_TRC20", "available": "1240.55", "locked": "500" },
  { "asset": "BTC",        "available": "0.0312",  "locked": "0" }
] }

available is what you can withdraw now; locked is reserved by payouts that are still in flight.

curl https://api.easyway.cash/v1/rates \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

{ "data": { "USDT_TRC20": "1", "BTC": "67412.18000000", "ETH": "3188.40000000", "TRX": "0.34319100", … } }

USD per unit, the median of several exchanges, refreshed every minute. Stablecoins are pinned to 1. These are indicative — an invoice locks its own rate at the moment the customer picks a coin.

curl https://api.easyway.cash/v1/assets \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

{ "fee_bps": 50,
  "data": [
    { "id": "USDT_TRC20", "symbol": "USDT", "name": "Tether", "network": "TRON", "network_label": "TRON · TRC-20",
      "memo_required": false, "decimals": 6, "confirmations": 19, "payout_fee": "1", "min_payout": "0.5" },
    …
  ] }

The coins you can use right now for new invoices and payouts — the same list as Coins & networks, straight from the server, so your integration never offers a coin that isn't enabled. fee_bps is your processing fee in basis points (50 = 0.5%); payout_fee is charged in the asset itself on top of each payout.

Payouts

A payout moves coins from your easyway balance to a wallet of yours (or anyone's). In live mode a payout can only go to an address you have whitelisted in the dashboard with 2FA — so a leaked API key can never drain your balance to a stranger. Whitelisting takes effect after a short cooldown.

curl -X POST https://api.easyway.cash/v1/payouts \
  -H "Authorization: Bearer $EASYWAY_API_KEY" \
  -H "Idempotency-Key: settle-2026-09-23" \
  -H "Content-Type: application/json" \
  -d '{"asset":"USDT_TRC20","address":"TJRabPrwbZy45sbavfcjinPJC18kjpRTv8","amount":"500","note":"Daily settlement"}'

{
  "id": "po_3Hd8Kq1Lm5Np7Rs9Tv2Wx4",
  "status": "pending",
  "mode": "live",
  "asset": "USDT_TRC20",
  "address": "TJRabPrwbZy45sbavfcjinPJC18kjpRTv8",
  "memo": null,
  "amount": "500",
  "network_fee": "1",
  "tx_hash": null,
  "failure_reason": null,
  "created_at": "2026-09-23T12:20:00.000Z"
}

Amount + network fee are reserved (locked) immediately. Then: pending → processing (being signed) → sent with a tx_hash, or failed with the funds back on your balance. Subscribe to payout.sent / payout.failed, or poll:

curl https://api.easyway.cash/v1/payouts/po_3Hd8Kq1Lm5Np7Rs9Tv2Wx4 \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

curl https://api.easyway.cash/v1/payouts?page=1&pageSize=50&status=sent&from=2026-09-01&to=2026-09-30 \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

Returns { data: [payout…], total, page, page_size } for the key's mode — handy for reconciling your settlement records: page through one month with from / to until you have total rows. A day is a UTC day.

A walk-through with idempotent retries, the payout webhooks and a go-live checklist: send crypto payouts with the API.

Payment links & hosted checkout

No code at all: create a payment link in Dashboard → Payment links (fixed price, or let the customer type an amount within limits) and share https://easyway.cash/pay/link/pl_…. Each visit mints a normal invoice, so your webhooks fire exactly as for API-created ones.

The hosted checkout page (payment_url) works on phones and desktops, shows a QR code that pre-fills address, amount and memo in wallet apps, polls for the payment itself, and handles under-payments by asking for the remainder. It is safe to open in an <iframe> on your domain.

Idempotency

Networks fail. If your request to create an invoice or payout times out, you can't know whether it went through — unless you sent an Idempotency-Key. Then a retry with the same key and body returns the original result instead of creating a second one. Use something that identifies the action on your side: an order id, a settlement batch id.

Idempotency-Key: order-2048        # 8–128 chars (A–Z a–z 0–9 _ - : .), unique per action

Errors

Errors use conventional HTTP status codes and a small JSON body. error is a stable machine-readable code — match on it, not on the message.

HTTP/1.1 400 Bad Request
{
  "error": "validation_error",
  "fields": ["amount"]
}

fields (validation errors only) names the inputs that were rejected; other errors carry a human-readable message instead.

5xx and network errors: retry with exponential back-off (1 s, 2 s, 4 s…) and the same Idempotency-Key.

Test mode & go-live

Everything exists twice: test and live. Test keys, test invoices, test webhooks and test balances never touch a blockchain. Switch the dashboard to Test mode (top bar) to see and manage sandbox data. A test plan for paid, underpaid, expired and late payments: test crypto payments in sandbox mode.

Go-live checklist

Questions? support@easyway.cash — what to include is on the contact page, and live API and watcher health on system status.