Restaurant Backend, Payment, AR Optimization

My restaurant ordering platform is already live with core features coded, yet it still needs a round of deep polishing before it can comfortably scale. Here is what remains: • Payment flow Customers must be able to pay the restaurant directly inside the app or website. The underlying codebase is ready for a gateway (Stripe Connect, Square API, or similar), but I need you to wire it end-to-end, handle web-hooks, receipts, and edge-case errors so funds settle straight into each restaurant’s account. • Kitchen order experience Orders appear on tablet-based kitchen display screens (iOS and Android). I want the ticket layout, bump/recall actions, and sound/visual alerts tuned the way an experienced line cook expects them. Any latency, mis-sorting, or unclear status colours should be fixed. • 3D & AR assets Menu items are stored as .glb files for augmented-reality previews. Optimise load times, ensure correct scene lighting, and test on mainstream AR viewers so models pop up crisply in customers’ kitchens. • Bug hunting & UX polish Run through the whole web + mobile stack, squash lingering bugs, tighten API calls, and reduce page/app launch time. I’d like every click path to feel effortless for both diners and staff. • Final walkthrough Once the code is stable, walk me through deployment scripts, environment variables, and payment-ops reports so I can run the system confidently without further hand-holding. Acceptance is simple: payments clear to restaurant accounts without manual intervention, tickets fire correctly on tablets under service load, glb models render in AR with <2 s load, and no critical errors show in the log after a full dinner-rush simulation.