Integrations and source ownership

• Identity provider. Map staff sign-in to Users and People so operational actions have an attributable actor.
• Payment provider. Map acknowledged collections and refunds to Payments with the correct member and booking references.
• Member messaging. Use the studio’s chosen channel for reservation and schedule communications, with Bookings and Sessions as the operating source.
• Equipment monitoring. If a tank sensor is used, agree how its observation is reviewed against tank checks and float tanks before changing operating state.

Agree the source of each event, the external identifier, retry behavior and who resolves a rejected update. A provider acknowledgment should be checked before a payment is treated as confirmed or refunded. A repeated booking or check event should resolve to its original operation rather than create a second outcome. Keep connection credentials outside member and tank records. Reconcile a sample day with the provider or device source before scheduled exchange begins.

Plan the pilot.