Skip to content

Inspect a Litecoin payment QR

Read the actual destination, amount and URI parameters before opening a payment request in a wallet. Images and text stay in this browser.

Read the request

Compare two payment requests

PNG, JPEG or WebP, up to 10 MiB and 16 megapixels. Files are decoded locally. No camera or wallet connection.

Compare two payment requests

Use a request from a trusted source as A and the request you received as B. Compare the full destination and requested amount before opening either in a wallet.

Request A

Request B

Images are read in this browser. PNG, JPEG or WebP, up to 10 MiB and 16 megapixels. Demo requests are for practice only. Do not send funds to them.

What this inspection establishes

An address checksum detects some copying errors. It does not prove who controls the address. Compare the full address with authenticated payment instructions. The amount is in LTC, not USD or another fiat currency. No payment is sent and no URI is opened automatically.

This inspector accepts public Litecoin mainnet L, M, ltc1q and ltc1p addresses supported by our address validator. Ambiguous 3-prefixed and private MWEB requests are outside its scope. Duplicate parameters, unknown required parameters, negative amounts, scientific notation and more than eight decimals are flagged rather than normalized into a payable request.

Optional time or expiry fields are displayed, without enforcing a wallet deadline. Wallet parsers differ; a syntax check here does not establish wallet behavior. Our original QR study publishes exact cases and results. The Electrum and Cake parser comparison adds pinned wallet-source evidence without claiming complete-app validation. BIP 21’s original URI rules provide background for this older, widely used request format; it is a Bitcoin specification, not a Litecoin wallet compatibility guarantee.

Frequently asked questions

Does uploading a Litecoin payment QR image send it to a server?
No. Both pasted payment URIs and QR images (PNG, JPEG or WebP) are decoded locally in your browser using JavaScript. No wallet connection, server upload or automatic payment is triggered.
Does a valid Litecoin address checksum prove who owns the address?
No. Checksum validation catches some typing errors, not impersonation or tampered invoices. Always confirm the full destination address and LTC amount against an authenticated channel before sending.
Why does the inspector flag unknown required parameters or extra decimals?
Under BIP-21 URI conventions, required parameters (req-*) or non-standard amounts with more than eight decimal places can be rejected or interpreted differently by wallets. Comparing two URIs side by side helps verify exact agreement before paying.