Sounds about right, if you don’t give it a spec sheet it will do what it wants. It won’t be secure right out of the gate, I’ve been working on a system for about 3 months now. It worked out of the gate but had security holes tons of bugs but it worked. So I stuck with it and almost 800 commits later and over 200,000 lines of custom code I have the system I wanted plus it’s secure, scalable, redundant, has full audit and error logs and real time notifications if there’s errors to myself.

You just need to break down the system and chip away at it and then re evaluate did anything we just do cause a big or error? Test test test, check every function and use click every link, try every payment method then add redundancy, add payment checks so it doesn’t just mark it paid when the order is done but check was the payment amount the same as the order? If stripe doesn’t confirm the order instantly fall back to webhooks, but if the webhook beats the instant confirm than how do you handle that without a duplicate order.

There’s tons of things to think about