Connecting Stripe

Stripe is the single most important connection for Omesta. It's where failed-payment detection and recovery live.

What we request

On the OAuth screen Stripe shows, you'll see we request read access to charges, subscriptions, invoices, customers, and disputes. We do not request write access on connection. It's read-only by default.

When write access is added

Only if you enable payment-retry automation or dunning emails on the Growth or Scale plan. At that point we get scoped write access to exactly two surfaces: retry an existing failed charge, and send a dunning email to a specific customer. Nothing else. We can't refund, can't change prices, can't touch subscriptions.

Revoking access

One click from Settings → Integrations → Stripe → Disconnect. Or from Stripe directly: Settings → Team and security → Authorized apps → revoke Omesta. Either path kills the connection immediately and wipes our cache of your data within 24 hours. See Data security for the encryption and access-control story behind the scenes.