systeme.io Review: Pricing, Limits, Payments, and Exit Boundaries

What this review can establish

Facts are bounded to official pages reviewed September 6, 2026. Where official pages disagree, this article records the conflict instead of selecting the more favorable claim.

Who should shortlist systeme.io

• You want email, landing pages, sales funnels, checkout, courses, and automation under one subscription.
• A permanent free plan is useful for validating a small real workflow before paying.
• Basic hosted communities support the offer rather than define the whole member experience.
• You accept processor-specific payment rules and can test Japan onboarding directly.

Start with the course-first versus community-first guideand use the Requirements Finder to keep one critical unknown from becoming an assumed match.

Who should pause

• You need a branded native learner or community mobile app.
• You need live webinars rather than automated evergreen sessions.
• You require a documented full-site, full-course, community, and automation export.
• You need a specialist feature to be equivalent in depth, performance, or usability.

Compare a course-first alternative in the LearnWorlds research brief, a compact community model in the Skool research brief, and the normalized course and community dataset.

Japan pricing and core plan limits

The free plan does not expire and requires no card. Annual billing is advertised as two months free. Unlimited email sends and file storage are listed across plans, subject to the fair-use policy. Add-ons and negotiated services are not included in this table.

Email, funnels, automation, courses, and community

Published features include unlimited email sending within the contact ceiling, newsletters and campaigns, funnel pages, rules and multi-step workflows, blogs, custom domains, hosted courses, drip access, quizzes, bundles, student progress, and communities. Storage is advertised as unlimited, but “unlimited” is not exemption from the fair-use policy.

Community pages document topics, posts, comments, files, voice notes, embeds, scheduling, and approval. That list does not establish community depth or moderation quality. Webinar and Unlimited plans support automated evergreen webinars; official help says fixed-date live webinars are not supported.

Checkout, payment plans, gateways, fees, and tax

Order forms can sell digital or physical products and grant courses, bundles, tags, communities, or calendar events. Price plans support one-time payment, subscription, optional trial periods, and installment payment plans.

Keep five economics lines separate: subscription cost, platform transaction fee, processor fee, taxes, and add-ons. systeme.io advertises a 0% platform transaction fee; processor fees from Stripe, PayPal, or another gateway remain separate. The official gateway documentation includes JPY for Stripe cards and PayPal, but merchant approval, methods, recurring support, settlement, and fees remain provider- and country-specific. Use the total cost calculator for a separated scenario.

The documented automatic tax logic concentrates on VAT. It does not establish complete Japanese consumption-tax calculation, filing, invoicing, or advice; the seller remains responsible for validating the intended tax treatment.

Two different affiliate systems

Customer-run affiliate management

This product feature lets a seller operate an affiliate program for the seller's own offers. Defaults shown in help are 40%, a $30-equivalent threshold, a 30-day delay, and 0% second tier; settings can be changed. The seller remains responsible for affiliate payouts, manually or through documented Wise or PayPal-assisted workflows.

systeme.io publisher affiliate program

This separate commercial program currently advertises 60% commission, lifetime account attribution with a payment-page-link exception, a $30 threshold, at least a 30-day hold, and payment after conditions are met. The agreement permits rate changes through the Affiliate Tool. Publisher affiliate economics did not influence this product verdict. No affiliate application, account, tracking link, or commercial placement is active.

Integrations, API, and webhooks

The current public API can manage contacts, email, funnels and pages, prices, courses, communities, automation rules, subscriptions, products, offers, and webhooks. Help documents up to three API keys; the pricing matrix lists 30, 60, 120, and unlimited API requests per minute by plan. Named integrations include Google Sheets, Calendar, Meet, Zoom, ActiveCampaign, SendGrid, and Twilio. ActiveCampaign synchronization is one-way.

Zapier's current plan boundary was not established by the reviewed official material. Test each required trigger, action, payload, rate limit, and error path rather than treating “integration” as proof of a complete workflow.

Branding and mobile boundary

Custom domains are plan-limited. Paid plans can remove the systeme.io affiliate badge from funnel pages; the Free plan cannot. Pages, creator stores, and light courses have mobile-oriented editing or layouts, but systeme.io's official community page says there is no branded native mobile app.

White Label changes dashboards, login pages, transactional email, logos, and colors for resold accounts; it is not a native learner app. Official help warns that White Label activation currently cannot be deleted, reset, or deactivated and dedicates its domain.

Cancellation, refunds, retention, backup, and portability

Cancellation takes effect at the next renewal boundary. Public terms describe subscriptions as non-refundable, while support says special circumstances can be reviewed. Downgrades require support. Excess paid-plan usage may trigger an automatic upgrade after notice; restrictions can disable new opt-ins, payments, sends, and enrollments.

Official help documents contact CSV and student-and-progress CSV exports. It does not prove a complete export of funnel structure, page design, course content, community history, automation, files, subscriptions, or settings. The privacy policy mentions regular backups but publishes no customer restore workflow, retention duration, RPO, or RTO.

Free migration into systeme.io is offered with Unlimited monthly or any annual plan and can include contacts, funnels, blogs, courses, campaigns, and automation. The stated average is 17 days, not a service guarantee. An end-to-end exit or reconstruction was not tested.

Japan, support, and payout unknowns

• Not verified Japan-specific Stripe or PayPal merchant approval, settlement schedule, and processor fees.
• Not verified Japanese consumption-tax filing, qualified-invoice, and accounting workflow.
• Not verified Publisher affiliate eligibility for a particular Japan entity and successful receipt by a particular Japanese bank.
• Not verified Payout currency, conversion spread, intermediary-bank fees, withholding, and identity documents.
• Not verified Complete backup restoration and cross-platform reconstruction.

Affiliate payout documentation offers PayPal or wire transfer using ACH, wire, or SWIFT details; wire is unavailable before the first affiliate sale and must be configured per earned currency. The agreement is with Ireland-incorporated ITACWT Limited and applies Irish law and Irish-court jurisdiction. That does not by itself prove Japan payout eligibility.

Official pricing advertises email support seven days a week with an average response under two hours. General phone support is not offered; eligible annual or Unlimited monthly plans receive a kickstart call, and a separately priced technical call is documented. Published support availability does not establish support quality or response time; neither was tested.

Validation checklist before replacing tools

1. Confirm the controlling plan limits in the logged-in My plan and checkout screens.
2. Import a consented sample list and test authentication, segmentation, sends, and unsubscribe behavior.
3. Build one complete funnel with checkout, tax, refund, failed-payment, subscription, and installment cases.
4. Create a representative course, drip schedule, quiz, community, and learner account.
5. Exercise each required API, webhook, and integration workflow.
6. Export every record and asset needed to rebuild elsewhere before migrating production data.