Could use CLINK, it fetches the invoice over nostr, then will fire a nostr native receipt once paid. Also doesn't require your Lightning node or middleware to it to have static http endpoints / jwt etc. Lightning.Pub will also allow your node to fire callbacks to something external.
99% of internet users don't have a Lightning wallet
This is surprisingly not true, CashApp alone is a Lightning wallet on 100M phones in just the US alone... a badge to remind users of that option may help conversion. You could use the browser time zone to change the badge based on geo to apps they are most likely to have that supports LN. Since you're selling "crypto" information, the odds of them having something that can pay a Lightning invoice is fairly high.
I considered time-bound URLs and key escrow
This could be transparent to the user, leeching from your CDN is worse than copies... your back-end just signs the url and the key lives in the users browser storage.
Could use CLINK, it fetches the invoice over nostr, then will fire a nostr native receipt once paid. Also doesn't require your Lightning node or middleware to it to have static http endpoints / jwt etc. Lightning.Pub will also allow your node to fire callbacks to something external.
This is surprisingly not true, CashApp alone is a Lightning wallet on 100M phones in just the US alone... a badge to remind users of that option may help conversion. You could use the browser time zone to change the badge based on geo to apps they are most likely to have that supports LN. Since you're selling "crypto" information, the odds of them having something that can pay a Lightning invoice is fairly high.
This could be transparent to the user, leeching from your CDN is worse than copies... your back-end just signs the url and the key lives in the users browser storage.