Administration

Stripe Sync Subscriptions: subscriptions and documents

Reuse Stripe gateway credentials and webhook, synchronize subscriptions, link customers, and optionally create documents.

Last updated: 2026-08-19

Automatic document creation

Stripe Sync settings — Masked gateway credentials, shared webhook, and document rules.

The option can create an invoice, receipt, or proforma only when Stripe reports an invoice generated by a synchronized subscription. Ordinary Stripe payments and unrelated events do not create documents through this module.

Before enabling it, configure numbering, VAT, customer fiscal data, currency, descriptions, and duplicate prevention. Review the first generated document line by line before relying on automation.

Manual synchronization

Synchronize subscriptions follows every Stripe result page and creates missing records or updates existing ones by Subscription ID. The log reports processed, created, updated, and failed counts.

Customer association and creation

Stripe Customer ID and email are used to resolve the CRM customer. When supported, synchronization can create a customer record from Stripe data while retaining the remote identifier.

Deduplicate by identity and email before bulk use. A customer created from payment data may still require legal name, tax identifiers, invoice address, and electronic-delivery fields before valid billing.

List and states

The list correlates Subscription ID, Stripe customer, CRM customer, product or description, amount, currency, status, and current period. Use remote identifiers to diagnose mismatches with the configured Stripe account.

Stripe states such as active, canceled, past_due, incomplete, or trialing describe the remote subscription and do not automatically equal the lifecycle of an ISP Billing service. Define how cancellation, collection failure, suspension, and termination are reconciled.

Synchronized Stripe subscriptions — Remote identifiers and state support reconciliation with CRM and billing.

Checklist

Configure the Stripe gateway first
Keep test and live environments separate
Choose the document type deliberately
Validate numbering, tax, and currency
Deduplicate Stripe and CRM customers
Run one synchronization at a time
Review processed and failed counts
Reconcile remote and service lifecycle states
Inspect the first automatic document
Avoid manual duplicates during delayed events