How this site is funded. We may earn a commission through the Systeme.io links on this page, at no additional cost to you. Other recommendations can be non-affiliate links. Read the disclosure.
Start with a single offer delivered through course access. Connect a supported payment provider, create the resource, attach it to the order form, and test the full customer journey before promoting it.
Before opening the builder
Prepare the product name, lesson or file content, price, currency, customer support address and the purchase terms you intend to display. This example uses a course resource that can contain a lesson and downloadable materials. It is a workflow for selling your own product—not a requirement for promoting an affiliate link.
The button names below follow the linked official help pages. Interfaces can change; a payment or authorization screen should only be completed when its current wording matches the intended action. No page preview substitutes for a real access test.
1. Connect the payment provider
- Open your profile menu, then Settings → Payment gateways.
- For Stripe, choose Connect and complete the provider’s own account and authorization flow. Use accurate business details.
- Return to Systeme.io and confirm the connection is present. Do not publish credentials or payment keys in your page code.
Stripe’s guide says the order form needs email and first-name fields. [source] PayPal has a separate connection flow and additional order-form and notification requirements; use its guide when you enable it. [source]
2. Prepare the resource buyers will receive
- Open Assets → Courses → Add a new course. Enter its name, available domain, URL path and theme, then Save.
- Choose Add module, name it and save. Inside it, choose Add lecture.
- Set the lecture title and release timing, choose a template and save. Add your actual teaching content and materials in the lecture editor.
- Activate the course and its ready lectures, then test access with a student account.
These are the official course-creation steps. Full access and drip access behave differently, so choose the mode that matches the product description. [source]
3. Build the sales funnel
- Go to Sites → Sales funnels → Create.
- Enter the funnel name, choose an available domain and currency, and select the Sell type. It supplies an order form and thank-you step.
- Choose and edit the order-form template. Explain the product, who it is for, what access includes, price and support.
- Edit the thank-you page with accurate next steps rather than a public link that bypasses your chosen access controls.
Use + Add step when you need another page. Start without extra branches until the basic sale works. [source]
4. Attach the offer and set its price
In the order-form configuration, choose Digital product, add the course resource and select the intended access mode. Create the price plan, choose one-time payment for this example, enter the amount and check currency and tax treatment. Save the price and the order-form configuration. [source] [source]
Open the funnel’s Funnel settings, enable the connected card or PayPal payment option you will use, and Save. A connected account and an enabled funnel payment option are separate checks. [source]
5. Add only the follow-up you need
First inspect the built-in course access message so your custom email does not duplicate it. For an additional workflow, open Automations → Workflows → + Create, name it, save, and configure the appropriate purchase or course-related trigger and action. Test exactly when it fires. [source]
Keep access instructions separate from optional marketing. Use an authenticated sending domain for the addresses you control and honor the relevant consent and unsubscribe requirements. [source]
6. Test, then publish
- Use a fresh buyer email and the payment provider’s supported test procedure.
- Confirm the displayed charge and resource agree with the offer.
- Open the access message and lesson on a phone; test any download from a non-admin session.
- Verify a failed purchase does not grant unintended access.
- Check what happens when an order is refunded or access is revoked.
- Publish only after the support path and all customer-facing text are accurate.
Use the launch checklist (.txt) to record results. An order bump or upsell is a later optimization: the documented setup differs, so treat each added offer as another journey to test. [source] [source]
Common questions
Do I need my own domain to test the workflow?
Use an address available in the account for the pilot. A branded domain can be connected later using that account’s generated DNS records.
Does a tag alone protect a download?
No. A tag can trigger actions but is not an access-control mechanism for a publicly reachable file.
Should I add every automation before launch?
No. Prove the basic payment-and-delivery journey first. Add more branches only when their purpose and tests are clear.
Show your work
Sources & methodology
Official documentation and plan pages checked on 4 October 2026. Prices and features can change. The practical recommendations are IONOSX’s analysis; this article does not claim hands-on performance testing.
- Systeme.io — connect Stripe
- Systeme.io — connect PayPal
- Systeme.io — create a course and lectures
- Systeme.io — create a sales funnel
- Systeme.io — create an order form
- Systeme.io — configure a price plan
- Systeme.io — activate Stripe or PayPal
- Systeme.io — create and manage workflows
- Systeme.io — authenticate an email-sending domain
- Systeme.io — order bumps
- Systeme.io — upsells and downsells