Integrations and source ownership

• Card terminal and processor. Bring settlement references in so the accounts clerk can confirm each payment against what was actually received.

• Accounting. Send confirmed and refunded payments to your accounting system for takings and refunds.

• Online booking or website. Bring booking requests in as requested bookings for the front desk to confirm.

• Identity provider. Map staff and instructors to user accounts so every check-in and exposure plan shows who entered it.

Each connection needs an agreed source of truth, a field mapping, an event identifier and a retry policy. Keep credentials in the approved secret store with the smallest scope that works. A repeated delivery must not create a second booking or payment. Rejected records wait in a queue with the original identifier and a visible reason.

Reconcile bookings and payments with their source daily during the pilot. Test a duplicate booking request, a failed card payment and a revoked credential before turning on schedules. Availability depends on each provider’s interface, commercial access and configuration.

Use the implementation plan to agree integration acceptance criteria.