Stripe
Connection status
The states a Stripe connection can be in, and what each means for your events.
Each tenant has one Stripe connection, and that connection is always in exactly one state.
States#
| State | Polling | Webhooks | Meaning |
|---|---|---|---|
ACTIVE | Runs | Accepted | Healthy. The normal state |
PAUSED | Stops | Not accepted | Stopped on purpose, by an operator or by you. Can be resumed |
DISABLED | Stops | Not accepted | The integration was removed or its credential revoked. It stays off until a new connection is created |
DEGRADED | Stops | Accepted | Verlix found a fault it could not fix by itself. It does not recover on its own |
A DEGRADED connection still receives webhooks, so events keep arriving even though polling has stopped. Treat it as a prompt to contact Verlix, not as a reason to relax.
Delivery modes#
A connection also has a mode, which decides how events are collected.
| Mode | Behaviour |
|---|---|
PULL | Polling only |
PUSH | Webhooks, with a polling run kept as a reconciliation check |
BOTH | Webhooks and regular polling together |
Rules of the connection#
- One per tenant. A tenant cannot hold two Stripe connections, and creating a second is refused.
- Identity comes from the connection. Verlix decides which tenant an event belongs to from the connection it arrived on. The event body can contradict that, and never overrides it.
- Secrets never leave. Stored credentials and signing secrets are encrypted, and are not returned when connections are read back.
Pausing and removing#
Pausing stops collection without discarding anything. Disabling is meant to be permanent: the connection stays off until a new one is created. Neither action deletes events that were already stored, and neither removes the webhook endpoint from your Stripe account, so remove it there yourself if you want it gone.