easyway
Log inGet started

Accept Bitcoin (BTC) payments

Bitcoin is still the coin most customers ask for by name. Here is how on-chain BTC payments work with easyway: how you connect your own wallet, what the payer sees, when an invoice counts as paid, and what it costs.

How a Bitcoin payment works here

easyway is non-custodial: the customer pays your own wallet, directly. On the Wallets page of the dashboard you paste the account-level extended public key of a wallet you control (xpub / ypub / zpub), exported from your wallet app. For every invoice the gateway derives the next receive address of that account, so each invoice has its own address and a payment is matched to its order by the address alone; no memo, no reference to type.

An extended public key can only produce addresses. It cannot spend, and anything that looks like a private key or a seed phrase is refused. Before you save, the dashboard shows the first three addresses it derives so you can compare them with the ones your wallet app shows. You can choose the address type — native SegWit (bc1q…), wrapped SegWit or legacy; the default follows the key's prefix. An address that was shown to a payer but never received anything can be given out again later, which keeps your wallet app within its gap limit.

Two things to know. An extended public key lets whoever holds it see that account's addresses and history, so a dedicated account for the gateway is a sensible choice. And if you would rather not share one, you can set a single address instead: all invoices then show that address and are told apart by the exact amount asked. More on the security page.

The customer picks Bitcoin on the hosted checkout and is shown the address (also as a QR code) and the exact BTC amount, with a copy button for each. The BTC amount is fixed from the exchange rate at the moment they pick the coin, and the invoice expires after its lifetime (60 minutes unless you set another) if nothing arrives.

Confirmations and what "paid" means

As soon as the transaction appears in the mempool the checkout switches to confirming and your server gets an invoice.confirming webhook. That is a heads-up only: an unconfirmed transaction can still be replaced (RBF) or double-spent. The invoice turns paid after 2 confirmations, about 20 minutes on average. The coins themselves are in your wallet from the moment the transaction confirms; the gateway only records it.

Before an invoice is marked paid, the confirmed output is checked against a second, unrelated block explorer: the watcher reads payments from one source and only reports a deep enough output once a different one shows the same transaction, output, address and amount. A single faulty data source cannot get an invoice marked paid on its own.

What the customer needs

Any Bitcoin wallet or exchange that can send on-chain to the address shown — which today is practically all of them. Wallets that only speak Lightning cannot pay; there is no Lightning invoice. Two things worth telling customers:

Send the exact amount in one go if you can. Some exchanges deduct their withdrawal fee from the amount sent; the invoice then shows as underpaid, and the checkout asks for the remainder. Several transfers to the same invoice address all count towards the invoice. You can allow a small shortfall in Settings (the underpayment tolerance) so a few satoshis short still counts as paid. Anything sent on top is flagged as overpaid and reported in overpaid_amount.

Pay a normal network fee. A transaction with a very low fee can sit unconfirmed for hours. An invoice's own address is watched for seven days after the invoice expires, so a slow payment is still recorded and flagged as late — and either way the bitcoin is in your wallet once it confirms.

Price risk

Nothing is converted: the customer's BTC arrives as BTC in your wallet. If you price in USD, the amount you receive is worth the invoice price at the moment the customer picked Bitcoin; after that the value moves with the market, up or down. If you want to avoid that, offer stablecoins such as USDT or USDC alongside or instead of Bitcoin with allowed_assets.

Costs and limits

Fee taken from the paymentNone — the full amount arrives in your wallet
Confirmations required2
Smallest invoice0.00001 BTC
Your walletExtended public key (xpub / ypub / zpub), or a single address
How invoices are matchedNew address per invoice (extended public key); exact amount if you set a single address
PlanFree: 30 live invoices a month; paid plans from $19/month

easyway earns from subscription plans, not from a cut of payments. The customer pays the Bitcoin network fee for their own transfer. Plans and every other coin and network are on the pricing page.

Integrating Bitcoin payments

Set your Bitcoin wallet in the dashboard first; without one, live invoices cannot be paid in BTC. Then create an invoice in USD and let the customer choose Bitcoin among every coin you have a wallet for, or set currency: "BTC" to price in BTC and accept only BTC. Redirect to the hosted checkout, then fulfil the order on the signed invoice.paid webhook. The quickstart has runnable code in cURL, Node.js, PHP and Python, and the full API is described in OpenAPI format.

Common questions

Who holds the bitcoin? You do. It is paid to an address of your own wallet, so there is no balance at easyway and nothing to withdraw. easyway stores no private key or seed phrase and cannot move, freeze or recover coins; keeping your wallet's keys and backups safe is your responsibility. Refunds are sent by you, from your own wallet. See security.

Can I accept other UTXO coins? Litecoin, Dogecoin and Dashwork the same way — an extended public key of your own wallet, one address per invoice, a few confirmations. See the coins and networks table.

Create free accountRead the API docsAlready have an account? Sign in
Accept bitcoin on website: BTC payment gateway | easyway