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.
Payment URI
In brief Text, often encoded as a QR code, that requests a payment but does not send coins or prove the recipient's identity.
Structured request text, often inside a QR code, containing a destination and optional payment fields. Many Litecoin requests use the litecoin: scheme. Bitcoin's older BIP21 format provides background, but supported addresses, amounts and parameters depend on the actual Litecoin wallet.
For example The placeholder litecoin:ADDRESS?amount=0.1 requests 0.1 LTC; it does not send coins or prove that the named recipient controls the address.
Common mistake Assuming a QR code authenticates a merchant or that every wallet interprets optional fields and expiry information the same way.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
Address
In brief An encoded payment destination whose network, owner and wallet compatibility still need checking.
An encoded destination for a payment. Common transparent Litecoin addresses begin with L, M or ltc1; MWEB uses a different address format. An address is not a bank account or proof of identity. Check network and wallet compatibility before sending.
For example To receive LTC, copy a Litecoin receiving address from your wallet and check it against the address shown to the sender.
Common mistake A valid-looking address does not prove that it belongs to the intended person or uses the network the sender selected.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
Bech32
In brief An error-detecting address format for Litecoin's version-0 SegWit addresses, distinct from Bech32m for later versions.
An address encoding with an error-detecting checksum. Litecoin's native witness-version-0 addresses use Bech32 and begin ltc1q on mainnet. Later witness versions use the related Bech32m encoding. A valid checksum does not identify the owner or guarantee wallet support.
For example A wallet can recognize an ltc1q address while an older sending service still refuses that format.
Common mistake Treating every ltc1 address as the same script type or assuming a valid address guarantees that a service will credit the payment.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
MWEB
In brief Litecoin's optional layer that conceals amounts inside it, while base-chain and boundary activity can still reveal information.
Mimblewimble Extension Blocks, activated on Litecoin in May 2022. MWEB conceals amounts inside the extension layer; the base chain and boundary transfers can reveal information. Use maintained software and review the 2026 security postmortem.
For example An MWEB transfer uses compatible software and a different address format from an ordinary transparent Litecoin transfer.
Common mistake Assuming every LTC wallet or exchange accepts MWEB addresses, or that optional privacy removes all possible information leaks.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
Litoshi
In brief An informal name for 0.00000001 LTC, the smallest Litecoin unit, with 100,000,000 in one LTC.
An informal name for the smallest Litecoin unit: 0.00000001 LTC. One LTC contains 100,000,000 litoshis. Some software uses the inherited label satoshi, so always check which coin and unit a screen means.
For example 10,000 litoshis equal 0.0001 LTC; 1 litoshi equals 0.00000001 LTC.
Common mistake Confusing a fee quoted per virtual byte with that many litoshis for the whole transaction.
Full glossary entryOptional: what would make this clearer?
Choose one reason, or leave without answering.
Read the request
Decoded request
| Parameter | Value |
|---|
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.
Comparison result
Matching fields only establish agreement between these two requests. Verify the recipient separately through a trusted channel.
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?
Does a valid Litecoin address checksum prove who owns the address?
Why does the inspector flag unknown required parameters or extra decimals?
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.