LITECOIN PAYMENT SUPPORT: SIX TYPED TEMPLATES Version 2026-10-11-v1. Original teaching resource from Litecoin.watch. Use only inside the provider's verified support channel. Print or edit locally. Replace brackets, keep unknown fields marked UNKNOWN, and delete irrelevant lines. No recovery words, private key, password, 2FA code, wallet backup, descriptor or xpub. Never publish a completed ticket: case/account/order references stay private. Public-chain fields can link your identity to payment history. These templates do not authenticate a provider or guarantee recovery. TEMPLATE 1: Withdrawal request without a network transaction ID Subject: LTC withdrawal request - please confirm broadcast status Asset and requested network [TEXT]: Request date and time [ISO 8601 WITH TIMEZONE]: Sending app and version [TEXT]: Withdrawal request reference [PRIVATE TEXT]: Displayed request status [EXACT TEXT]: Requested LTC amount [DECIMAL, UP TO 8 PLACES]: Displayed service charge and deduction rule [TEXT OR UNKNOWN]: Actual network transaction ID: NOT PROVIDED Question: Was this request broadcast, or is it still awaiting a service step? If broadcast, please provide the network transaction ID and network used. -------------------------------------------------------------------- TEMPLATE 2: Inconclusive lookup or visible unconfirmed transaction Subject: LTC transaction observation - please confirm the next step Asset and network [TEXT]: Transaction ID [PUBLIC-CHAIN TEXT, PRIVATE CHANNEL]: Sending app and version [TEXT]: Lookup source [URL]: Lookup time [ISO 8601 WITH TIMEZONE]: Lookup result [EXACT TEXT: UNAVAILABLE / NOT FOUND / RECORD FOUND]: Confirmations [INTEGER OR UNKNOWN]: Intended destination match [YES / NO / UNKNOWN]: Recipient output index and LTC [INTEGER + DECIMAL OR UNKNOWN]: Withdrawal reference if needed [PRIVATE TEXT]: Question: Please confirm identifier, network and broadcast state, and the documented pending-transaction procedure. I have not sent a duplicate payment. -------------------------------------------------------------------- TEMPLATE 3: Confirmed matching output with account credit pending Subject: Confirmed LTC output - receiving account credit remains pending Asset and network [TEXT]: Transaction ID [PUBLIC-CHAIN TEXT, PRIVATE CHANNEL]: Relevant output index [NONNEGATIVE INTEGER]: Relevant full destination [PUBLIC-CHAIN TEXT, PRIVATE CHANNEL]: Recipient amount LTC [DECIMAL, UP TO 8 PLACES]: Source and lookup time [URL + ISO 8601 WITH TIMEZONE]: Active-chain confirmations at that lookup [INTEGER]: Receiving instructions saved at [ISO 8601 WITH TIMEZONE]: Destination compared against saved instructions [YES / NO / UNKNOWN]: Current minimum and confirmation requirement [SOURCE + TEXT OR UNKNOWN]: Receiving account status and check time [PRIVATE TEXT + TIME]: Order/deposit reference required for this case [PRIVATE TEXT OR OMIT]: Question: Which stated deposit requirement or internal review remains incomplete? Please identify the next required action through this authenticated case. -------------------------------------------------------------------- TEMPLATE 4: Invoice amount and delivered output differ Subject: LTC invoice shortfall - request for reconciliation rule Invoice reference [PRIVATE TEXT]: Required amount LTC [DECIMAL, UP TO 8 PLACES]: Invoice address and validity period [PRIVATE CONTEXT + PUBLIC-CHAIN TEXT]: Transaction ID and relevant output index [PUBLIC-CHAIN TEXT + INTEGER]: Delivered recipient amount LTC [DECIMAL, UP TO 8 PLACES]: Source and lookup time [URL + ISO 8601 WITH TIMEZONE]: Gross withdrawal request LTC [DECIMAL OR UNKNOWN]: Displayed service charge LTC and deduction rule [DECIMAL + TEXT OR UNKNOWN]: Network fee LTC [DECIMAL OR UNKNOWN; SEPARATE FROM SERVICE CHARGE]: Question: Which amount did your system credit, and what is the accepted underpayment, top-up or refund procedure? I have not reused an expired invoice. -------------------------------------------------------------------- TEMPLATE 5: Wrong network or different destination Subject: Asset/network/destination mismatch - request for documented policy Sending asset and actual network [EXACT TEXT]: Requested receiving asset and network [EXACT TEXT]: Actual transaction ID on the actual network [PUBLIC-CHAIN TEXT OR UNKNOWN]: Actual destination [PUBLIC-CHAIN TEXT, PRIVATE CHANNEL]: Destination in saved receiving instructions [PUBLIC-CHAIN TEXT, PRIVATE CHANNEL]: Recipient output amount if visible [DECIMAL OR UNKNOWN]: Instruction and observation times [ISO 8601 WITH TIMEZONE]: Relevant private request/invoice reference [PRIVATE TEXT OR OMIT]: Mismatch [NETWORK / ADDRESS / BOTH / UNKNOWN]: Question: Does your service control the relevant destination or offer a documented procedure for this exact asset and network? Please state the eligibility, limits and applicable charges. I understand recovery is not assured. Do not supply any seed, key, wallet file or signing material with this message. -------------------------------------------------------------------- TEMPLATE 6: Security exposure, without disclosing the secret again Subject: Security incident - request for official account procedure Product involved [CUSTODIAL ACCOUNT / SELF-CUSTODY WALLET / UNKNOWN]: Approximate incident time [ISO 8601 WITH TIMEZONE]: Incident category [CREDENTIAL DISCLOSURE / SIGNING-MATERIAL DISCLOSURE / REMOTE ACCESS / SUSPICIOUS MESSAGE / UNKNOWN]: Actions already taken through official controls [TEXT, NO SECRETS]: Verified case reference if one already exists [PRIVATE TEXT OR OMIT]: Question: Which official security procedure applies to this product? This ticket contains no disclosed secret and no wallet backup or descriptor. For self-custody exposure, I understand that support cannot revoke a private key and that securing funds may require new uncompromised signing material. --------------------------------------------------------------------