Crypto payments for e-commerce
Add crypto as a payment method next to cards. Your store creates one easyway invoice per order, sends the customer to a hosted payment page where they pay straight to your own wallet in any of 75 coins on 15 networks you choose to accept, and ships when a signed webhook says the order is paid.
Using WooCommerce, PrestaShop, OpenCart, Magento 2, WHMCS, Blesta or Odoo? Download the plugin for your platform: it does everything below for you.
How a crypto checkout works
At checkout your server creates an invoice for the order total and redirects the customer to its payment_url. The customer picks a coin and network there; the coin amount is fixed at that moment's rate, so a dollar price stays a dollar price while they pay. When the payment is confirmed on-chain, easyway posts invoice.paid to your webhook and the payment page shows a button back to your success_url. Your store's code never handles addresses or block confirmations; you set your receiving wallet once per network in the dashboard (Wallets) — live invoices are refused with 409 no_wallets_configured / wallet_not_configured until you do. If you show the amount yourself, show pay_amount from the invoice: on TRON, EVM chains and Solana it can be a hair above the quote (for example 129.901 USDT), because the exact amount is what tells orders paid to your one address apart.
curl https://api.easyway.cash/v1/invoices \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-10482-129.90" \
-d '{
"amount": "129.90",
"currency": "USD",
"order_id": "10482",
"description": "Order #10482",
"customer_email": "buyer@example.com",
"allowed_assets": ["USDT_TRC20", "USDT_BEP20", "USDC_ERC20"],
"success_url": "https://shop.example.com/order/10482/thanks",
"cancel_url": "https://shop.example.com/cart",
"lifetime": 60
}'order_id is your order number (up to 128 characters); it comes back in every webhook and you can list invoices by it. allowed_assets is optional — leave it out to accept every coin you have a wallet for, or keep it to stablecoins if you do not want to hold volatile coins. lifetime is how long the invoice can be paid, from 5 to 1,440 minutes (default 60).
Order states and webhooks
Map each invoice status to an order state in your store. Decide on the status in the webhook, never on the redirect: a customer can close the tab before returning to your site.
| Invoice status | Webhook | What the store does |
|---|---|---|
| pending | — | Order waits for payment; reserve the stock |
| confirming | invoice.confirming | Show “payment received, confirming” — do not ship yet |
| paid | invoice.paid | Mark the order paid and ship, once (handlers must be idempotent) |
| underpaid | invoice.underpaid | Hold the order; the customer can send the rest from the same page |
| expired | invoice.expired | Release the stock but keep the order — a late payment can still arrive |
| cancelled | invoice.cancelled | You cancelled it (cart changed or order abandoned) |
Once a coin is chosen the invoice stays watched for a while after it expires (hours on a shared address, 7 days on a fresh Bitcoin-style address): a transfer that still arrives turns an expired invoice paid or underpaid with late: true and the normal webhook. A cancelled invoice stays cancelled: a payment to it is recorded and flagged, no webhook fires and you get an e-mail, so you can ship after all or refund it from your wallet. The underpaid and late payments guide has a handler for every case, and verifying webhook signatures shows how to check that a delivery is genuine.
When the cart changes
An invoice is for one amount. If the customer goes back and edits the cart, cancel the old invoice with POST /v1/invoices/:id/cancel — possible only while it is pending — and create a new one. Building the Idempotency-Key from the order id and the total, as above, makes a retried request return the same invoice while a new total always gets a new one. In your invoice.paid handler, compare the invoice amount with the order total before you ship, in case an old, expired invoice was paid after the cart changed.
Fees, your wallet and refunds
No fee is taken from a payment and there is no setup fee: the full amount lands in your own wallet, in the coin the customer chose, and is not converted (easyway never holds it; convert on an exchange of your choice if you want). The Free plan covers a small number of live orders a month; paid plans raise the allowance. Past it, invoice creation answers 402 plan_invoice_limit_reached. Plans and the smallest amount per coin are on the pricing page.
Crypto payments have no chargebacks, and there is no refund button. To refund an order, ask the customer for an address on the same network and send the amount from your own wallet; easyway cannot move or reverse a payment.
No developer? Use a payment link
If your store cannot call an API, create a payment link in the dashboard and paste it into the order confirmation e-mail. For files, licence keys or gift codes, a product link delivers the item after payment — see selling digital products.
Start in test mode
Test keys create invoices that never touch a blockchain. Place a test order, press Simulate payment in the dashboard and check that your store marks the order paid; simulate a smaller amount to see the underpaid path. The sandbox guide walks through it, and the crypto payment API overview and the invoice reference list every field.