For a course sold as a subscription, systeme.io grants resource access when the order is created by default—even if the first payment has not yet been received. Keep that default only if you accept the possibility of temporary unpaid access. If course access must wait for confirmed collection, choose Grant access only after receiving the first payment in Payment settings.
This guide is for a solo teacher deciding one access policy before selling a subscription offer. It does not cover a one-time price or an installment plan. Reference + Worksheet: official Help Center pages checked October 30, 2026. No order, payment, retry, cancellation, or setting change was performed for this article.
Choose which risk your promise can carry
Access after order
Documented default. The learner can enter while the first payment is still processing. Your risk is access before confirmed collection.
Access after payment
Optional setting. The resource waits for the first payment. Your risk is a legitimate buyer waiting during payment processing.
Original policy map based on documentation; it is not a payment test or a systeme.io screenshot.
Start with the subscription promise
Choose the sentence you can support:
Immediate policy: “Your course access starts when your subscription order is created. Payment confirmation may follow.”
Payment-first policy: “Your course access starts after the first subscription payment is received.”
Do not promise “instant access after payment” when your payment method can remain pending. Systeme.io says processing for methods such as PayPal or GoCardless may take up to seven days. That is a documented possibility, not a prediction for every transaction.
Check the documented payment setting
The official subscription resource-access guide gives this route: Profile picture → Settings → Payment settings. The default is Grant immediate access after creating an order. The alternative is Grant access only after receiving the first payment.
Not tested here: this setting was not opened or changed. The help page does not explicitly document whether a change affects existing subscription orders, only future orders, or every offer in the account. If that scope matters, leave the live setting unchanged and ask systeme.io support before editing it.
The official page also says that a failed first payment triggers additional collection attempts in the following days. It does not give a retry count or exact schedule on this page. Do not invent either in your buyer message.
Record the policy before changing anything
Copy the subscription access-policy note
Offer: exact internal name
Price plan confirmed: subscription / other / Not checked
Buyer-facing access promise: exact sentence
Current Payment settings choice: immediate after order / after first payment / Not checked
Payment methods offered: actual methods
Longest documented processing window relevant to those methods: record or Not checked
Risk accepted: temporary unpaid access / paid buyer waiting / neither yet
Pending-payment reply: exact wording or Not prepared
Existing subscriptions affected: confirmed scope / Not tested
Next action: keep setting / change after review / ask support / do not use a subscription
Keep buyer names, email addresses, payment references, and private checkout links out of shared copies. This note records a policy; it is not proof that a payment or access event occurred.
Separate first-payment timing from cancellation
The separate subscription cancellation guide says its documented cancellation takes effect just before the next expiration date and automatically removes the resource. It also says installment offers do not use that cancellation path. Cancellation is a later lifecycle event; it does not answer when the first access should begin.
Finish with one policy—or keep subscriptions out
You can finish when the offer type, access promise, current setting, accepted risk, and pending-payment reply agree. If neither risk is acceptable, do not sell this course as a subscription until you have a support process you can maintain. No purchase, upgrade, or platform move is required.
Handling one buyer whose expected access and payment state do not match? Use the private course-access case log and keep payment evidence separate from access evidence. If your real requirement is a fixed access window for a Full or Partial course rather than recurring billing, use the course-expiration timing guide.
Official sources
How do you control access to subscription resources? (updated January 1, 2026) and How to cancel a subscription to systeme.io or an offer hosted on systeme.io (updated June 25, 2026). Checked October 30, 2026. No affiliate links.