Use case
SaaS access
Software sellers need a processor-independent chronology of entitlement, authentication, and usage milestones when a buyer disputes a charge.
Why reconstruction fails
Provider dashboards show payment state. Product telemetry shows usage. Neither alone answers the full question of what the buyer received and when.
What the record is designed to hold
Useful items may include account creation, entitlement activation, authentication, product usage milestones, billing changes, and suspension or cancellation events.
Designed to capture / may include
- Account creation
- Entitlement activation
- Authentication
- Product usage milestones
- Billing changes
- Account suspension or cancellation
Custom checkout and API ingestion paths are in development so SaaS merchants can send server-side events without waiting for a named host connector.