Can you pass a software engineering interview question? Let's see if you can get it.

Can you pass a software engineering interview question? Let's see if you can get it. This is more focused on the payment feature of your applications. Let's see if you can vibe code your way through this. So you decided to sell a vibe coded slash day trading course and you're doing the processing for payments. Unfortunately, you have to process the payments asynchronously. You can't just take money out of people's bank account without some validation. You decide to make the architectural decision to use a message broker. If you don't know what that is, I would highly recommend you look that up. With this message broker, you have workers that take the payments and process it, validate it, and do some other things needed for compliance. The first question is, when someone clicks the pay button, what do you display? Payment successful or payment received? Tell me why. Next question is, you have a problem where people are clicking the pay button twice, like they're double clicking for some reason. Is there any front end UI UX decisions that you can make to stop users from clicking the pay button twice? So, what is it? Last question, I think the most important question. So you remember we did this architecture of using a message broker. So now I go on your website and I click pay for your how to vibe code 101 course. This payment gets put into the message broker, but some for some reason, some network issues happen and I don't get a confirmation email. I go back on your website and say like, okay, I didn't get the course, so I'll pay for it again. I click the pay button for the same course and it gets added to your message broker. How do you prevent your message broker from processing two of the same orders?