GetRejoinly server integration (Express example) Install only inside your existing application. Its own authenticated account and CSRF middleware are required. Keep the GetRejoinly key in a server secret. app.post('/api/rejoinly-cancel', requireLogin, requireCsrf, async (req, res) => { // These IDs MUST come from the logged-in user's record in YOUR database. // Never take customer/subscription IDs from req.body or URL parameters. const account = await database.findAccountForUser(req.user.id); if (!account?.stripeCustomerId || !account?.stripeSubscriptionId) { return res.status(404).json({error: 'No subscription found.'}); } try { const response = await fetch('https://getrejoinly.com/api/cancel-sessions', { method: 'POST', headers: { 'Authorization': 'Bearer ' + process.env.REJOINLY_SERVER_KEY, 'Content-Type': 'application/json' }, body: JSON.stringify({ customer: account.stripeCustomerId, subscription: account.stripeSubscriptionId, returnUrl: 'https://YOUR_PRODUCT_DOMAIN/billing' }) }); if (!response.ok) { return res.status(502).json({error: 'Please use our normal billing page.'}); } res.json(await response.json()); } catch { res.status(503).json({error: 'Please use our normal billing page.'}); } }); Add the browser script/button shown on https://getrejoinly.com/install. If your CSRF token is available in a meta[name="csrf-token"] element, the browser helper sends it in X-CSRF-Token. Adapt to your existing protection. Keep your original billing page accessible even when GetRejoinly is unavailable. GetRejoinly sets cancel_at_period_end in Stripe. Your existing Stripe lifecycle handler must still update app access at the correct time. GetRejoinly does not preserve projects, bypass your access checks, or restart paid plans automatically.