Merchant-owned authorization
OAuth or API credentials are stored per GHL location in the database. No per-merchant Railway variable is used.

Integrations
Each connection belongs to one merchant sub-account. Events become evidence only after ScaleSafe can match them to the exact client enrollment with defensible confidence.
Connection principles
Merchants connect their own platform once. ScaleSafe discovers the relevant resources, suggests offer matches, and keeps collecting without asking the merchant to repair individual events.
OAuth or API credentials are stored per GHL location in the database. No per-merchant Railway variable is used.
Stable enrollment references and external IDs survive email changes and repeat purchases of the same offer.
The credential determines the location. A webhook payload cannot select another merchant sub-account.
Ambiguous events remain internal and never become evidence, alter access, or enter a defense packet.
Current catalog
The website and merchant catalog must label each provider accurately instead of marketing a roadmap as a live integration.
Contacts, workflows, appointments, communications, course and fulfillment events supported by the installed app.
NativeMerchant-owned OAuth connection and webhook event pipeline. Public attendance claims wait for final participant-event certification.
BetaTenant-bound canonical API for service access, usage, sessions, progress, deliverables, support, and approved custom activity.
AvailablePayment, recurring, refund, dispute, and supported evidence-submission records.
AvailablePayment, vault, recurring, refund, lifecycle, and reconciliation records.
AvailableHosted checkout, payments, memberships, refunds, and supported membership lifecycle actions.
BetaKajabi, Teachable, Thinkific, Circle, and related providers are released only after provider-specific certification.
StagedClickUp and later project, portal, file, and support systems will focus on delivery evidence rather than raw data dumps.
StagedDefense evidence contract
Providers can send timestamps, activity, actors, resources, duration, progress, and source identifiers. They cannot assign their own proof strength, reason-code tags, exhibit title, or defense conclusion.
ScaleSafe private beta
Request private beta access and we will follow up about your payment channel, offers, and fulfillment systems.
Request beta access