Sapeans

Design access that can support your community.

Separate the community’s Sapeans plan from member-facing paid access, plans, coupons, billing, receipts, and entry state.

Platform pricing and member access are different decisions.

A community pays for the Sapeans capabilities it uses; a member may separately pay for access to that community or one of its plans. Combining those concepts creates confusion at exactly the moment trust matters. Sapeans presents creator billing, paid-membership configuration, coupons, member checkout, and payment history as related but distinct flows.

What it makes possible

Choose the community’s Sapeans plan

Circles, Tasks, Courses, Marketplace, and Gigs are free. Pro enables charging for memberships, courses, Marketplace offers, and event tickets.

Enable paid membership

Eligible admins can turn on paid membership and configure active member plans. A community only requires paid entry when the feature is enabled and an applicable active plan exists.

Create membership coupons

Coupons support percentage or amount discounts, first-invoice or ongoing duration where currently implemented, redemption limits, expiry, and eligible member plans.

Keep checkout state explicit

Joining preserves the intended community or event destination through authentication, configured questions, plan selection, provider checkout, and resulting membership state. Failure and pending states remain visible rather than being treated as approved access.

Give members payment context

The member-facing Payments surface presents the relevant community payment and receipt information exposed by the current provider integration, including appropriate empty and entry states.

How it works

Configure

The community selects its Sapeans plan, enables paid membership, and creates eligible member plans.

Present

A joining visitor sees the applicable access model and active member plans.

Complete checkout

The visitor follows the current payment-provider handoff and returns with an explicit state.

Maintain access

Membership, renewals, cancellations, payment context, and plan eligibility follow the current billing rules.

Controls for community builders

Community subscription

The Current Sapeans plan controls platform capabilities and remains separate from member pricing.

Member plans and coupons

Admins manage active membership plans, paid-entry enablement, and the coupon fields currently supported.

Provider handoff

Sensitive checkout is handled through the configured payment integration; marketing copy does not promise a provider-independent guarantee.

Plans, permissions, and availability

Paid memberships and membership discounts require Pro. Paid entry also requires configured payment support, active member plans, and successful checkout state.

Frequently asked questions

Is a Sapeans plan the same as a community membership plan?

No. The Sapeans plan belongs to the community builder and controls platform capabilities. A membership plan belongs to the community’s members and controls paid entry or access.

Can a community offer coupons?

Yes, when paid memberships and the applicable plan capabilities are available. Current coupon fields include discount type, amount or percentage, duration, limits, expiry, and eligible plans.

Does payment instantly bypass review?

No general bypass is promised. Joining continues to respect the configured membership, question, payment, and approval states.

Where can a member see payment information?

The member Payments surface presents the current billing and receipt information exposed by the configured payment flow.