easyway
Log inGet started
API reference · v1

Build crypto payments into anything

One REST API, JSON in and out, and signed webhooks that tell your server when a payment has arrived in your own wallet. 75 coins on 15 networks, no fee taken from payments.

Get an API key Quickstart OpenAPI 3.1

Base URL

https://api.easyway.cash

Auth

Bearer sk_…

Format

JSON · snake_case

POST

/v1/invoices

curl https://api.easyway.cash/v1/invoices \
  -H "Authorization: Bearer sk_test_…" \
  -H "Idempotency-Key: order-2048" \
  -d '{"amount":"149.00","currency":"USD"}'
201

{ "id": "inv_7Q2m…", "payment_url": "…/pay/inv_7Q2m…" }

Quickstart

Create an invoice, redirect, fulfil on the webhook.

Invoices

Fields, lifecycle, under- and overpayments.

Webhooks

Events, signatures and delivery rules.

Playground

Send real sandbox requests from this page.

Paid APIs & x402

Charge apps and AI agents per call.

Errors

Every code, and which ones to retry.

The API changed on 2026-11-17 with the non-custodial release: balances and payouts are gone, and live invoices need a receiving wallet. If you integrated before that date, read the changelog first.

01 · GET STARTED

Overview

easyway is non-custodial. You set your own receiving wallet for each network, and your customers pay straight into it. easyway never holds the coins and has no key to your wallet: it watches the blockchain, works out which invoice each transfer pays, and tells your server. There are no balances, no payouts and no fee taken from a payment.

A payment is an invoice. You create one from your server with the amount your customer owes and redirect them to its payment_url. The customer picks a coin and network and is shown your wallet address with the exact amount to send. Your server learns about the payment from a webhook — never by trusting the browser.

StepWhat happens
0. WalletsOnce, in the dashboard: set a receiving wallet for each network you accept. See Receiving wallets.
1. CreatePOST /v1/invoices with the amount. You get back an id and a payment_url.
2. PayRedirect the customer to payment_url (or open it in a new tab / iframe). The page updates itself while the payment confirms.
3. ConfirmYou receive invoice.paid on your webhook URL. Verify the signature, then fulfil the order. (invoice.underpaid if they sent less.)
4. DoneThe coins are already in your wallet: the full amount, on the network the customer paid on. There is nothing to withdraw.
0. Wallets
Once, in the dashboard: set a receiving wallet for each network you accept. See Receiving wallets.
1. Create
POST /v1/invoices with the amount. You get back an id and a payment_url.
2. Pay
Redirect the customer to payment_url (or open it in a new tab / iframe). The page updates itself while the payment confirms.
3. Confirm
You receive invoice.paid on your webhook URL. Verify the signature, then fulfil the order. (invoice.underpaid if they sent less.)
4. Done
The coins are already in your wallet: the full amount, on the network the customer paid on. There is nothing to withdraw.

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

02 · GET STARTED

Receiving wallets

Set your receiving wallet first. A live invoice can only be created, and paid, in coins whose network has a wallet. Without any wallet POST /v1/invoices answers 409 no_wallets_configured; asking for a coin whose network has none answers 409 wallet_not_configured. Test mode needs no wallet.

Wallets are set in Dashboard → Wallets, one per network, and there is deliberately no API endpoint to change them. You enter public information only: an address, or on Bitcoin-like chains an account-level extended public key. Never a private key or a seed phrase; those are refused. Replacing a wallet requires 2FA, and every change is emailed to the account owner and written to the activity log.

NetworkWhat you enterHow an invoice is recognised
TRONOne addressExact amount per invoice
BNB Smart ChainOne addressExact amount per invoice
TONOne address of your own walletComment (memo) per invoice
EthereumOne addressExact amount per invoice
BitcoinExtended public key (xpub / ypub / zpub) or one addressNew address per invoice (extended public key); exact amount if you set a single address
LitecoinExtended public key (Ltub / Mtub / xpub / ypub / zpub) or one addressNew address per invoice (extended public key); exact amount if you set a single address
DogecoinExtended public key (dgub / xpub) or one addressNew address per invoice (extended public key); exact amount if you set a single address
XRP LedgerOne address of your own walletDestination tag per invoice
SolanaOne addressExact amount per invoice
PolygonOne addressExact amount per invoice
AvalancheOne addressExact amount per invoice
BaseOne addressExact amount per invoice
Arbitrum OneOne addressExact amount per invoice
OP MainnetOne addressExact amount per invoice
DashExtended public key (drkp / xpub) or one addressNew address per invoice (extended public key); exact amount if you set a single address
TRON
One address
Exact amount per invoice
BNB Smart Chain
One address
Exact amount per invoice
TON
One address of your own wallet
Comment (memo) per invoice
Ethereum
One address
Exact amount per invoice
Bitcoin
Extended public key (xpub / ypub / zpub) or one address
New address per invoice (extended public key); exact amount if you set a single address
Litecoin
Extended public key (Ltub / Mtub / xpub / ypub / zpub) or one address
New address per invoice (extended public key); exact amount if you set a single address
Dogecoin
Extended public key (dgub / xpub) or one address
New address per invoice (extended public key); exact amount if you set a single address
XRP Ledger
One address of your own wallet
Destination tag per invoice
Solana
One address
Exact amount per invoice
Polygon
One address
Exact amount per invoice
Avalanche
One address
Exact amount per invoice
Base
One address
Exact amount per invoice
Arbitrum One
One address
Exact amount per invoice
OP Mainnet
One address
Exact amount per invoice
Dash
Extended public key (drkp / xpub) or one address
New address per invoice (extended public key); exact amount if you set a single address
MethodDetails
New address per invoiceBitcoin, Litecoin, Dogecoin, Dash with an extended public key (xpub / ypub / zpub, Ltub / Mtub, dgub, drkp). Each invoice gets the next receive address of that wallet account in pay_address. The dashboard shows the first three derived addresses before you save, so you can compare them with your wallet app.
Memo / destination tagTON and XRP. All invoices share your address; each gets a numeric pay_memo that the customer must attach. Use a wallet of your own, not an exchange deposit address that needs a memo of its own.
Exact amountTRON, Ethereum, BNB Smart Chain, Polygon, Avalanche, Solana, and any Bitcoin-like network where you set a single address. All invoices share your address and are told apart by pay_amount, which is made unique with a few extra decimals. See the note on pay_amount.
New address per invoice
Bitcoin, Litecoin, Dogecoin, Dash with an extended public key (xpub / ypub / zpub, Ltub / Mtub, dgub, drkp). Each invoice gets the next receive address of that wallet account in pay_address. The dashboard shows the first three derived addresses before you save, so you can compare them with your wallet app.
Memo / destination tag
TON and XRP. All invoices share your address; each gets a numeric pay_memo that the customer must attach. Use a wallet of your own, not an exchange deposit address that needs a memo of its own.
Exact amount
TRON, Ethereum, BNB Smart Chain, Polygon, Avalanche, Solana, and any Bitcoin-like network where you set a single address. All invoices share your address and are told apart by pay_amount, which is made unique with a few extra decimals. See the note on pay_amount.

GET /v1/assets tells your integration which coins are usable right now: available is true when the coin's network has a wallet.

03 · GET STARTED

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.

WooCommerce

v0.1.0 · beta

WordPress 6.0+, WooCommerce 7.0+, PHP 7.4+, store currency USD

DownloadHow to install

PrestaShop

v0.1.0 · beta

PrestaShop 8.0+, PHP with curl and json, HTTPS

OpenCart

v0.1.0 · beta

OpenCart 4.0.0.0 – 4.0.2.x, PHP 8.0+ with curl and json, HTTPS

Magento 2

v0.1.0 · beta

Magento 2.4.x, PHP 7.4 or 8.1+, base currency USD

WHMCS

v0.1.0 · beta

WHMCS 8.x, PHP with curl, client currency USD

Blesta

v0.1.0 · beta

Blesta 5.x, PHP with curl, currency USD

Odoo

v17.0.0.1.0 · beta

Odoo 17 (Community or Enterprise) with the payment module, prices in USD

04 · GET STARTED

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)
ModeThe key decides: sk_test_… keys only ever see sandbox data, sk_live_… keys only real payments. There is no mode parameter.
ScopesEach key has scopes: invoices:read, invoices:write, transactions:read. Give a server only what it needs. No scope can move money or change a wallet: the API has no endpoint for either.
IP allowlistOptional per key. With one set, requests from any other IP are refused (403 ip_not_allowed).
Project detailsOptional per key: a business name, a support email and a webhook. Running several shops on one account? Give each its own key — the checkout of every invoice created with that key shows that name and support address (and underpayment alerts go there) instead of the ones in Settings → Business, and its invoice events go to that key's webhook.
Rate limit300 requests per minute per key. Over it you get 429 rate_limited; the RateLimit-* headers tell you when to retry.
Keep it secretNever ship a key in a browser, mobile app or public repo. Rotate it from the dashboard if it leaks — revoking is instant.
Mode
The key decides: sk_test_… keys only ever see sandbox data, sk_live_… keys only real payments. There is no mode parameter.
Scopes
Each key has scopes: invoices:read, invoices:write, transactions:read. Give a server only what it needs. No scope can move money or change a wallet: the API has no endpoint for either.
IP allowlist
Optional per key. With one set, requests from any other IP are refused (403 ip_not_allowed).
Project details
Optional per key: a business name, a support email and a webhook. Running several shops on one account? Give each its own key — the checkout of every invoice created with that key shows that name and support address (and underpayment alerts go there) instead of the ones in Settings → Business, and its invoice events go to that key's webhook.
Rate limit
300 requests per minute per key. Over it you get 429 rate_limited; the RateLimit-* headers tell you when to retry.
Keep it secret
Never ship a key in a browser, mobile app or public repo. Rotate it from the dashboard if it leaks — revoking is instant.

05 · GET STARTED

Quickstart

Set a receiving wallet (or use a test key, which needs none), then 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:

JSON

{
  "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",
  "overpaid_amount": "0",
  "late": false,
  "fee_amount": "0",          // always "0": nothing is taken from a payment
  "net_amount": "0",          // always equal to received_amount
  "customer_email": "jane@example.com",
  "metadata": { "cart": "c_81f2" },
  "payment_url": "https://easyway.cash/pay/inv_7Q2mN4kL8pR1sT9uV3wX0y",
  "expires_at": "2026-11-17T13:15:00.000Z",
  "paid_at": null,
  "created_at": "2026-11-17T12:15:00.000Z"
}

2. Send the customer to the payment page

Node.js

// 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.
Test the whole flow with a sk_test_ key first: sandbox invoices are identical, and the dashboard has a Simulate payment button that fires the real webhook. See Test mode.

06 · GET STARTED

Try it (playground)

Send real requests to the sandbox from this page with a sk_test_ key. Responses are exactly what your code will get; nothing here can touch live data or money.

Kept only in this browser tab. Create one in Dashboard → Developers with test mode on.

Coins, networks, minimums and whether each is available.

07 · API REFERENCE

Invoices

Create an invoice

POST
/v1/invoices
scope invoices:write · supports Idempotency-Key
FieldTypeDescription
amountstring, requiredDecimal string. In currency units: "149.00" USD, or "0.005" when currency is BTC.
currencystring"USD" (default) — the customer chooses the coin and the crypto amount is quoted at payment time — or a coin id such as "USDT_TRC20" to price in that coin (then only that coin is accepted; which to use). Live mode: the coin's network must have a receiving wallet.
order_idstring ≤128Your reference. Comes back on the invoice and in every webhook; searchable in the list endpoint.
descriptionstring ≤500Shown to the customer on the payment page.
customer_emailemailStored on the invoice for your records and support.
success_urlhttp(s) URLWhere the customer can return after paying.
cancel_urlhttp(s) URLWhere the customer can return if they give up.
allowed_assetsstring[]Restrict which coins are offered, e.g. ["USDT_TRC20", "USDT_BEP20"]. Default: every coin you have a wallet for. In live mode, coins without a wallet are dropped from the list; if none is left the request fails with 409 wallet_not_configured. With one id the coin is selected at once (examples).
metadataobjectUp to 20 string values (≤500 chars each). Returned untouched, e.g. your cart or user id.
lifetimeinteger 5–1440Minutes until the invoice expires unpaid. Default: your account setting (60).
amount
string, required
Decimal string. In currency units: "149.00" USD, or "0.005" when currency is BTC.
currency
string
"USD" (default) — the customer chooses the coin and the crypto amount is quoted at payment time — or a coin id such as "USDT_TRC20" to price in that coin (then only that coin is accepted; which to use). Live mode: the coin's network must have a receiving wallet.
order_id
string ≤128
Your reference. Comes back on the invoice and in every webhook; searchable in the list endpoint.
description
string ≤500
Shown to the customer on the payment page.
customer_email
email
Stored on the invoice for your records and support.
success_url
http(s) URL
Where the customer can return after paying.
cancel_url
http(s) URL
Where the customer can return if they give up.
allowed_assets
string[]
Restrict which coins are offered, e.g. ["USDT_TRC20", "USDT_BEP20"]. Default: every coin you have a wallet for. In live mode, coins without a wallet are dropped from the list; if none is left the request fails with 409 wallet_not_configured. With one id the coin is selected at once (examples).
metadata
object
Up to 20 string values (≤500 chars each). Returned untouched, e.g. your cart or user id.
lifetime
integer 5–1440
Minutes until the invoice expires unpaid. Default: your account setting (60).

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}'

An invoice priced in a coin (or limited to one coin) has its payment details in the response straight away. This one was asked for 25 USDT on a wallet matched by exact amount, while another open invoice already asked for 25:

JSON

{
  "id": "inv_2Bk9Xw4Hs7Ld1Qm6Zt3Vn8",
  "status": "pending",
  "amount": "25",
  "currency": "USDT_TRC20",
  "pay_asset": "USDT_TRC20",
  "pay_amount": "25.001",     // show THIS to the customer, not "25"
  "pay_address": "TJRabPrwbZy45sbavfcjinPJC18kjpRTv8",   // your own wallet
  "pay_memo": null,
  "pay_network": "TRON · TRC-20",
  …
}

Always show pay_amount

On networks matched by exact amount, pay_amount can differ slightly from the amount you asked for. It is rounded up to a few decimals and, if another open invoice on the same address already asks for that amount, raised by one small step until it is unique (25 → 25.001 → 25.002 …). One step is worth about a tenth of a cent or less. If you build your own payment UI, always display pay_amount, pay_address and pay_memo exactly as returned, or simply redirect to payment_url. A customer who sends your original round amount may be matched to the wrong invoice or to none.

The invoice object

FieldTypeDescription
idstringinv_ + 22 characters. Also the last part of payment_url.
statusstringpending → confirming → paid; or underpaid, expired, cancelled. See lifecycle below.
modestringlive or test.
amount / currencystringWhat you asked for, as a canonical decimal string: trailing zeros are dropped ("149.00" comes back as "149"), USD keeps at most 2 decimals.
pay_assetstring | nullThe coin the customer chose (e.g. USDT_TRC20); null until they choose.
pay_amountstring | nullHow much of that coin they must send — quoted at selection and locked for the invoice's lifetime. May carry extra decimals; see above.
pay_addressstring | nullWhere to send it: your own receiving wallet. A fresh address per invoice with an extended public key; otherwise the same address for every invoice on that network.
pay_memostring | nullWhen non-null, the customer must attach it (TON comment / XRP destination tag). The payment page shows it and encodes it in the QR.
pay_networkstring | nullHuman-readable network name of pay_asset.
ratestring | nullUSD price of one unit of pay_asset at quote time.
received_amountstringConfirmed on-chain amount so far, in pay_asset.
remaining_amountstringWhat is still owed (0 once the full amount arrived). Non-zero with status underpaid — and also on a paid invoice that came in short within your underpayment tolerance, so decide on status, not on this field.
overpaid_amountstringWhat arrived on top of pay_amount; "0" unless the customer overpaid or paid twice.
latebooleantrue when a payment arrived after the invoice had expired or been cancelled.
fee_amount / net_amountstringKept for compatibility. fee_amount is always "0" and net_amount equals received_amount: the whole payment is in your wallet.
payment_urlstringThe hosted payment page for this invoice.
expires_at / paid_at / created_atISO-8601UTC timestamps.
id
string
inv_ + 22 characters. Also the last part of payment_url.
status
string
pending → confirming → paid; or underpaid, expired, cancelled. See lifecycle below.
mode
string
live or test.
amount / currency
string
What you asked for, as a canonical decimal string: trailing zeros are dropped ("149.00" comes back as "149"), USD keeps at most 2 decimals.
pay_asset
string | null
The coin the customer chose (e.g. USDT_TRC20); null until they choose.
pay_amount
string | null
How much of that coin they must send — quoted at selection and locked for the invoice's lifetime. May carry extra decimals; see above.
pay_address
string | null
Where to send it: your own receiving wallet. A fresh address per invoice with an extended public key; otherwise the same address for every invoice on that network.
pay_memo
string | null
When non-null, the customer must attach it (TON comment / XRP destination tag). The payment page shows it and encodes it in the QR.
pay_network
string | null
Human-readable network name of pay_asset.
rate
string | null
USD price of one unit of pay_asset at quote time.
received_amount
string
Confirmed on-chain amount so far, in pay_asset.
remaining_amount
string
What is still owed (0 once the full amount arrived). Non-zero with status underpaid — and also on a paid invoice that came in short within your underpayment tolerance, so decide on status, not on this field.
overpaid_amount
string
What arrived on top of pay_amount; "0" unless the customer overpaid or paid twice.
late
boolean
true when a payment arrived after the invoice had expired or been cancelled.
fee_amount / net_amount
string
Kept for compatibility. fee_amount is always "0" and net_amount equals received_amount: the whole payment is in your wallet.
payment_url
string
The hosted payment page for this invoice.
expires_at / paid_at / created_at
ISO-8601
UTC timestamps.

Lifecycle

StatusMeaningWhat you should do
pendingCreated; nothing seen on-chain yet.Nothing. Expires at expires_at if unpaid.
confirmingA payment was seen but is not final yet (waiting for confirmations).Nothing — you get invoice.confirming so you can show \"payment detected\".
paidFinal. The amount (within your underpayment tolerance, default 1%) has arrived in your wallet.Fulfil the order on invoice.paid. This is the only status that means paid in full.
underpaidFinal, but less than the amount arrived. remaining_amount says how much is missing.What was sent is in your wallet. The checkout asks the customer for the remainder; you decide whether to fulfil partially, wait, or refund from your own wallet.
expiredNobody paid before expires_at.A payment that arrives while the invoice is still being watched is recorded, late becomes true and the invoice moves to paid or underpaid — so keep handling invoice.paid for old ids.
cancelledYou cancelled it (dashboard or API) while it was pending.Nothing. A payment that was already on its way is recorded the same way as for an expired invoice.
pending
Created; nothing seen on-chain yet.
Nothing. Expires at expires_at if unpaid.
confirming
A payment was seen but is not final yet (waiting for confirmations).
Nothing — you get invoice.confirming so you can show \"payment detected\".
paid
Final. The amount (within your underpayment tolerance, default 1%) has arrived in your wallet.
Fulfil the order on invoice.paid. This is the only status that means paid in full.
underpaid
Final, but less than the amount arrived. remaining_amount says how much is missing.
What was sent is in your wallet. The checkout asks the customer for the remainder; you decide whether to fulfil partially, wait, or refund from your own wallet.
expired
Nobody paid before expires_at.
A payment that arrives while the invoice is still being watched is recorded, late becomes true and the invoice moves to paid or underpaid — so keep handling invoice.paid for old ids.
cancelled
You cancelled it (dashboard or API) while it was pending.
Nothing. A payment that was already on its way is recorded the same way as for an expired invoice.

Underpaid, overpaid and late payments

CaseWhat you see
UnderpaidStatus underpaid, remaining_amount > 0, event invoice.underpaid. A top-up that completes the amount moves it to paid. Payments within your tolerance (Dashboard → Settings, 0–5%) count as paid.
OverpaidStatus paid, overpaid_amount > 0, event invoice.overpaid (also when a paid invoice is paid a second time). The extra coins are in your wallet; returning them is your decision.
LateA payment after expiry or cancellation sets late: true and fires invoice.paid or invoice.underpaid. An invoice stays watched for seven days after expiry on a per-invoice address, and for a few hours on a shared address (memo or exact amount). After that the transfer is not recorded by easyway; it is still in your wallet.
UnmatchedA transfer that cannot be tied to exactly one invoice. See Unmatched transactions.
Underpaid
Status underpaid, remaining_amount > 0, event invoice.underpaid. A top-up that completes the amount moves it to paid. Payments within your tolerance (Dashboard → Settings, 0–5%) count as paid.
Overpaid
Status paid, overpaid_amount > 0, event invoice.overpaid (also when a paid invoice is paid a second time). The extra coins are in your wallet; returning them is your decision.
Late
A payment after expiry or cancellation sets late: true and fires invoice.paid or invoice.underpaid. An invoice stays watched for seven days after expiry on a per-invoice address, and for a few hours on a shared address (memo or exact amount). After that the transfer is not recorded by easyway; it is still in your wallet.
Unmatched
A transfer that cannot be tied to exactly one invoice. See Unmatched transactions.

Every invoice keeps a status history (created, coin selected, detected, confirming, paid, underpaid, overpaid, late payment, expired, cancelled, assigned) with the transaction id and amounts. It is shown on the invoice in the dashboard.

The customer's wallet or exchange may deduct its own fee from the amount sent. Tell customers to send the exact pay_amount, and pick a tolerance in Dashboard → Settings that suits your margins. Refunds are transfers you send from your own wallet; easyway cannot send or reverse a payment. Every case with a handler you can copy: underpaid and late payments.

Retrieve an invoice

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

List invoices

GET
/v1/invoices
scope invoices:read
FieldTypeDescription
pageinteger1-based, default 1. Newest first.
pageSizeinteger1–100, default 20.
statusstringOnly invoices in this state: pending, confirming, paid, underpaid, expired or cancelled.
assetstringOnly invoices paid (or to be paid) in this coin id.
order_idstringOnly invoices with exactly this order_id.
from / toYYYY-MM-DDOnly invoices created in this range of UTC days, both inclusive. Either side may be left out.
page
integer
1-based, default 1. Newest first.
pageSize
integer
1–100, default 20.
status
string
Only invoices in this state: pending, confirming, paid, underpaid, expired or cancelled.
asset
string
Only invoices paid (or to be paid) in this coin id.
order_id
string
Only invoices with exactly this order_id.
from / to
YYYY-MM-DD
Only invoices created in this range of UTC days, both inclusive. Either side may be left out.
curl https://api.easyway.cash/v1/invoices?page=1&pageSize=50&status=paid&from=2026-11-01&to=2026-11-30 \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

JSON

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

Cancel an invoice

POST
/v1/invoices/:id/cancel
scope invoices:write · only while pending
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).

08 · API REFERENCE

Unmatched transactions

When a confirmed transfer reaches one of your shared addresses and cannot be tied to exactly one invoice, easyway does not guess. It parks the transfer as an unmatched transaction, fires transaction.unmatched on your account webhooks, and lists it in the dashboard, where you assign it to an invoice (which then moves along exactly as if it had matched) or mark it as ignored. The coins are in your wallet either way.

reasonMeaning
memo_missingTON / XRP: the transfer carried no numeric comment or destination tag.
memo_unknownTON / XRP: the memo does not belong to an invoice being watched.
no_invoice_for_amountExact-amount networks: no open invoice on that address asks for this coin.
ambiguous_amountExact-amount networks: the amount fits several open invoices, or none of several.
memo_missing
TON / XRP: the transfer carried no numeric comment or destination tag.
memo_unknown
TON / XRP: the memo does not belong to an invoice being watched.
no_invoice_for_amount
Exact-amount networks: no open invoice on that address asks for this coin.
ambiguous_amount
Exact-amount networks: the amount fits several open invoices, or none of several.
GET
/v1/transactions/unmatched
scope transactions:read
FieldTypeDescription
page / pageSizeintegerAs for invoices.
statusstringopen, assigned or ignored.
from / toYYYY-MM-DDCreated in this range of UTC days, both inclusive.
page / pageSize
integer
As for invoices.
status
string
open, assigned or ignored.
from / to
YYYY-MM-DD
Created in this range of UTC days, both inclusive.
curl https://api.easyway.cash/v1/transactions/unmatched?status=open \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

JSON

{ "data": [
  { "id": "utx_8Fq2Lm5Np7Rs9Tv2Wx4Hd3",
    "status": "open",
    "mode": "live",
    "asset": "USDT_TRC20",
    "network": "TRON · TRC-20",
    "address": "TJRabPrwbZy45sbavfcjinPJC18kjpRTv8",
    "memo": null,
    "amount": "24",
    "tx_hash": "4f0c…9be1",
    "log_index": 0,
    "from_address": "TQn9Y2khEsLJW1ChVWFMSMeRDow5KcbLSE",
    "reason": "ambiguous_amount",
    "block_time": "2026-11-17T12:31:09.000Z",
    "created_at": "2026-11-17T12:32:40.000Z" }
], "total": 1, "page": 1, "page_size": 20 }

Assigning and ignoring are done in the dashboard; the API is read-only here. Only confirmed live transfers are parked. With a per-invoice address (extended public key) every transfer to the address belongs to its invoice, so nothing ends up unmatched.

09 · API REFERENCE

Coins & networks

Every (coin, network) pair has its own id — USDT on TRON and USDT on Ethereum are different coins that arrive in different wallets. Use these ids in currency, allowed_assets and pay_asset.

idCoinNetworkConfirmationsSmallest invoice
USDT_TRC20USDTTRON · TRC-20190.5 USDT
USDT_BEP20USDTBNB Smart Chain · BEP-20150.5 USDT
USDT_TONUSDTTON · Jetton10.5 USDT
USDT_ERC20USDTEthereum · ERC-20120.5 USDT
TRXTRXTRON191.5 TRX
BNBBNBBNB Smart Chain150.0007 BNB
GRAMGRAMTON10.35 GRAM
ETHETHEthereum120.0002 ETH
BTCBTCBitcoin20.00001 BTC
LTCLTCLitecoin40.008 LTC
DOGEDOGEDogecoin65 DOGE
USDC_ERC20USDCEthereum · ERC-20120.5 USDC
USDC_BEP20USDCBNB Smart Chain · BEP-20150.5 USDC
XRPXRPXRP Ledger10.35 XRP
SOLSOLSolana10.005 SOL
USDT_SOLUSDTSolana · SPL10.5 USDT
USDC_SOLUSDCSolana · SPL10.5 USDC
POLPOLPolygon644 POL
USDT_POLYGONUSDTPolygon · PoS640.5 USDT
USDC_POLYGONUSDCPolygon · PoS640.5 USDC
AVAXAVAXAvalanche C-Chain100.05 AVAX
USDT_AVAXUSDTAvalanche · C-Chain100.5 USDT
ETH_BASEETHBase300.0002 ETH
USDC_BASEUSDCBase300.5 USDC
ETH_ARBETHArbitrum One2400.0002 ETH
USDT_ARBUSDTArbitrum One2400.5 USDT
USDC_ARBUSDCArbitrum One2400.5 USDC
ETH_OPETHOP Mainnet300.0002 ETH
USDT_OPUSDTOP Mainnet300.5 USDT
USDC_OPUSDCOP Mainnet300.5 USDC
USDC_AVAXUSDCAvalanche · C-Chain100.5 USDC
DAI_ERC20DAIEthereum · ERC-20120.5 DAI
FDUSD_BEP20FDUSDBNB Smart Chain · BEP-20150.5 FDUSD
DASHDASHDash40.01 DASH
SHIB_ERC20SHIBEthereum · ERC-2012100000 SHIB
PEPE_ERC20PEPEEthereum · ERC-2012120000 PEPE
BONK_SOLBONKSolana · SPL1150000 BONK
NOT_TONNOTTON · Jetton11000 NOT
PYUSD_ERC20PYUSDEthereum · ERC-20120.5 PYUSD
DOGS_TONDOGSTON · Jetton110000 DOGS
CATI_TONCATITON · Jetton18 CATI
HMSTR_TONHMSTRTON · Jetton13500 HMSTR
WIF_SOLWIFSolana · SPL13 WIF
LINK_ERC20LINKEthereum · ERC-20120.05 LINK
UNI_ERC20UNIEthereum · ERC-20120.08 UNI
AAVE_ERC20AAVEEthereum · ERC-20120.004 AAVE
ONDO_ERC20ONDOEthereum · ERC-20121.3 ONDO
ENA_ERC20ENAEthereum · ERC-20122.6 ENA
CRV_ERC20CRVEthereum · ERC-20121.6 CRV
GRT_ERC20GRTEthereum · ERC-201227 GRT
SKY_ERC20SKYEthereum · ERC-20128 SKY
USDS_ERC20USDSEthereum · ERC-20120.5 USDS
USDE_ERC20USDeEthereum · ERC-20120.5 USDe
MNT_ERC20MNTEthereum · ERC-20121.1 MNT
ARB_ERC20ARBEthereum · ERC-20123.5 ARB
WLD_ERC20WLDEthereum · ERC-20121.4 WLD
MANA_ERC20MANAEthereum · ERC-20127 MANA
SAND_ERC20SANDEthereum · ERC-201211 SAND
IMX_ERC20IMXEthereum · ERC-20124 IMX
GALA_ERC20GALAEthereum · ERC-2012310 GALA
FET_ERC20FETEthereum · ERC-20123.5 FET
JASMY_ERC20JASMYEthereum · ERC-2012140 JASMY
SPX_ERC20SPXEthereum · ERC-20121.4 SPX
XCN_ERC20XCNEthereum · ERC-2012150 XCN
APE_ERC20APEEthereum · ERC-20125 APE
AXS_ERC20AXSEthereum · ERC-20120.65 AXS
CHZ_ERC20CHZEthereum · ERC-201247 CHZ
1INCH_ERC201INCHEthereum · ERC-20127 1INCH
PENDLE_ERC20PENDLEEthereum · ERC-20120.35 PENDLE
ETHFI_ERC20ETHFIEthereum · ERC-20120.9 ETHFI
ZRO_ERC20ZROEthereum · ERC-20120.35 ZRO
BAT_ERC20BATEthereum · ERC-20125 BAT
LPT_ERC20LPTEthereum · ERC-20120.45 LPT
ZRX_ERC20ZRXEthereum · ERC-20126.5 ZRX
SUSHI_ERC20SUSHIEthereum · ERC-20123.5 SUSHI
BAL_ERC20BALEthereum · ERC-20124.5 BAL
COMP_ERC20COMPEthereum · ERC-20120.03 COMP
RPL_ERC20RPLEthereum · ERC-20120.45 RPL
ANKR_ERC20ANKREthereum · ERC-2012170 ANKR
CVX_ERC20CVXEthereum · ERC-20120.4 CVX
GLM_ERC20GLMEthereum · ERC-20126 GLM
CAKE_BEP20CAKEBNB Smart Chain · BEP-20150.25 CAKE
TWT_BEP20TWTBNB Smart Chain · BEP-20151.2 TWT
RENDER_SOLRENDERSolana · SPL10.3 RENDER
JUP_SOLJUPSolana · SPL12 JUP
PYTH_SOLPYTHSolana · SPL18 PYTH
JTO_SOLJTOSolana · SPL11.4 JTO
RAY_SOLRAYSolana · SPL10.35 RAY
W_SOLWSolana · SPL153 W
FARTCOIN_SOLFARTCOINSolana · SPL15.2 FARTCOIN
TRUMP_SOLTRUMPSolana · SPL10.53 TRUMP
PENGU_SOLPENGUSolana · SPL197 PENGU
POPCAT_SOLPOPCATSolana · SPL119.5 POPCAT
USDT_TRC20
CoinUSDT
NetworkTRON · TRC-20
Confirmations19
Smallest invoice0.5 USDT
USDT_BEP20
CoinUSDT
NetworkBNB Smart Chain · BEP-20
Confirmations15
Smallest invoice0.5 USDT
USDT_TON
CoinUSDT
NetworkTON · Jetton
Confirmations1
Smallest invoice0.5 USDT
USDT_ERC20
CoinUSDT
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.5 USDT
TRX
CoinTRX
NetworkTRON
Confirmations19
Smallest invoice1.5 TRX
BNB
CoinBNB
NetworkBNB Smart Chain
Confirmations15
Smallest invoice0.0007 BNB
GRAM
CoinGRAM
NetworkTON
Confirmations1
Smallest invoice0.35 GRAM
ETH
CoinETH
NetworkEthereum
Confirmations12
Smallest invoice0.0002 ETH
BTC
CoinBTC
NetworkBitcoin
Confirmations2
Smallest invoice0.00001 BTC
LTC
CoinLTC
NetworkLitecoin
Confirmations4
Smallest invoice0.008 LTC
DOGE
CoinDOGE
NetworkDogecoin
Confirmations6
Smallest invoice5 DOGE
USDC_ERC20
CoinUSDC
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.5 USDC
USDC_BEP20
CoinUSDC
NetworkBNB Smart Chain · BEP-20
Confirmations15
Smallest invoice0.5 USDC
XRP
CoinXRP
NetworkXRP Ledger
Confirmations1
Smallest invoice0.35 XRP
SOL
CoinSOL
NetworkSolana
Confirmations1
Smallest invoice0.005 SOL
USDT_SOL
CoinUSDT
NetworkSolana · SPL
Confirmations1
Smallest invoice0.5 USDT
USDC_SOL
CoinUSDC
NetworkSolana · SPL
Confirmations1
Smallest invoice0.5 USDC
POL
CoinPOL
NetworkPolygon
Confirmations64
Smallest invoice4 POL
USDT_POLYGON
CoinUSDT
NetworkPolygon · PoS
Confirmations64
Smallest invoice0.5 USDT
USDC_POLYGON
CoinUSDC
NetworkPolygon · PoS
Confirmations64
Smallest invoice0.5 USDC
AVAX
CoinAVAX
NetworkAvalanche C-Chain
Confirmations10
Smallest invoice0.05 AVAX
USDT_AVAX
CoinUSDT
NetworkAvalanche · C-Chain
Confirmations10
Smallest invoice0.5 USDT
ETH_BASE
CoinETH
NetworkBase
Confirmations30
Smallest invoice0.0002 ETH
USDC_BASE
CoinUSDC
NetworkBase
Confirmations30
Smallest invoice0.5 USDC
ETH_ARB
CoinETH
NetworkArbitrum One
Confirmations240
Smallest invoice0.0002 ETH
USDT_ARB
CoinUSDT
NetworkArbitrum One
Confirmations240
Smallest invoice0.5 USDT
USDC_ARB
CoinUSDC
NetworkArbitrum One
Confirmations240
Smallest invoice0.5 USDC
ETH_OP
CoinETH
NetworkOP Mainnet
Confirmations30
Smallest invoice0.0002 ETH
USDT_OP
CoinUSDT
NetworkOP Mainnet
Confirmations30
Smallest invoice0.5 USDT
USDC_OP
CoinUSDC
NetworkOP Mainnet
Confirmations30
Smallest invoice0.5 USDC
USDC_AVAX
CoinUSDC
NetworkAvalanche · C-Chain
Confirmations10
Smallest invoice0.5 USDC
DAI_ERC20
CoinDAI
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.5 DAI
FDUSD_BEP20
CoinFDUSD
NetworkBNB Smart Chain · BEP-20
Confirmations15
Smallest invoice0.5 FDUSD
DASH
CoinDASH
NetworkDash
Confirmations4
Smallest invoice0.01 DASH
SHIB_ERC20
CoinSHIB
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice100000 SHIB
PEPE_ERC20
CoinPEPE
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice120000 PEPE
BONK_SOL
CoinBONK
NetworkSolana · SPL
Confirmations1
Smallest invoice150000 BONK
NOT_TON
CoinNOT
NetworkTON · Jetton
Confirmations1
Smallest invoice1000 NOT
PYUSD_ERC20
CoinPYUSD
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.5 PYUSD
DOGS_TON
CoinDOGS
NetworkTON · Jetton
Confirmations1
Smallest invoice10000 DOGS
CATI_TON
CoinCATI
NetworkTON · Jetton
Confirmations1
Smallest invoice8 CATI
HMSTR_TON
CoinHMSTR
NetworkTON · Jetton
Confirmations1
Smallest invoice3500 HMSTR
WIF_SOL
CoinWIF
NetworkSolana · SPL
Confirmations1
Smallest invoice3 WIF
LINK_ERC20
CoinLINK
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.05 LINK
UNI_ERC20
CoinUNI
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.08 UNI
AAVE_ERC20
CoinAAVE
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.004 AAVE
ONDO_ERC20
CoinONDO
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice1.3 ONDO
ENA_ERC20
CoinENA
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice2.6 ENA
CRV_ERC20
CoinCRV
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice1.6 CRV
GRT_ERC20
CoinGRT
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice27 GRT
SKY_ERC20
CoinSKY
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice8 SKY
USDS_ERC20
CoinUSDS
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.5 USDS
USDE_ERC20
CoinUSDe
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.5 USDe
MNT_ERC20
CoinMNT
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice1.1 MNT
ARB_ERC20
CoinARB
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice3.5 ARB
WLD_ERC20
CoinWLD
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice1.4 WLD
MANA_ERC20
CoinMANA
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice7 MANA
SAND_ERC20
CoinSAND
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice11 SAND
IMX_ERC20
CoinIMX
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice4 IMX
GALA_ERC20
CoinGALA
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice310 GALA
FET_ERC20
CoinFET
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice3.5 FET
JASMY_ERC20
CoinJASMY
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice140 JASMY
SPX_ERC20
CoinSPX
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice1.4 SPX
XCN_ERC20
CoinXCN
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice150 XCN
APE_ERC20
CoinAPE
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice5 APE
AXS_ERC20
CoinAXS
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.65 AXS
CHZ_ERC20
CoinCHZ
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice47 CHZ
1INCH_ERC20
Coin1INCH
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice7 1INCH
PENDLE_ERC20
CoinPENDLE
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.35 PENDLE
ETHFI_ERC20
CoinETHFI
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.9 ETHFI
ZRO_ERC20
CoinZRO
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.35 ZRO
BAT_ERC20
CoinBAT
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice5 BAT
LPT_ERC20
CoinLPT
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.45 LPT
ZRX_ERC20
CoinZRX
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice6.5 ZRX
SUSHI_ERC20
CoinSUSHI
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice3.5 SUSHI
BAL_ERC20
CoinBAL
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice4.5 BAL
COMP_ERC20
CoinCOMP
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.03 COMP
RPL_ERC20
CoinRPL
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.45 RPL
ANKR_ERC20
CoinANKR
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice170 ANKR
CVX_ERC20
CoinCVX
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice0.4 CVX
GLM_ERC20
CoinGLM
NetworkEthereum · ERC-20
Confirmations12
Smallest invoice6 GLM
CAKE_BEP20
CoinCAKE
NetworkBNB Smart Chain · BEP-20
Confirmations15
Smallest invoice0.25 CAKE
TWT_BEP20
CoinTWT
NetworkBNB Smart Chain · BEP-20
Confirmations15
Smallest invoice1.2 TWT
RENDER_SOL
CoinRENDER
NetworkSolana · SPL
Confirmations1
Smallest invoice0.3 RENDER
JUP_SOL
CoinJUP
NetworkSolana · SPL
Confirmations1
Smallest invoice2 JUP
PYTH_SOL
CoinPYTH
NetworkSolana · SPL
Confirmations1
Smallest invoice8 PYTH
JTO_SOL
CoinJTO
NetworkSolana · SPL
Confirmations1
Smallest invoice1.4 JTO
RAY_SOL
CoinRAY
NetworkSolana · SPL
Confirmations1
Smallest invoice0.35 RAY
W_SOL
CoinW
NetworkSolana · SPL
Confirmations1
Smallest invoice53 W
FARTCOIN_SOL
CoinFARTCOIN
NetworkSolana · SPL
Confirmations1
Smallest invoice5.2 FARTCOIN
TRUMP_SOL
CoinTRUMP
NetworkSolana · SPL
Confirmations1
Smallest invoice0.53 TRUMP
PENGU_SOL
CoinPENGU
NetworkSolana · SPL
Confirmations1
Smallest invoice97 PENGU
POPCAT_SOL
CoinPOPCAT
NetworkSolana · SPL
Confirmations1
Smallest invoice19.5 POPCAT

The smallest invoice is about half a dollar on every network; below it the coin cannot be selected (400 amount_below_minimum). “Confirmations” is how many blocks a payment must be buried under before the invoice is marked paid: 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.

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

JSON

{ "fee_bps": 0,
  "data": [
    { "id": "USDT_TRC20", "symbol": "USDT", "name": "Tether", "network": "TRON", "network_label": "TRON · TRC-20",
      "memo_required": false, "decimals": 6, "confirmations": 19, "min_amount": "0.5",
      "available": true, "monitor_ok": true },
    …
  ] }
FieldTypeDescription
fee_bpsintegerAlways 0. Kept so older integrations keep parsing the response.
memo_requiredbooleantrue on TON and XRP: an invoice in this coin carries a pay_memo.
min_amountstringSmallest amount an invoice may ask for in this coin.
availablebooleanCan this key take payments in the coin right now? Live keys: true when the coin's network has a receiving wallet and you have not switched the coin off. Test keys: always true.
monitor_okbooleanIs the chain watcher for this network reporting in? false means payments are detected late, not lost.
fee_bps
integer
Always 0. Kept so older integrations keep parsing the response.
memo_required
boolean
true on TON and XRP: an invoice in this coin carries a pay_memo.
min_amount
string
Smallest amount an invoice may ask for in this coin.
available
boolean
Can this key take payments in the coin right now? Live keys: true when the coin's network has a receiving wallet and you have not switched the coin off. Test keys: always true.
monitor_ok
boolean
Is the chain watcher for this network reporting in? false means payments are detected late, not lost.
GET
/v1/rates
any key
curl https://api.easyway.cash/v1/rates \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

JSON

{ "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.

10 · API REFERENCE

Plans & limits

No fee is taken from payments. easyway is paid for by subscription plans, each with a monthly allowance. The standard plans are below; your dashboard's Plan page shows the ones that apply to your account and is where you buy or renew one, paying in crypto through an ordinary easyway checkout. Details are on the pricing page.

PlanPriceLive invoices / monthLive API keysWebhook endpointsPayment linksWhite-label checkout
FreeFree30113No
Starter$19 / month · $190 / year3003320No
Business$59 / month · $590 / year3,0001010UnlimitedYes
Enterprise$149 / month · $1,490 / yearUnlimitedUnlimitedUnlimitedUnlimitedYes
Free
PriceFree
Live invoices / month30
Live API keys1
Webhook endpoints1
Payment links3
White-label checkoutNo
Starter
Price$19 / month · $190 / year
Live invoices / month300
Live API keys3
Webhook endpoints3
Payment links20
White-label checkoutNo
Business
Price$59 / month · $590 / year
Live invoices / month3,000
Live API keys10
Webhook endpoints10
Payment linksUnlimited
White-label checkoutYes
Enterprise
Price$149 / month · $1,490 / year
Live invoices / monthUnlimited
Live API keysUnlimited
Webhook endpointsUnlimited
Payment linksUnlimited
White-label checkoutYes
RuleDetails
What countsEvery invoice created in live mode: API, dashboard and payment links, paid or not. The count resets on the first day of each calendar month (UTC).
Test modeNever limited.
At the limitPOST /v1/invoices answers 402 plan_invoice_limit_reached. Invoices that are already open keep working and payments to them are still detected and reported.
When a plan endsThe account falls back to Free and its limits. Open invoices keep working. Nothing is deleted.
Other limitsCreating a live API key, account webhook or payment link beyond the allowance is refused in the dashboard (plan_api_key_limit_reached, plan_webhook_limit_reached, plan_paylink_limit_reached).
What counts
Every invoice created in live mode: API, dashboard and payment links, paid or not. The count resets on the first day of each calendar month (UTC).
Test mode
Never limited.
At the limit
POST /v1/invoices answers 402 plan_invoice_limit_reached. Invoices that are already open keep working and payments to them are still detected and reported.
When a plan ends
The account falls back to Free and its limits. Open invoices keep working. Nothing is deleted.
Other limits
Creating a live API key, account webhook or payment link beyond the allowance is refused in the dashboard (plan_api_key_limit_reached, plan_webhook_limit_reached, plan_paylink_limit_reached).
GET
/v1/account
any key
curl https://api.easyway.cash/v1/account \
  -H "Authorization: Bearer $EASYWAY_API_KEY"

JSON

{
  "plan":  { "id": "starter", "name": "Starter", "expires_at": "2026-12-17T09:40:00.000Z", "invoices_per_month": 300 },
  "usage": { "invoices_this_month": 212, "resets_at": "2026-12-01T00:00:00.000Z" }
}

invoices_per_month is null when unlimited, and expires_at is null on the Free plan. Poll this before a busy period, or alert yourself when usage gets close to the allowance.

Sell your own API, model or data per use. Define products with a price per unit in Dashboard → Paid API & agents (fractions of a cent are fine). Each consumer — an app, a customer, an AI agent — gets a ck_… key and a prepaid USD balance, topped up by paying an ordinary invoice straight to your wallet. Your server deducts each use with one call. easyway holds no money here either: the balance is your record of what the consumer prepaid.

POST
/v1/metering/charge
scope invoices:write · idempotent per request_id
curl -X POST https://api.easyway.cash/v1/metering/charge \
  -H "Authorization: Bearer $EASYWAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"consumer_key":"ck_live_…","product":"search","units":3,"request_id":"req-8812"}'
FieldTypeDescription
consumer / consumer_key / external_idstringWho is charged: the consumer id (con_…), its key (ck_…) or your own id for it. One of them is required.
productstring, requiredProduct id or slug, e.g. search.
unitsstringHow many units, default 1. Cost = units × the product's price.
request_idstringYour id for this use. Sending it again never charges twice (duplicate: true).
consumer / consumer_key / external_id
string
Who is charged: the consumer id (con_…), its key (ck_…) or your own id for it. One of them is required.
product
string, required
Product id or slug, e.g. search.
units
string
How many units, default 1. Cost = units × the product's price.
request_id
string
Your id for this use. Sending it again never charges twice (duplicate: true).

A charge is atomic: parallel requests can never take the balance below zero. When the balance is too low the answer is 402 insufficient_balance with charged: false; create a top-up with POST /v1/metering/consumers/:id/topups. A consumer holding only its key can read its balance and ask for a top-up itself at GET /api/meter/balance and POST /api/meter/topup (header X-Consumer-Key).

Pay-per-request with x402

For agents without an account, switch on x402 for a product. Your server answers a request without payment with HTTP 402 and the body of POST /v1/x402/requirements (an invoice for this one request, with an accepts[] entry per coin). The agent pays, retries with an X-PAYMENT header, and you verify and settle it — each payment unlocks exactly one request, and a replay is refused. The JavaScript SDK ships an x402Guard middleware that does all three steps.

POST
/v1/x402/verify
scope invoices:write
curl -X POST https://api.easyway.cash/v1/x402/verify \
  -H "Authorization: Bearer $EASYWAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"payment":"<X-PAYMENT header>","resource":"/reports/42"}'
Every on-chain payment has the coin's minimum (about $0.50), so per-request x402 suits pricier calls. For fractions of a cent, use a prepaid balance and /v1/metering/charge.

12 · API REFERENCE

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 — unmatched transactions, 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:

JSON

{
  "id": "evt_5Gz2Kq8Lm1Np4Rs7Tv0Wx3",
  "type": "invoice.paid",
  "mode": "live",
  "created": 1794918900,
  "data": {
    "invoice": { …the invoice object, exactly as GET /v1/invoices/:id returns it… }
  }
}
EventWhen
invoice.createdAn invoice was created (API, dashboard or payment link).
invoice.confirmingA payment was seen on-chain and is waiting for confirmations.
invoice.paidThe payment is final and in your wallet. Fulfil the order.
invoice.underpaidA final payment arrived, but less than the amount. data.invoice.remaining_amount says how much is missing.
invoice.overpaidMore than the amount arrived, or a paid invoice was paid again. data.invoice.overpaid_amount says how much. Sent in addition to invoice.paid.
invoice.expiredThe invoice expired unpaid.
invoice.cancelledThe invoice was cancelled.
transaction.unmatchedA transfer reached your wallet but could not be tied to one invoice. data.transaction is the object shown under Unmatched transactions. Account webhooks only.
webhook.testSent by the “Send test” button in the dashboard.
invoice.created
An invoice was created (API, dashboard or payment link).
invoice.confirming
A payment was seen on-chain and is waiting for confirmations.
invoice.paid
The payment is final and in your wallet. Fulfil the order.
invoice.underpaid
A final payment arrived, but less than the amount. data.invoice.remaining_amount says how much is missing.
invoice.overpaid
More than the amount arrived, or a paid invoice was paid again. data.invoice.overpaid_amount says how much. Sent in addition to invoice.paid.
invoice.expired
The invoice expired unpaid.
invoice.cancelled
The invoice was cancelled.
transaction.unmatched
A transfer reached your wallet but could not be tied to one invoice. data.transaction is the object shown under Unmatched transactions. Account webhooks only.
webhook.test
Sent by the “Send test” button in the dashboard.

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

Respond fastAnswer 2xx within 10 seconds, then do the work. Anything else (timeouts, 4xx, 5xx) counts as a failure.
RetriesA failed delivery is tried up to 8 times in about 45 hours, retrying after 1 min, 5 min, 30 min, 2 h, 6 h, 12 h, 24 h. You can also retry any delivery by hand from the dashboard, which shows every attempt, status code and error.
Idempotent handlersThe same event can reach you twice (a retry after a slow 200). Store event.id and skip repeats — or make your handler naturally idempotent (“set order 2048 to paid” is safe to run twice).
OrderEvents are not guaranteed to arrive in order. Decide from the invoice's status in the payload, not from which event came last.
Source of truthIf in doubt, GET /v1/invoices/:id. The payload is a snapshot from the moment the event was created.
Respond fast
Answer 2xx within 10 seconds, then do the work. Anything else (timeouts, 4xx, 5xx) counts as a failure.
Retries
A failed delivery is tried up to 8 times in about 45 hours, retrying after 1 min, 5 min, 30 min, 2 h, 6 h, 12 h, 24 h. You can also retry any delivery by hand from the dashboard, which shows every attempt, status code and error.
Idempotent handlers
The same event can reach you twice (a retry after a slow 200). Store event.id and skip repeats — or make your handler naturally idempotent (“set order 2048 to paid” is safe to run twice).
Order
Events are not guaranteed to arrive in order. Decide from the invoice's status in the payload, not from which event came last.
Source of truth
If in doubt, GET /v1/invoices/:id. The payload is a snapshot from the moment the event was created.

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, and each of those invoices counts towards your plan's monthly allowance.

The hosted checkout page (payment_url) works on phones and desktops, offers only the coins you have a wallet for, shows your address with the exact amount and memo, 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. On the Business and Enterprise plans the "secured by" line is removed.

14 · GUIDES

Idempotency

Networks fail. If your request to create an invoice 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, such as an order id.

Idempotency-Key: order-2048        # 8–128 chars (A–Z a–z 0–9 _ - : .), unique per action
SituationResponse
First requestProcessed normally; the response is stored under the key for 24 hours.
Retry, same bodyThe stored response (same status code, same id) — nothing is created twice.
Retry, different body422 idempotency_key_reused — the key is bound to the first body.
Retry while the first is still running409 request_in_progress — wait a moment and retry.
First request
Processed normally; the response is stored under the key for 24 hours.
Retry, same body
The stored response (same status code, same id) — nothing is created twice.
Retry, different body
422 idempotency_key_reused — the key is bound to the first body.
Retry while the first is still running
409 request_in_progress — wait a moment and retry.

15 · GUIDES

Errors

Errors use conventional HTTP status codes and a small JSON body with a stable, machine-readable code. Validation errors put it in error and list the rejected inputs in fields:

JSON

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

Most other errors carry a general class in error (bad_request, unauthorized, forbidden, not_found, conflict) and the specific code in message:

JSON

HTTP/1.1 401 Unauthorized
{
  "error": "unauthorized",
  "message": "invalid_api_key"
}

So the code in the table below is message when error is one of those five classes, and error otherwise (e.g. validation_error, idempotency_key_reused, plan_invoice_limit_reached, rate_limited). Match on that code, never on other text.

StatusCodeMeaning
400validation_errorA field is missing or malformed; `fields` lists which.
400invalid_idempotency_keyIdempotency-Key must be 8–128 characters: letters, digits, _ - : .
400unknown_currency / unknown_assetNot one of the ids in Coins & networks.
400asset_not_allowedThe invoice's allowed_assets doesn't include it.
400amount_too_small / amount_too_largeBelow the coin's precision or above 1,000,000 USD.
400amount_below_minimumThe amount in the chosen coin is below that coin's smallest invoice (min_amount in GET /v1/assets).
401invalid_api_keyMissing, malformed, revoked, or a test key used against live data.
402plan_invoice_limit_reachedThis month's live-invoice allowance of your plan is used up. Upgrade in Dashboard → Plan, or wait for the next calendar month (UTC). Open invoices keep working.
402insufficient_balanceMetering only: the consumer's prepaid balance is lower than the charge. Nothing was charged; ask for a top-up.
403missing_scopeThe key was created without the scope this endpoint needs.
403ip_not_allowedThe key has an IP allowlist and this IP isn't on it.
404invoice_not_foundWrong id, or it belongs to another merchant or mode.
409no_wallets_configuredLive mode: the account has no receiving wallet yet. Set one in Dashboard → Wallets.
409wallet_not_configuredLive mode: no receiving wallet for the network of the coin you asked for (currency, or every coin in allowed_assets).
409invoice_not_pending / invoice_expiredThe invoice can no longer be changed.
409request_in_progressThe same Idempotency-Key is still being processed — retry in a moment.
422idempotency_key_reusedSame Idempotency-Key, different request body.
429rate_limitedOver 300 requests per minute on this key. Back off and retry.
503rate_unavailableNo fresh exchange rate for a non-stablecoin right now — retry shortly.
503too_many_open_invoicesToo many open invoices for the same amount on one shared address, so no unique amount is left. Retry later, or price the invoice slightly differently.
400
validation_error
A field is missing or malformed; `fields` lists which.
400
invalid_idempotency_key
Idempotency-Key must be 8–128 characters: letters, digits, _ - : .
400
unknown_currency / unknown_asset
Not one of the ids in Coins & networks.
400
asset_not_allowed
The invoice's allowed_assets doesn't include it.
400
amount_too_small / amount_too_large
Below the coin's precision or above 1,000,000 USD.
400
amount_below_minimum
The amount in the chosen coin is below that coin's smallest invoice (min_amount in GET /v1/assets).
401
invalid_api_key
Missing, malformed, revoked, or a test key used against live data.
402
plan_invoice_limit_reached
This month's live-invoice allowance of your plan is used up. Upgrade in Dashboard → Plan, or wait for the next calendar month (UTC). Open invoices keep working.
402
insufficient_balance
Metering only: the consumer's prepaid balance is lower than the charge. Nothing was charged; ask for a top-up.
403
missing_scope
The key was created without the scope this endpoint needs.
403
ip_not_allowed
The key has an IP allowlist and this IP isn't on it.
404
invoice_not_found
Wrong id, or it belongs to another merchant or mode.
409
no_wallets_configured
Live mode: the account has no receiving wallet yet. Set one in Dashboard → Wallets.
409
wallet_not_configured
Live mode: no receiving wallet for the network of the coin you asked for (currency, or every coin in allowed_assets).
409
invoice_not_pending / invoice_expired
The invoice can no longer be changed.
409
request_in_progress
The same Idempotency-Key is still being processed — retry in a moment.
422
idempotency_key_reused
Same Idempotency-Key, different request body.
429
rate_limited
Over 300 requests per minute on this key. Back off and retry.
503
rate_unavailable
No fresh exchange rate for a non-stablecoin right now — retry shortly.
503
too_many_open_invoices
Too many open invoices for the same amount on one shared address, so no unique amount is left. Retry later, or price the invoice slightly differently.

5xx and network errors: retry with exponential back-off (1 s, 2 s, 4 s…) and the same Idempotency-Key. Do not retry 402 or 409 no_wallets_configured / wallet_not_configured automatically: they need a change in the dashboard. Which codes to retry and which to fix, with a Node.js helper: API errors: retry or fix.

16 · GUIDES

Test mode & going live

Everything exists twice: test and live. Test keys, test invoices and test webhooks never touch a blockchain, need no wallet and are never counted against a plan. 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.

In test mode
InvoicesCreated the same way, with realistic addresses that nobody controls. Open the invoice in the dashboard and press Simulate payment (full or partial) — it runs the real matching code and fires your webhooks.
WalletsNot needed. Every coin is available to a test key, and each test invoice gets its own sandbox address (plus a memo on TON and XRP), so exact-amount matching does not occur in test mode.
RatesLive rates when available, otherwise a static fallback, so tests never block.
WebhooksA separate list of endpoints. Use the Send test button to check your signature code.
Invoices
Created the same way, with realistic addresses that nobody controls. Open the invoice in the dashboard and press Simulate payment (full or partial) — it runs the real matching code and fires your webhooks.
Wallets
Not needed. Every coin is available to a test key, and each test invoice gets its own sandbox address (plus a memo on TON and XRP), so exact-amount matching does not occur in test mode.
Rates
Live rates when available, otherwise a static fallback, so tests never block.
Webhooks
A separate list of endpoints. Use the Send test button to check your signature code.

Going live checklist

1Enable 2FA on your account. It is required to replace a wallet later.
2Set a receiving wallet for every network you want to accept. Check each address (or the first derived addresses of an extended public key) against your own wallet app. On TON and XRP use your own wallet, not an exchange deposit address.
3Make sure you hold the keys and a backup of every wallet you entered. easyway cannot recover coins sent to a wallet you cannot open.
4Call GET /v1/assets with your live key and confirm available: true for the coins you plan to offer.
5Create a live API key with only the scopes your server needs, and an IP allowlist if your servers have fixed IPs.
6Add a live webhook endpoint over HTTPS, verify the signature, respond 2xx fast, and make the handler idempotent.
7Fulfil only on invoice.paid, and decide your policy for invoice.underpaid, invoice.overpaid and late payments. Never trust the success_url visit.
8If you render your own payment UI, show pay_amount, pay_address and pay_memo exactly as returned.
9Subscribe an account webhook to transaction.unmatched, or check the unmatched list in the dashboard regularly.
10Handle 402 plan_invoice_limit_reached and the two 409 wallet errors in your code, and pick a plan that covers your monthly invoice count.
11Send an Idempotency-Key with every POST and retry failed requests with the same key.
12Make a real payment of a few dollars end to end and see it arrive in your wallet — the first live invoice is the best test there is.
1
Enable 2FA on your account. It is required to replace a wallet later.
2
Set a receiving wallet for every network you want to accept. Check each address (or the first derived addresses of an extended public key) against your own wallet app. On TON and XRP use your own wallet, not an exchange deposit address.
3
Make sure you hold the keys and a backup of every wallet you entered. easyway cannot recover coins sent to a wallet you cannot open.
4
Call GET /v1/assets with your live key and confirm available: true for the coins you plan to offer.
5
Create a live API key with only the scopes your server needs, and an IP allowlist if your servers have fixed IPs.
6
Add a live webhook endpoint over HTTPS, verify the signature, respond 2xx fast, and make the handler idempotent.
7
Fulfil only on invoice.paid, and decide your policy for invoice.underpaid, invoice.overpaid and late payments. Never trust the success_url visit.
8
If you render your own payment UI, show pay_amount, pay_address and pay_memo exactly as returned.
9
Subscribe an account webhook to transaction.unmatched, or check the unmatched list in the dashboard regularly.
10
Handle 402 plan_invoice_limit_reached and the two 409 wallet errors in your code, and pick a plan that covers your monthly invoice count.
11
Send an Idempotency-Key with every POST and retry failed requests with the same key.
12
Make a real payment of a few dollars end to end and see it arrive in your wallet — the first live invoice is the best test there is.

17 · GUIDES

Changelog

2026-11-19 — paid APIs, x402, mass payouts

Additive; nothing existing changed.

ChangeDetails
MeteringPOST /v1/metering/charge, POST /v1/metering/consumers, GET /v1/metering/consumers/:id, POST /v1/metering/consumers/:id/topups. See Paid APIs & x402.
x402POST /v1/x402/requirements and POST /v1/x402/verify.
New error402 insufficient_balance (metering only).
New webhook eventpayout_batch.completed: every row of a mass-payout list (dashboard) is sent, failed or skipped.
Metering
POST /v1/metering/charge, POST /v1/metering/consumers, GET /v1/metering/consumers/:id, POST /v1/metering/consumers/:id/topups. See Paid APIs & x402.
x402
POST /v1/x402/requirements and POST /v1/x402/verify.
New error
402 insufficient_balance (metering only).
New webhook event
payout_batch.completed: every row of a mass-payout list (dashboard) is sent, failed or skipped.

2026-11-18 — customers, subscriptions, refunds, reports

Additive; nothing existing changed.

ChangeDetails
CustomersPOST /v1/customers (create or update by your external_id or e-mail), GET /v1/customers, GET /v1/customers/:id (by cus_… or your id, with the customer's invoices). POST /v1/invoices accepts customer: { external_id, email, name, phone }.
SubscriptionsGET /v1/subscription-plans, POST /v1/subscriptions, GET /v1/subscriptions, GET /v1/subscriptions/:id, POST /v1/subscriptions/:id/cancel. Each period is a renewal invoice the customer pays from the subscription's pay_url; nothing is debited automatically. Renewal invoices carry metadata.subscription_id and metadata.period, so the usual invoice.paid webhook tells you a period was paid.
RefundsPOST /v1/refunds, GET /v1/refunds, GET /v1/refunds/:id. A refund is a record: you send the coins from your own wallet; it is approved and marked sent (with the transaction hash) in the dashboard.
ReportsGET /v1/reports?from=&to=&group_by=day|week|month: totals, a period series, breakdowns by coin, network, status and project, exceptions and refunds. Add format=xlsx or csv for a file.
Payment linksOne-time links, an expiry date, allowed coins and a logo (dashboard).
Customers
POST /v1/customers (create or update by your external_id or e-mail), GET /v1/customers, GET /v1/customers/:id (by cus_… or your id, with the customer's invoices). POST /v1/invoices accepts customer: { external_id, email, name, phone }.
Subscriptions
GET /v1/subscription-plans, POST /v1/subscriptions, GET /v1/subscriptions, GET /v1/subscriptions/:id, POST /v1/subscriptions/:id/cancel. Each period is a renewal invoice the customer pays from the subscription's pay_url; nothing is debited automatically. Renewal invoices carry metadata.subscription_id and metadata.period, so the usual invoice.paid webhook tells you a period was paid.
Refunds
POST /v1/refunds, GET /v1/refunds, GET /v1/refunds/:id. A refund is a record: you send the coins from your own wallet; it is approved and marked sent (with the transaction hash) in the dashboard.
Reports
GET /v1/reports?from=&to=&group_by=day|week|month: totals, a period series, breakdowns by coin, network, status and project, exceptions and refunds. Add format=xlsx or csv for a file.
Payment links
One-time links, an expiry date, allowed coins and a logo (dashboard).

2026-11-17 — non-custodial release

easyway no longer holds funds. Payments go straight to the merchant's own wallet, and plans replace the per-payment fee. Breaking changes:

ChangeDetails
Removed endpointsGET /v1/balances, POST /v1/payouts, GET /v1/payouts, GET /v1/payouts/:id. There is no balance and nothing to pay out.
Removed scopesbalances:read, payouts:read, payouts:write. Scopes are now invoices:read, invoices:write, transactions:read.
Removed webhook eventspayout.sent, payout.failed.
Wallet requiredLive invoices need a receiving wallet: new errors 409 no_wallets_configured and 409 wallet_not_configured.
pay_amount may differOn exact-amount networks pay_amount can be slightly higher than the amount requested. Always show pay_amount.
pay_addressIs now the merchant's own wallet, and on most networks the same address for every invoice.
No feefee_amount is always "0", net_amount equals received_amount, and fee_bps in GET /v1/assets is 0.
GET /v1/assetspayout_fee and min_payout removed; min_amount, available and monitor_ok added.
PlansMonthly live-invoice allowance: new error 402 plan_invoice_limit_reached; new endpoint GET /v1/account.
New invoice fieldsoverpaid_amount, late.
New eventsinvoice.created, invoice.overpaid, transaction.unmatched.
New endpointGET /v1/transactions/unmatched (scope transactions:read).
New list filtersstatus and asset on GET /v1/invoices.
Other new errors400 amount_below_minimum, 503 too_many_open_invoices.
Removed endpoints
GET /v1/balances, POST /v1/payouts, GET /v1/payouts, GET /v1/payouts/:id. There is no balance and nothing to pay out.
Removed scopes
balances:read, payouts:read, payouts:write. Scopes are now invoices:read, invoices:write, transactions:read.
Removed webhook events
payout.sent, payout.failed.
Wallet required
Live invoices need a receiving wallet: new errors 409 no_wallets_configured and 409 wallet_not_configured.
pay_amount may differ
On exact-amount networks pay_amount can be slightly higher than the amount requested. Always show pay_amount.
pay_address
Is now the merchant's own wallet, and on most networks the same address for every invoice.
No fee
fee_amount is always "0", net_amount equals received_amount, and fee_bps in GET /v1/assets is 0.
GET /v1/assets
payout_fee and min_payout removed; min_amount, available and monitor_ok added.
Plans
Monthly live-invoice allowance: new error 402 plan_invoice_limit_reached; new endpoint GET /v1/account.
New invoice fields
overpaid_amount, late.
New events
invoice.created, invoice.overpaid, transaction.unmatched.
New endpoint
GET /v1/transactions/unmatched (scope transactions:read).
New list filters
status and asset on GET /v1/invoices.
Other new errors
400 amount_below_minimum, 503 too_many_open_invoices.

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

Crypto payment API documentation | easyway