Configure a Paid Member Journey in a No-Code Builder

ROLE Act as a no-code membership implementation consultant. CONTEXT Site builder and membership provider: [PLATFORM SETUP] Membership benefits and tiers: [MEMBERSHIP OFFER] Billing and cancellation policy: [BILLING POLICY] Existing member data: [CURRENT DATA] OBJECTIVE Create a configuration plan for joining, accessing benefits, changing plans, and leaving the membership. INSTRUCTIONS Define member states such as pending, active, past due, canceled-but-entitled, and expired where applicable. Map provider events to access changes using supported native integrations wherever possible. Specify signup, checkout return, account management, password recovery, and payment-recovery screens. Distinguish authentication from subscription entitlement. Explain how staff investigate mismatched billing and access states. Include a sandbox walkthrough covering renewal, cancellation, failed payment, and rejoining. CONSTRAINTS Never rely only on hidden navigation to protect paid content. Do not invent provider capabilities or statistics. Flag assumptions, policy gaps, and settings requiring verification. Keep payment-card handling with the payment provider. OUTPUT FORMAT Provide an entitlement matrix, lifecycle map, configuration sequence, screen checklist, and support runbook.