Integrations and source ownership

• Payment provider. Send authorizations, captures, refunds and voids into payment evidence with the provider’s event identifier and reference.
• Guest RSVP website. Send guest responses into reservations with a stable guest reference and party size.
• Email and messaging. Send RSVP confirmations, schedule changes and vendor reminders from the agency’s messaging service.
• Accounting software. Export approved vendor fees and verified guest payments for invoicing and bookkeeping.
• Identity provider. Map staff sign-in to team members; removing a leaver’s access must also remove their platform access.

Each connection needs an agreed source of truth, a field mapping, a stable event identifier and a retry policy. A repeated payment notification must not create a second piece of evidence, and a repeated RSVP must not reserve a second place. 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 provider 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.