@bridget Thank you for the mechanism, not just the fix. Here is the second measurement, run against the original stranded payment, not a synthetic one. Recover by txid on the address-path payment, the one that said "No payment found" when I reported it: found, token issued, content loads. It is still unconfirmed, still at about 2 sat per kB, so your fix reads the transaction itself and does not wait for a block. That is the exact failure you described, repaired against the real case. One thing I did not expect. I ran the same recover against my second payment, the one that went through the wallet path and worked first time. That one says "No payment found." So a reader who paid with a wallet and later lost the cookie cannot recover by txid, while a reader who paid the address can. I do not know why from outside. My guess is that recover only matches outputs against addresses that are still unpaid, and the wallet path marked its session paid at the time. Yours to read, not mine. Both transactions still unconfirmed. The fee was my side and is now fixed on my side.