Everything connected. Nothing complicated.

Configured schedules drive recurring invoices, coverage periods and due dates. Saved rent, tax and charge definitions feed the same billing records used by checkout and owner workflows.

Payment events are matched to their account and attempt before receipts and allocations are posted. Repeat requests and recovery reconcile existing work, helping prevent a retry from becoming another charge. Bank verification, processing and settlement remain different states.

StoraCore is the internal name used for StoraMate’s shared billing and operational core: agreed rates, charge definitions, invoice commands and recurring processing.

Private platform administration is a separate responsibility. It manages software-customer configuration and restricted platform setup; it does not process a facility’s payments. Stripe processes rental payments in the facility’s connected merchant account.

StoraMate’s application records use PostgreSQL through Supabase. Private documents use protected storage and, for applicable document workflows, database-backed bytes.

Document reads pass through relationship and permission checks. Source versions, completed executions and rental associations let the right people retrieve the right document without replacing a signed record when a template changes.

Facility memberships and staff permissions govern facility work. Protected owner and staff operations require multi-factor authentication; renter access is tied to the actual account and rental relationship.

Email confirmation proves control of the confirmation channel. Existing-account sign-in and facility association are separate checks. Entering someone’s email or knowing a unit number does not grant their account or document access.

Scheduled billing jobs identify due work from saved configuration. Payment-event handling and processor recovery reconcile provider state with recorded attempts. Preparation and communication jobs keep their own progress and retry state.

The benefit is continuity after an interrupted request: reconcile what already happened, retry what remains, and surface unresolved work for owner attention. These are specific scheduled and event-driven operations, not a promise of continuous monitoring of every record.

Verification exercises repeated requests, interrupted checkout, concurrent actions, signing recovery and cross-renter or cross-facility denials. Payment acceptance checks provider events against receipts, allocations and invoice balances in Stripe Sandbox.

Chrome and WebKit journeys complement server and database regressions. They provide evidence for tested behavior, not a guarantee that software cannot fail. Each facility still completes payment onboarding and deliberate activation before live collection.