Accepting Litecoin as a merchant: invoices, fees and refunds
Plan a complete LTC checkout with current fee references, invoice states, exception handling, refunds and reconciliation.
Reviewed 18 September 2026. Provider terms can change; confirm current availability and pricing for your business before integrating.
Accepting Litecoin means defining what counts as payment, how an order is fulfilled, where funds are held and how exceptions are handled. A displayed address is only the beginning of a merchant workflow.
The former provider table used outdated blanket fee claims. This revision separates network costs, processing charges and operational responsibilities.
Select an operating model
| Model | Main benefit | Responsibility retained by the merchant |
|---|---|---|
| Direct wallet payments | Control over receipt and custody | Invoices, reconciliation, confirmation policy and refunds |
| Self-hosted payment software | Automated invoicing under your operation | Hosting, updates, monitoring and secure configuration |
| Managed processor | Integration and settlement services | Provider due diligence, contractual terms and reconciliation |
BTCPay Server's altcoin documentation lists Litecoin among community-supported integrations. That does not mean every BTCPay deployment includes LTC automatically or that every altcoin feature has identical maintenance coverage. Check the actual deployment and support arrangement.
BitPay's pricing page shows volume-based processing tiers. At this review, its advertised rates are 2% plus $0.25 below $500,000 monthly transaction value, 1.5% plus $0.25 from $500,000 to below $1 million, and 1% plus $0.25 at $1 million or more. Check contract-specific terms and additional costs. A universal “BitPay charges 1%” statement is misleading.
Price the invoice and define its expiry
Record the order's pricing currency, LTC amount, exchange-rate source and quote expiry. Display the exact supported payment route. If the customer pays after expiry, your system needs a documented response rather than silently accepting an obsolete conversion rate.
For a hypothetical $100 invoice, a 2% plus $0.25 processing charge is $2.25, leaving $97.75 before other costs. A low blockchain fee does not erase the processor charge, conversion spread or settlement costs.
Use the LTC calculator as a reference during planning. An invoice should use the rate and validity rules of the actual integration, not an unrelated public converter's latest display.
Implement a clear payment state machine
| State | Meaning | Appropriate action |
|---|---|---|
| Created | Invoice exists but payment is not confirmed | Show instructions and expiry |
| Detected | Transaction observed | Continue checking; do not confuse detection with settlement |
| Confirmed or settled | Your defined acceptance conditions are met | Fulfil once, according to the business policy |
| Underpaid, overpaid or late | Amount or timing differs from the invoice | Route to a documented exception process |
| Refunded | An authorized refund was executed | Preserve refund reference and accounting link |
Do not fulfil an order based only on a customer-facing browser redirect. A robust integration verifies the invoice state through the provider's authenticated interface or its own validated chain data. Process repeated notifications idempotently so one payment cannot trigger duplicate fulfilment.
Follow the provider's documented notification verification mechanism. Do not assume that all providers use the same webhook-signature format.
Make refunds safe and understandable
A transaction input address is not necessarily a suitable refund destination. It may belong to an exchange or be part of a multi-input payment. Obtain and verify a supported refund destination through the authenticated customer process.
State whether refunds are denominated in the original pricing currency or the original LTC amount, and explain who bears applicable network or processing costs. Local consumer rules and your contract may constrain that policy.
BitPay's fee documentation distinguishes processing charges and refund network fees. Other providers may use different arrangements.
Test the exceptions before going live
Use a provider sandbox where available, then a controlled small live payment when appropriate. Test an ordinary payment, an expired invoice, underpayment, repeated notifications, failed callbacks and the refund process. Record expected and actual states.
Also test recovery after a server restart. Confirm that a paid order cannot be fulfilled twice and that staff can reconcile a transaction without needing to handle private keys.
Do not assume MWEB support because the processor lists Litecoin. Check the specific accepted address formats and route instructions.
Keep records suitable for reconciliation
Preserve the order ID, invoice ID, LTC amount, relevant timestamps, transaction ID, pricing-currency value, exchange-rate source, fees, settlement details and refunds. Your jurisdiction determines the accounting and tax treatment; a payment-processing dashboard is not a universal tax calculation.
For cross-border customers, compare the complete path using the LTC versus XRP payment guide. Network speed is one component of the customer's experience.
Frequently asked questions
Is self-hosted payment processing free?
The software may have no processing charge, but hosting, maintenance, conversion and network costs still exist.
Should an unconfirmed transaction trigger fulfilment?
That depends on a deliberately chosen risk policy. Detection alone should not be confused with confirmation or guaranteed settlement.
Can I refund to the address shown as the sender?
Do not assume that address is appropriate. Obtain and verify the customer's supported refund destination.
Track Litecoin in real time
Rates for 30+ currencies. Check each tool for its latest source timestamp.
Open dashboard