Lightning invoice expired at sportsbook — act quickly.
A player watches the betting window close as a Lightning deposit appears expired in the sportsbook UI. Stakes and bankroll access can vanish in minutes, so treat this as triage rather than a mystery. Three symptom clusters deserve immediate checking: clock mismatch, invoice lifecycle issues, and network/wallet delivery problems.
Three common technical reasons cause that message:
Before requesting a new invoice, confirm whether the payment actually settled. Check the sportsbook deposit history and the wallet or node payment status for the payment hash/preimage. If a preimage was revealed (or the invoice shows settled), the funds arrived and only account reconciliation is needed.
If not settled, request a fresh invoice and attempt payment again; collect the payment hash and timestamps to aid support if problems persist.
Copy the payment hash and any node/wallet payment IDs before retrying. That information proves whether an HTLC was attempted or a preimage revealed.
Screenshots of the sportsbook deposit page, the lightning invoice (amount, expiry, payment hash), and the wallet payment screen should be saved. Note exact timestamps and any error messages or status labels.
Check the wallet's payment history and the pending payments list for the invoice's payment hash or outgoing entry. If the wallet shows a completed payment or a preimage, treat it as debited even if the sportsbook hasn't credited yet.
Do not request a replacement invoice or attempt another payment until the wallet history confirms no outgoing payment. If the wallet shows no debit after a few minutes, request a fresh invoice from the sportsbook and retry.
Collect payment hash, preimage (if available), amounts, invoice, and timestamps, then open a support ticket with the sportsbook. Allow 10–20 minutes for routing/settlement before escalating; see troubleshooting deposits that don't appear for follow-up steps.
Monitor the wallet's pending status and the sportsbook for up to 20 minutes; capture any state changes. If unresolved, escalate to both wallet support and the sportsbook with the evidence collected.
Do not send a second payment while the first is unconfirmed. Duplicate payments are the most common cause of lost funds and long disputes.
When contacting support include:
Payment hash and preimage (if shown) Exact invoice screenshot and wallet payment screenshot Precise timestamps and the amountIf a preimage appears in the wallet, treat that as final proof of settlement and highlight it to support.
Start with the wallet's error message and recent logs. Look for phrases like route not found, insufficient liquidity, HTLC locked, or local invoice expired — each points to a different problem (routing vs. invoice TTL vs. hold-invoice). If the wallet shows a payment hash or HTLC ID, note it for later reconciliation.
Route failures often mean insufficient outbound liquidity or channels with low forwarding capacity. Inspect channel balances and recent forwarding errors. If logs report repeated failures and no alternate route, try smaller split payments or temporarily rebalancing channels.
A locally expired invoice usually requires a fresh invoice from the sportsbook. Locked HTLCs (stuck in-flight) can clear after timeouts; if they persist, a wallet or node restart may release them. Avoid requesting a duplicate invoice until the wallet definitively shows no debit.
Request a fresh invoice when the wallet proves the original was not debited or shows an explicit invoice expiry; otherwise troubleshoot routing and liquidity first.
Request a new invoice only after confirming the wallet shows no debit or the sportsbook confirms expiration. If the wallet logs indicate routing or liquidity errors, fix those first to avoid repeated failures.
When an invoice is expired or ambiguous, sportsbooks need clear, verifiable evidence. Include:
Attach files rather than pasting images into chat; name each file clearly.
Most sportsbooks will verify logs, ask clarifying questions, then either credit the account, refund, or mark the payment as failed. Simple cases often resolve within a few hours; manual reconciliations typically take 24–72 hours. Complex or AML‑related reviews can take several days. Expect follow‑up requests for additional logs or confirmation of the preimage.
Preimage proves settlement. If a preimage is available, attach it immediately — it confirms the payment cleared and speeds reconciliation. If unavailable, include full wallet logs and timestamps.
If a wallet shows funds debited or HTLCs locked while the sportsbook shows an expired invoice, collect definitive artifacts before retrying. Key items and where to find them:
lncli listpayments, c‑lightning: listpays).Also capture timestamps, wallet type/version, node pubkey, invoice JSON and screenshots. For common wallet behavior, consult bitcoin wallets for sports betting and Lightning deposits.
Package these items (logs, JSON, screenshots, txid, payment_hash, preimage) and send to sportsbook support for manual reconciliation.
Preserve evidence and pause retries.
Export payment/invoice JSON and wallet logs. Do not reattempt the same invoice until support confirms; duplicate attempts complicate reconciliation.Keep outbound capacity on channels that route toward the sportsbook. Regularly rebalance channels or open a channel with a well-connected peer to avoid one-sided drains.
Use wallets that support route probing, multi-path payments (MPP), or fee bumping. Allow slightly higher fee limits for critical deposits to reduce route failures.
Request the invoice immediately before sending and avoid long TTLs; if sending is delayed more than a minute, request a new invoice. Confirm sportsbook hold‑invoice behavior and expected settlement windows.
Avoid rounding or adding dust—send the precise amount shown on the invoice. See the how to send the exact BTC amount for Lightning deposits guide for exact‑amount steps and common wallet pitfalls.
Enable MPP, keep system clock synced, and run a small test payment before large bets. Log failures and increase monitoring of channel balances to catch degrading liquidity early.
Before each deposit:
Request a fresh invoice and send promptly. Do a tiny test payment (e.g., 100 sats) to confirm routing. Keep MPP enabled and allow modest fee ceilings.Small, consistent checks remove most accidental expiries.
Not immediately. First confirm whether the original payment settled (preimage, wallet debit, or sportsbook record). If no settlement or debit is visible after a short wait, request a fresh invoice.
Response times vary; many sportsbooks acknowledge tickets within a few hours, but manual reconciliation often takes 24–72 hours. Including clear evidence speeds handling.
No. Lightning invoices are single-use and resending to an expired invoice can fail or cause ambiguous states. Avoid duplicate attempts until settlement is confirmed or support advises retrying.
Only after confirmation that the prior payment definitely failed and the sportsbook issued a new invoice. Otherwise the risk of double settlement or disputes remains.
Include payment hash/preimage, wallet logs/screenshots showing debit or lack thereof, timestamps, and any on-chain fallback TX IDs. Concise, labeled evidence reduces back-and-forth.
Prioritize confirmation over quick retries: avoid duplicate payments and supply clear evidence to speed reconciliation. If the sportsbook advises a retry, use the new invoice and keep logs for dispute resolution.
Online gambling has witnessed a dynamic shift in the landscape of payment methods, with players…
When a sportsbook accepts on‑chain BTC, it provides an address and waits for a transaction…