Dotted-underlined terms open a quick definition. Close it to keep reading.
Two payment requests arrive for the same invoice. Both say Demo invoice 1042. One is the reference you expected. The other could be a legitimate correction or a mistake. Can you tell what changed before opening either in a ?
Try the comparison
Demo only. Do not send funds. The requests use public test addresses with mainnet formatting. You can complete the exercise entirely in the browser.
Look at the after litecoin:, the amount, and the label in each request. Which two fields differ? The %20 in the label represents a space.
Select Compare requests to check your answer. Read the full destinations in the comparison result.
What changed?
Destination: A starts with ltc1qhdh and B with ltc1qa9d. Both share the ltc1q prefix, but they are different addresses. In a real payment, compare the full destination.
Requested amount: A asks for 0.25 LTC and B asks for 0.30 LTC. B requests 0.05 LTC more.
Label: Both decode to Demo invoice 1042. The label is text supplied in the request and can be copied from one request to another.
For a second round, change B’s amount to 0.25 and compare again. The amount now matches, but the destination still differs. Finally, copy the complete text from A into B and compare again. The fields agree. That tells you what the two requests contain. It gives you no independent evidence about who controls the address or whether a payment is due.
What to do when a real request changes
Find a trusted reference. Start from the original order in an account you access independently, or use a known contact method for the recipient. A second copy of the same forwarded request provides no independent check.
Ask about any change before paying. Confirm the full destination, Litecoin network, requested LTC amount and invoice reference with that source. A changed destination could be legitimate. Wait until you have confirmed which instructions apply.
Check what your wallet will send. Before approving a real payment, check the destination and amount in the wallet’s screen against the verified instructions. If the request leaves the amount blank, confirm what is due instead of treating the blank as zero.
The inspector compares the information it can read from the requests. It processes the input in your browser and sends no payment. An address can pass a format check without telling you who controls it. If the inspector flags unsupported or unreadable input, get fresh instructions from your trusted source before relying on a comparison.
How a payment URI carries these fields
A is a text string a QR code can carry. In this example, the string includes a destination, an amount in LTC and a label. The Litecoin Core URI parser shows how those fields are read. The original Bitcoin URI specification gives background for this format. Wallet support can vary. Our payment QR study shows examples of what a QR code can tell a wallet.
Wallet
In brief Software or a device for managing wallet keys and payments, though a watch-only setup cannot sign on its own.
Software or a device that manages keys and helps you receive and send Litecoin. Coins are recorded on the blockchain. A watch-only wallet can show addresses and transactions without holding the keys needed to spend.
For example One wallet can generate several receiving addresses and still show them as a single combined balance.
Common mistake Thinking coins live inside the app, or that seeing a balance proves that the wallet can sign a spend.
In brief A peer-to-peer cryptocurrency with its own Scrypt proof-of-work network and a maximum issuance of 84 million LTC.
A peer-to-peer cryptocurrency launched in 2011. Litecoin uses Scrypt proof of work, targets an average 2.5-minute block interval and has an issuance schedule capped at 84 million LTC. Individual block times and payment acceptance times vary.
For example Sending 0.1 LTC on Litecoin transfers a fraction of one coin; you do not need to buy a whole LTC first.
Common mistake Assuming a token with LTC in its name on another network is automatically native Litecoin.
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.
In brief A transaction gains confirmations as blocks build on its inclusion, but those confirmations can fall if chain history changes.
A transaction receives its first confirmation when included in a block in the accepted chain. Each block then built on top adds another. A chain reorganization can reduce or remove the count. The recipient decides how many confirmations it requires. Litecoin targets an average 2.5-minute block interval; individual blocks can arrive sooner or much later.
For example A transaction in the latest accepted block has one confirmation; the next block raises that count to two.
Common mistake Confusing a wallet's sent message, a TXID or mempool visibility with the first confirmation.
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.
Content review recorded: 2026-11-03. The review record does not identify a separate independent reviewer. An edited date above records an edit, not a new fact-check. AI-assisted editing or new artwork alone does not complete a source review.
