Use this guide only for an approved non-live environment that your organization can currently access. A test helps validate the displayed guest flow and its recorded result in that environment. It does not authorize a Live charge, prove a Live configuration, or establish Wallet or payout readiness.
Check the scope before testing
Confirm the displayed property, recipient, and guest entry point resolve to the same approved non-live environment. Do not infer this from a related account or from a previous test. Do not begin a test while the property is changing data mode; payments and operating changes can be paused while that transition is verified.
Run a controlled guest-flow check
Use the guest entry point and payment or test controls currently displayed for the authorized environment. The available payment methods and test behavior are configuration-dependent. Do not use real customer data, payment data, bank data, passwords, verification codes, or tokens. Do not rely on a redirect or a thank-you screen alone as final payment confirmation.
Verify the recorded result
Review the result through the currently available authorized controls in the same environment. Confirm the recorded recipient and amount only after the system has recorded the outcome. A Sandbox or Demo transaction, Wallet balance, notification, or report does not prove the corresponding Live transaction, balance, notification, report, or bank payout.
Move to Live deliberately
Treat Live as a separate production configuration. Before accepting guest payments, confirm the active environment and current operational readiness with an authorized administrator. Do not switch environments during an active guest or payment flow, and do not promise an immediate switch, a particular badge, data-purge behavior, test card, payment method, or payout timeline from this guide.
Get help safely
For a failed test, share the authorized property or recipient, displayed environment, approximate time, and a non-sensitive error or reference. Never send card numbers, bank details, passwords, verification codes, or tokens.