Integrations and source ownership

• Card terminal and payment provider. Match payments to pending charges by a stable reference.
• Online booking page. Send booking requests into the queue as Requested for confirmation.
• Email and SMS. Send booking confirmations, cancellations and closure notices.
• Chemistry controllers. Send readings from automatic controllers as water checks, with the pool and time.
• Accounting software. Export confirmed payments and refunds by day.

Each connection needs an agreed source of truth, a field mapping, a stable identifier and a retry policy. A repeated payment notification must not confirm a charge twice, and a repeated reading must not create a second check for the same time. Keep credentials in the approved secret store and grant the smallest scope the connection needs. Queue rejected records with their source identifier and a visible reason.

Test a timeout, a duplicate notification and a revoked credential before turning on schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree acceptance criteria for each connection.