Core concepts

The mental model behind Stripe Sync — worth two minutes before day-to-day use.

Two pipelines

Stripe Sync records billing in HubSpot through two distinct pipelines:

1. Immutable bookings — a booking (a new subscription, an upgrade) is written once, as it happened. It is never re-written or re-delivered. This is what makes revenue reporting trustworthy.
2. Delta deals — ongoing changes to an existing subscription (renewal amount changes, pauses, cancellations) are applied as deltas to the linked deal, so the deal reflects the current truth without rewriting history.

Sync states

Every synced object carries a state:

State	Meaning
pending	Seen in Stripe, not yet written to HubSpot.
synced	Written and current.
broken	Mapping failed (e.g. linked contact deleted) — needs a relink.
ignored	Excluded by your settings (e.g. test-mode data).

What we never do

• No stage changes on our own — pipelines move deals between the stages you configure; we don't invent lifecycle steps.
• No invoice re-delivery — a booking is delivered once. Corrections in Stripe appear as new events, not edits of the past.
• No writes to Stripe you didn't ask for — every outbound action (pause, cancel, refund, checkout link) is user-initiated and audited.