Skip to content
ADVISORY RECONCILIATION · STRIPE ↔ ENTITLEMENTSRun the browser-only CSV audit

USE CASE · ENGINEERS

Your access logic is code. Your billing is a service. The contract between them is invisible.

Platform engineers own the mapping between Stripe customers and application entitlements. SubSync Guard makes that mapping observable, testable, and auditable.

The engineering problem

The mapping between a Stripe customer and an application user is usually a foreign key, an email, or a heuristic. It breaks during migrations, during account merges, and during plan changes. The break is silent until a customer complains.

  • Customer-to-user mapping drift after an access-control migration
  • Entitlement state that lags behind subscription state
  • Manual grants and overrides that are never reconciled
  • No automated check that the two sides still agree

What SubSync Guard provides

A signed, HMAC-verified entitlement snapshot from the customer’s own Supabase project, compared against a paginated Stripe snapshot. The comparison is deterministic and policy-aware.

  • Signed Supabase entitlement snapshots with atomic nonce replay protection
  • Paginated Stripe subscription and invoice sync
  • Policy configuration for trials, grace periods, and cancellation
  • Stable finding fingerprints for idempotent reconciliation
  • Browser audit for one-off validation without infrastructure

Auditing an access-control migration

Run the browser audit before and after a migration to compare the entitlement state. Findings show which accounts changed, in which direction, and whether the policy still holds.

Frequently asked

Does SubSync Guard receive my service-role key?

No. You deploy a customer-owned Edge Function that exports a narrow shape and signs the request. The service-role key stays in your project.

Can I run reconciliation without connecting Stripe live?

Yes. The browser audit works on two CSV exports. Connected mode uses Stripe TEST keys only.

Is there a public API?

No. The current release candidate does not expose a public API.

Next step

Start with the evidence. Connect nothing until the workflow earns it.

START WITH THE EVIDENCE

See the gap before it becomes a refund.

Run a private CSV audit in your browser, or create a workspace and connect an isolated Stripe TEST account.