What Is Purchase & Access Testing?
Testing your purchase and access flow allows you to experience the path a real user takes when buying your course and gaining access to it.
This includes:
The checkout process
The redirect or confirmation page
Access being automatically granted
The product access notification email
The user’s ability to log in and access the course
Testing ensures everything works smoothly before you launch.
Why Testing Matters
Testing helps you:
Confirm your checkout links work
Ensure access is granted correctly
Verify your Stripe connection (if applicable)
Ensure new users are routed into CustomerHub after purchase
Catch mistakes before real customers encounter them
Avoid support issues on launch day
This step is critical for paid courses.
Before You Begin
Make sure:
Your course product is fully built
Your purchase method is configured
Your Stripe account is connected (if using Stripe checkout)
You have a test email address ready
You are logged out of your CustomerHub site before testing
If you are logged in, the system will treat you as an existing user and will not send you through checkout.
How to Test Purchase & Access Flow
Open a private/incognito window in your browser
This ensures you’re fully logged out and viewing the site as a new visitor.ctrl + shift + n OR command + shift + n
Firefox: cntrl + shift + p OR command + shift + p
Go to the checkout or sales page link
Use the exact link your customers will click.You can find the links in your product under Settings
Complete a test purchase
Fill in the checkout form using a valid email address you control.
Check for a successful redirect
Confirm the checkout redirects to the appropriate confirmation or success page.Check your email
Look for the Course Access Notification email from CustomerHub.Log in using your new user credentials
Use the email and password created during checkout (or provided in the access email).Confirm access to your course
Verify you can see and open the course in your product library.Open your course and test navigation
Confirm lessons load, media plays, and the course behaves based on your delivery settings.
Best Practices
Use a fresh email for each test purchase
If using Stripe test mode, enable test API keys before testing
If using an external checkout, confirm redirects back to CustomerHub
Test both desktop and mobile
After testing, revoke or delete your test user access to reset
FAQ
Do I need to use Stripe test mode for testing?
Recommended but not required. Test mode avoids charges to your card.
Will testing trigger real emails?
Yes. Access notifications will be sent to the test user email.
Do I need a new test user each time?
No, but it’s cleaner. You may repurpose the same test user by removing course access.
Why won’t my checkout trigger?
If you're logged in as an admin, CustomerHub assumes you already have access. Always test while logged out.


