Controlled beta checkout starts from a server-created booking draft.
Syviora is currently using a mock Midtrans-style provider for beta validation. This flow checks booking state, voucher handoff, and support recovery without collecting real payment.
Continue from an experience detail, booking draft, or trip record.
Instant-book products create a draft first, then request a simulated checkout session from the Syviora API. In controlled beta, the returned payment URL is for mock validation and must not be treated as real payment capture.
Shown only inside the simulated beta checkout; it does not create a real charge.
Wallet-style options may appear in the beta flow for UX validation only.
Virtual-account instructions in beta are generated by the mock provider route.
Card details are never collected directly by Syviora web surfaces.
Syviora keeps booking amount, status, guest retrieval token, and mock provider session creation on the backend. A standalone checkout form would drift from the beta flow and could imply real payment methods that are not enabled yet.