Ghost membership gating and Stripe webhook synchronization latency

Ghost uses a membership system integrated with Stripe to enforce content visibility settings, specifically for posts marked as 'Paid members only'. This mechanism relies on Stripe webhook events to update member statuses in the Ghost database to grant or revoke access.

There is uncertainty regarding the exact synchronization window between a successful payment event in Stripe and the corresponding status update within Ghost. If a user attempts to access gated content immediately after a subscription change, the server-side session check may not yet reflect the updated tier, potentially leading to unexpected redirects to the sign-up page.

• What is the expected latency for Stripe webhook events to propagate to the Ghost member status?
• Does Ghost provide a mechanism to force a session refresh for members immediately following a Stripe checkout completion?