May I drop few suggestions, take them or leave them, up to you.

- Make it fully transactional, ensure that when payment is processed you have committed data to at least two independent locations. HODL the LN transaction until the information is stored, and visa versa.

- Have an independent transaction sweeper, that will check for any inconsistencies, and either alert you or fix it.

- Design using “crash only” mindset, expect that the process may just crash at any point during the whole operation and stay incomplete or self-recover

- Don’t rely on browser storage, ever, things do and will go wrong

- Backup everything

🐶🐾🫡🫂

Reply to this note

Please Login to reply.

Discussion

Thank you so much for your suggestion! I really have to design it for the worst possible scenario. We developers often forget that people may not treat warnings seriously or follow the exact path. I have to make it in a way so that even if the user completely closes the payment window after making the payment, the seller should still receive the order. Your suggestions will really help, and I will release a more improved version soon.

🐶🐾🫡🫂