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

INTEGRATIONS

Narrow connections.
Explicit requirements.

Every integration states its real status. “Available now” means the path exists in the staging build. “Needs config” means deployment secrets or an administrator decision are required. “Not available” means it is not being sold.

Status keyAvailable nowStagingNeeds configNot available
Staging · TEST only

Stripe

Subscription billing source

Connect a Stripe restricted key with read-only access to customers, subscriptions, invoices, products, and prices. The backend performs a read check against each resource before storing the encrypted key.

Requirements

  • Restricted key beginning with rk_test_
  • Read permissions on the five required resources
  • An isolated Stripe test account is strongly recommended
  • Live keys are rejected by the current build
Requires customer setup

Supabase

Entitlement snapshot source

You deploy a small Edge Function in your own Supabase project. It exports a narrow entitlement shape and signs each request with HMAC-SHA256. SubSync Guard verifies the signature and uniqueness of the nonce.

Requirements

  • A customer-owned Edge Function or equivalent signer
  • A per-integration signing secret, stored encrypted
  • A complete-snapshot flag and row count
  • No service-role key is sent to SubSync Guard
Available now

CSV / TSV export

Manual, browser-only audit

The browser audit accepts comma- or tab-separated exports, maps common column names, and reconciles locally. It is the fastest way to validate the workflow before connecting anything.

Requirements

  • One Stripe subscription export
  • One entitlement export with a stable user or customer identifier
  • A modern browser with JavaScript enabled
  • No upload and no account
Staging

Slack

Alert destination

Save a Slack incoming webhook URL for high-priority findings. Only hooks.slack.com URLs under /services/ are accepted, and the UI can send a test message to verify delivery.

Requirements

  • A Slack incoming webhook
  • Backend outbound network access
  • An alert policy with a minimum priority
  • A test send before relying on it
Needs backend config

Email

Alert destination

Email alerts use Resend on the backend. The destination is validated and masked in the interface. Delivery is only available when the deployment has a sender identity and API key.

Requirements

  • RESEND_API_KEY configured on the backend
  • EMAIL_FROM with a verified sender domain
  • An alert policy with a minimum priority
  • A test send before relying on it
Needs admin allowlist

Custom webhook

Alert destination

A generic HTTPS webhook can receive finding notifications, but only after the deployment administrator approves the hostname. This prevents the alert system from becoming an SSRF path.

Requirements

  • HTTPS endpoint, no credentials in the URL, no custom port
  • Hostname added to ALERT_WEBHOOK_ALLOWED_HOSTS
  • A test send before relying on it
  • A receiver that tolerates retries
Not available

Public API

Programmatic access

There is no published public API and no API key program. Do not build against internal function endpoints; they are authenticated, versionless, and may change without notice.

Requirements

  • Not offered in the staging build
  • No API access is included in any plan
Not available

SSO / SCIM

Enterprise identity

SAML SSO and SCIM provisioning are not implemented. The current build uses Supabase email/password authentication and workspace invitations.

Requirements

  • Not offered in the staging build
  • No SSO claim should be inferred from the roles model

DELIBERATE NON-INTEGRATIONS

No write scopes.
No broad keys.

Some integrations are tempting because they make the demo look powerful. They also widen the blast radius. These are intentionally absent.

No Stripe write access

The product does not create charges, change subscriptions, issue refunds, or modify customers. A restricted read key is the only accepted credential.

No service-role key collection

The Supabase connector is deployed and controlled by the customer. SubSync Guard receives signed snapshots, not database credentials.

No automatic remediation

There is no “fix it” button that writes to another system. Remediation belongs to the product that owns the record.

No unapproved outbound hosts

Custom alert webhooks require an explicit deployment allowlist. The feature is not hidden behind a generic “webhook” promise.

THE FASTEST INTEGRATION

No connection beats a local audit.

Start with two CSV exports. If the workflow earns a second run, the documentation covers the Stripe TEST key and the signed Supabase connector.