Stripe

Events

The Stripe events Verlix subscribes to, and what each one tells you.

Verlix subscribes the webhook endpoint to sixteen Stripe event types. The names and payload shapes belong to Stripe. The descriptions here are a quick orientation, and Stripe's own reference stays the authority on fields.

Subscribed events#

Invoices#

Event	Means
`invoice.created`	A draft invoice now exists
`invoice.finalized`	The invoice is locked and ready to be paid
`invoice.paid`	The invoice has been paid in full
`invoice.payment_failed`	A payment attempt on the invoice did not succeed
`invoice.voided`	The invoice was cancelled and can no longer be paid
`invoice.marked_uncollectible`	The invoice was written off as unlikely to be paid

Credit notes#

Event	Means
`credit_note.created`	A credit note was issued against an invoice
`credit_note.voided`	A credit note was cancelled

Charges#

Event	Means
`charge.succeeded`	A card or bank charge went through
`charge.refunded`	A charge was refunded, fully or in part
`charge.dispute.created`	A customer opened a dispute against a charge

Payment intents#

Event	Means
`payment_intent.succeeded`	A payment completed
`payment_intent.payment_failed`	A payment attempt failed

Subscriptions#

Event	Means
`customer.subscription.created`	A subscription started
`customer.subscription.updated`	A subscription changed, for example its plan or status
`customer.subscription.deleted`	A subscription ended

Polling is not limited to this list

The list applies to webhooks only. Polling reads whatever Stripe returns from its events feed, so an event type outside the list can still land in Verlix. Do not rely on its absence.

What an event looks like#

Verlix keeps the body Stripe sent. A trimmed example, with placeholders instead of real values:

{
  "id": "evt_example",
  "type": "invoice.paid",
  "account": "acct_example",
  "created": 1767225600,
  "data": {
    "object": {
      "id": "in_example",
      "status": "paid"
    }
  }
}

Two fields matter to Verlix itself. account is compared with the account linked to your connection, and created decides the date the event is filed under.