Production refund and entitlement-revocation workflow

[oussama-HA]

Hello,

We use ExtensionPay for our extension with a one-time lifetime payment.
During testing, we refunded a completed payment in Stripe, but extpay.getUser() continued returning paid: true, including in another browser profile that had restored the purchase.

Could you please clarify:

• Does ExtensionPay automatically process Stripe refunds, reversals, disputes, and chargebacks for lifetime payments?
• If not, what is the exact procedure for revoking a refunded customer’s entitlement?
• Is there a dashboard control or authenticated server API for revoking paid access?
• Does revocation apply to every browser/profile where that customer restored their purchase?
• How quickly should getUser() return paid: false after revocation?
• Is automated refund synchronization or a developer revocation API planned?

We need a reliable production procedure that ensures refunded lifetime purchases no longer retain access.
Thank you,

[Glench]

Just email me if you want a lifetime user's paid access revoked across all browsers/logins. Subscriptions are already automatically synced. The reason is that sometimes a developer wants to let a user keep their paid access despite refund and sometimes not.