Sell access to a tour with pay-per-view only if you are using the SaaS payment workflow, not the basic Core viewer. Core creates and publishes tours; SaaS adds customer accounts, plans, credits, and payments. That distinction matters because a tour ticket is an access-control and billing setup, not a general replacement for your own customer platform. This article is based on documentation review and source inspection dated 2026-11-12; no hands-on transaction tests were performed.
As planning advice, decide whether you are selling a single paid access right or a bundled service that includes the tour plus another deliverable. If you are building the tour itself, the normal flow is to create the tour in how to create a virtual tour, add rooms in How to create a room panorama, connect movement points in How to connect rooms in a tour, and optionally enrich scenes with POIs from How to add contents POIs into a room. Pay-per-view sits on top of that structure; it does not replace the tour content model.
What the pay-per-view setup is for
The documented payment area is in the SaaS section, where you configure the provider and the release rules that control access. The source notes Stripe, PayPal, and Paddle as payment providers, with sandbox and live setup treated separately. That means you should first confirm your provider account is ready, then configure the tour release, price, and access conditions in the SaaS payment settings. If you are deciding between a subscription plan and a paid access model, review the plan structure in How to create subscription plans before you set payment behavior.
Do not assume every gateway supports every checkout flow. The documentation does not promise universal coverage, so treat payment-method availability as provider-specific. Also keep merchant fees, taxes, and refund policy outside the software setup; those are business rules you must define separately.
Configure access before you ask for payment
The safest sequence is: build the tour, publish the visitor link, then layer access controls on top. The publish workflow already provides a permanent visitor link and embed code, and the access settings determine who can reach that public viewer. Use How to publish a tour to understand the public link and available protection options, then apply How to protect a tour if you need gated access. Protection is not the same as draft status: the documentation says tours already have a visitor link, while status, protection, and scheduling affect access.
If you need lead capture as part of the purchase path, separate that from payment itself. The main form and POI form features collect data, while pay-per-view controls access. Review virtual tour lead generation and How to add forms into the tour main form POIs form to keep those purposes distinct. A form submission is not a payment receipt, and a payment approval is not proof that a form delivered successfully.
Test sandbox and live behavior separately
Before you switch on live payment, verify the provider in sandbox mode and check the access result from the visitor side. The brief specifically calls for testing access before and after purchase, plus sandbox failure paths, but those checks should be done by the operator in their own environment. In practical terms, confirm that an unpaid visitor reaches the expected gate, that a successful sandbox payment opens access, and that a failed sandbox payment does not unlock the tour. Then repeat the same checks after live credentials are enabled. Do not claim a transaction was completed unless you actually performed one.
Keep the editor and visitor roles separate while you test. Branding, editor access, and customer access are different layers in the product, and cloud subscriptions provide the subscriber with their own editor account rather than acting as a substitute for your own SaaS business platform. If you need account-level understanding, the product overview in Simple Virtual Tour and the SaaS area in white label virtual tour software help frame the difference between software ownership and customer-facing service delivery.
Use the right tour structure for a paid experience
A paid tour works best when the content is already organized for the visitor. Rooms are the base unit; on a floorplan, assign room points rather than treating them as generic POIs. If you want a map-style overview, use How to add floorplans and the explanation in what is a floor plan virtual tour. For a richer guided experience, you can combine room navigation with markers, POIs, and branded presentation. The branding workflow is documented in How to add logo to the tour, which is useful when the tour is part of a paid service.
If you are tempted to turn the tour into a store, remember that the documented shop feature is separate and uses external commerce integrations. The tour shop setup in How to set up the shop into the tour is different from SaaS pay-per-view. Use the shop feature when you need product presentation inside the tour; use SaaS payments when you need access control for viewing rights.
Practical operator checklist
- Create the tour and confirm the public visitor link exists.
- Set the payment provider in SaaS settings and keep sandbox/live credentials separate.
- Define the access rule, price, and release behavior for the paid tour.
- Test unpaid access, successful sandbox access, and sandbox failure behavior.
- Review refund and tax policy outside the software before launch.
- Check the live flow again after switching from sandbox to production credentials.
For a broader business context, compare this setup with how to sell virtual tours and how to make money with virtual tours. Those guides help you decide whether pay-per-view is the right commercial model, while this article focuses on the software-side configuration and verification steps.
If your paid experience depends on forms, maps, or customer workflow, plan each part separately: content in the tour, access in SaaS, and business policy outside the application. That separation keeps the setup understandable and reduces the risk of treating a payment provider, a lead form, and a published visitor link as the same thing.