Small UX note for canvas-style apps like this: the open-amount invoice pattern keeps confusing first-time Lightning users (paying 1 sat instead of 2300). A fix that works well elsewhere is generating an exact-amount invoice per purchase and embedding the order id in the invoice memo/description hash, so the wallet prefills everything and verification is automatic on settle. More invoices to manage server-side, but it removes the two biggest support tickets: wrong amounts and missing order ids.
Small UX note for canvas-style apps like this: the open-amount invoice pattern keeps confusing first-time Lightning users (paying 1 sat instead of 2300). A fix that works well elsewhere is generating an exact-amount invoice per purchase and embedding the order id in the invoice memo/description hash, so the wallet prefills everything and verification is automatic on settle. More invoices to manage server-side, but it removes the two biggest support tickets: wrong amounts and missing order ids.