Accept Litecoin (LTC) payments on your website
Litecoin is the cheap, quick on-chain coin many customers already hold on an exchange. Here is how LTC payments work with easyway: how you connect your own wallet, the address customers pay to, how long it takes to count, and what it costs you.
How a Litecoin 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 Litecoin wallet you control (Ltub / Mtub / xpub / ypub / zpub), exported from your wallet app. For each invoice the gateway derives the next receive address of that account. Because no address is shared between invoices, the payment is matched to its order by the address alone: no memo, no tag.
An extended public key can only produce addresses; it cannot spend, and anything that looks like a private key or seed phrase is refused. The dashboard shows the first three derived addresses so you can compare them with your wallet app before saving. You can choose the address type — native SegWit (ltc1q…), wrapped SegWit or legacy; the default follows the key's prefix, and a wallet that exports a plain xpub may need the type picked by hand. An address shown to a payer that never received anything can be given out again later, which keeps your wallet app within its gap limit.
The key lets whoever holds it see that account's addresses and history, so consider a dedicated account for the gateway. Alternatively you can set a single address: every invoice then shows it and invoices are told apart by the exact amount asked. See security.
On the hosted checkout the customer sees the address and the exact LTC amount, each with a copy button, and a QR code. The QR code is a litecoin: payment link that carries the amount as well, so a wallet that scans it fills in both and the customer doesn't have to type 0.0123… by hand — the most common cause of a short payment. The LTC amount is fixed from the exchange rate when the customer picks Litecoin.
Confirmations: about 10 minutes
Litecoin blocks come about every 2.5 minutes, four times as often as Bitcoin's. The checkout shows the payment as confirming (and sends an invoice.confirming webhook) as soon as the transaction is seen; it becomes paid after 4 confirmations, about 10 minutes on average. Unconfirmed transactions never mark an invoice paid.
A confirmed output is only reported once a second, independent source shows the same transaction, output, address and amount. If the second source can't be reached the invoice waits and the check is retried — it is never skipped. The coins are in your wallet regardless; the check only decides when the invoice is marked paid.
Litecoin or Bitcoin for your store?
Both are accepted, and a customer can pick either on the same checkout. They work the same way here (an extended public key of your own wallet, a new address per invoice, no conversion), so the choice is about speed and what your customers hold. The numbers below are the gateway's own settings:
| Litecoin (LTC) | Bitcoin (BTC) | |
|---|---|---|
| Block target | 2.5 minutes | 10 minutes |
| Confirmations before paid | 4 | 2 |
| Typical wait until paid | ~10 minutes | ~20 minutes |
| Native SegWit address | ltc1q… | bc1q… |
| Extended public key | Ltub / Mtub / xpub / ypub / zpub | xpub / ypub / zpub |
| Smallest invoice | 0.008 LTC | 0.00001 BTC |
Litecoin usually reaches paid sooner, and the customer's network fee is usually a small fraction of a cent, which suits small orders. Many customers only hold Bitcoin, so offering both costs nothing extra: no fee is taken from either, and one plan covers every coin. More on Bitcoin: accept Bitcoin payments; all four UTXO coins side by side: Litecoin, Dogecoin, Dash and Bitcoin compared.
What the customer needs
A Litecoin wallet or exchange account that can send to the address shown, which almost every current one can. A few things worth knowing:
Very small outputs are ignored. A dust-sized output is not counted, and the smallest invoice is 0.008 LTC. Several transfers to the invoice address all add up, and you can set an underpayment tolerance in Settings so a payment a hair short (for example after an exchange took its withdrawal fee out of the amount) still counts as paid. Otherwise the invoice shows as underpaid and the checkout asks for the remainder; anything on top is flagged as overpaid.
MWEB. Litecoin's optional privacy extension (MimbleWimble Extension Blocks) uses its own ltcmweb1… addresses. The checkout never shows one, and payments made from an MWEB balance have not been tested with easyway — ask customers to pay from a regular Litecoin balance.
A late payment is still recorded. An invoice's own address keeps being watched for seven days after the invoice expires, so a transaction that confirms late is recorded on the invoice and flagged as late. It is in your wallet either way.
Price risk
LTC stays LTC: it arrives in your own Litecoin wallet with no conversion. Its value moves with the market after the customer has paid. If you'd rather be paid in dollars, offer USDT or USDC as well, or only those, with allowed_assets.
Costs and limits
| Fee taken from the payment | None — the full amount arrives in your wallet |
| Confirmations required | 4 |
| Smallest invoice | 0.008 LTC |
| Your wallet | Extended public key (Ltub / Mtub / xpub / ypub / zpub), or a single address |
| How invoices are matched | New address per invoice (extended public key); exact amount if you set a single address |
| Plan | Free: 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 Litecoin network fee for their own transfer, which is usually a small fraction of a cent. Plans and all other coins are on the pricing page.
Three ways to accept Litecoin on your website
All three end on the same hosted checkout, with the same address-per-invoice, confirmations and costs described above. Pick the one that matches how your site is built.
1. A payment link, no code. In Dashboard → Payment links, create a link with a fixed USD price, or let the customer type an amount within limits you set, and put /pay/link/pl_… behind a "Pay with crypto" button. Each visit creates its own invoice with its own address of your wallet (or its own exact amount, if you set a single address), and the customer picks Litecoin on the checkout. Links can also deliver a licence key or other text after payment, or take donations.
2. A store plugin. For WooCommerce, PrestaShop, OpenCart, Magento 2, WHMCS, Blesta and Odoo there is a plugin that creates the invoice at checkout and marks the order paid from the signed webhook. They are in beta, so place a test-mode order before you switch to live.
3. The API, for a custom checkout: below.
Integrating Litecoin payments with the API
Set your Litecoin wallet in the dashboard first. Then create a USD invoice and let the customer pick Litecoin among the coins you have a wallet for, or set currency: "LTC" to price in LTC and accept only LTC. Send the customer to the hosted checkout and fulfil the order on the signed invoice.paid webhook. The quickstart has runnable cURL, Node.js, PHP and Python, and the whole API is in OpenAPI format.
Common questions
Can I accept Litecoin without writing code? Yes: a payment link behind a button, or one of the store plugins (currently in beta). The API is only needed for a custom checkout.
Who holds the litecoin? You do. It is paid to an address of your own wallet; there is no balance at easyway and nothing to withdraw. easyway stores no private key and cannot move or recover coins, and refunds are sent by you from your own wallet. See security.
How is this different from Bitcoin? The flow is the same — an extended public key of your own wallet, one address per invoice, a second-source check before the invoice is marked paid — but blocks are faster and fees lower. See accepting Bitcoin, or Dash, which has the same block time.