Separate two Stripe purposes
Reylin’s own subscription billing is not the customer analytics connection. A shared merchant account may contain unrelated services. Choose a selected-product scope, or explicitly choose account-wide analytics only when the entire account belongs in that project. No client metadata can establish product eligibility.
The owner-only launch policy is non-billable and currently permits only test-mode customer analytics. Live collection remains a separate acceptance and authorization gate.
Connection checklist
- Use a verified owner workspace and approved site origin, not the shared synthetic demo.
- Confirm the provider account and test/live mode with authoritative credentials before saving a connection.
- Choose the immutable project product scope before ingesting payments. Changing scope requires a separate project, not rewriting old receipts.
- Configure the exact webhook endpoint and signing secret through an approved secure credential flow. Never paste keys into a guide, article, browser console or chat.
- Confirm raw-body signature verification and delivery, then inspect payment and attribution success separately.
Selected-product decisions
Checkout line items or canonical invoice-payment allocation provide authoritative product evidence. Every included line must be resolvable and within the chosen product set. A wholly unrelated payment is excluded; mixed, ambiguous, missing or unsupported evidence is quarantined. No proportional revenue allocation is guessed.
Receipt amount remains the authoritative paid amount, including supported discounted/partial invoice payments. It is not replaced by a line-item sum. Evidence checks account, mode, identity and currency.
Refunds and recurring revenue
Accepted payment eligibility is frozen. Later product deletion does not break a valid partial refund. Refund-before-payment can retain the verified parent decision without subtracting net receipts until the parent payment arrives. Only succeeded refund state subtracts cash.
Subscription discovery and refresh apply the same product policy. Contracted MRR is gross before discounts and tax, separated by currency; it is not a cash forecast or complete tiered/metered billing model. Unsupported or stale states are not counted as healthy revenue.
Historical limits and live acceptance
Bounded provider-event backfill cannot recreate visitors who were never tracked, and provider history availability is finite. Excluded events advance import coverage without being counted as imported payments. Unresolved evidence remains pending.
Local synthetic tests cover duplicate events, scope exclusions, mixed products, partial refunds, invoice renewals and currency isolation. They do not prove real restricted-key permissions, API-version acceptance, webhook delivery or operational recovery. Complete those checks before connecting live data.