Litecoin.watch · Research & practical tools

Litecoin payment request & reconciliation

Create a payment request, reconcile one invoice or a batch of CSV records, and keep a clear record of exceptions.

Inspect an existing payment URI or QR image →

Your inputs stay in this page. It does not connect a wallet, send funds, watch an address or certify payment. A generated request is not proof that you own its receiving address.

1. Create a payment request

2. Reconcile an invoice

3. Reconcile a batch from CSV

Match public Litecoin receiving outputs to invoices, including multiple payments against one invoice. Files are read in your browser. They are not uploaded, saved in browser storage or checked against the blockchain.

CSV columns and matching rules

File	Required columns	Optional columns
Invoices	`invoice_id, address, amount_ltc, required_confirmations`	`expires_utc`
Receipts	`txid, vout, address, amount_ltc, confirmations`	`invoice_id, reported_received_utc`

Use UTF-8 CSV, comma or semicolon separators, plain LTC amounts with a decimal point and up to eight decimal places. Each file supports 5,000 data rows and 2 MiB. Timestamps use UTC, for example 2026-09-27T12:30:00Z. Leave optional timestamps empty if unknown. A receipt file containing only its header records no payments for any invoice.

Each invoice needs a unique reference. A fresh address per invoice allows automatic matching. If an address appears on multiple invoices, every receipt needs its exact invoice_id. A receipt's address must match even when a reference is supplied. Use the amount in the receiving output, not the transaction total; vout is its zero-based output index.

The same txid + vout is counted once. Identical duplicate rows are ignored and listed. Conflicting copies are all excluded and affected invoices are flagged for review. Supply one consistent export, not successive confirmation snapshots of the same output. Separate outputs can form a top-up.

Confirmed LTC sums only outputs meeting that invoice's confirmation requirement. Expiry checks use your reported receipt time; this is not independently observed arrival time. Missing times remain unknown. Addresses beginning with 3 and private MWEB addresses are unsupported. CSV exports escape formula-like text for spreadsheet safety; review your spreadsheet import settings before use.

Imported payment reconciliation

Amounts in LTC. Confirmed means the count reported in the receipt CSV meets the invoice requirement.
Invoice	Due	Recorded	Confirmed	Amount	Next step

Receipt line	Output reference	Issue

An arithmetic match does not certify settlement. Review excluded records, missing receipts, late payments and your acceptance policy before closing an order. A later reorganization can change confirmations.

Handle the exception before closing the order

Situation	Record and resolve
Underpayment	Record the shortfall and your agreed policy. If requesting a top-up, identify both transactions and verify their actual outputs.
Overpayment	Record the excess. Verify a refund destination through an authenticated customer channel; a transaction's input address is not automatically the customer's refund address.
Payment after quote expiry	Apply the policy agreed before payment. Do not silently replace the original exchange rate.
Exact amount, insufficient confirmations	Keep network confirmation status separate from amount matching and your order acceptance decision.
Refund	Record the basis (LTC amount or fiat value), fees, date, verified destination and refund transaction ID.

Model a refund Worked examples and refund policies Check a public transaction Refund record template · CSV

A complete worked example

An invoice requests 1.50000000 LTC. You verify that the output to your receiving address is 1.49000000 LTC. The shortfall is 0.01000000 LTC. Confirmations do not remove that shortfall. The same transaction may also contain change belonging to the sender; that output does not pay your invoice.

If your agreed policy accepts the shortfall, record that decision. If you require the balance, keep the original payment and the top-up in the same order record. Use the refund calculator when a return depends on a fiat amount or a different exchange rate.