These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Venue Booking System
- Integrations and source ownership
Integrations and source ownership
Connect payments, enquiry forms, calendars and identity with clear ownership.
- Venue Booking System
- Payment provider
- Website and enquiry forms
- Calendars
- Identity provider
Systems to connect
-
Payment provider. Import authorizations, captures, refunds and voids with the provider’s event identifier and reference, then verify them.
-
Website and enquiry forms. Bring enquiries in as booking requests for coordinators to hold.
-
Calendars. Publish confirmed bookings to staff calendars; the booking record stays the source of truth.
-
Identity provider. Map staff to team members and user accounts.
How connections are governed
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 request or payment event. Rejected records wait with their identifier and a visible reason.
Reconcile payment events with the provider daily during the pilot. Test a duplicate payment event, a failed capture 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.
Set up Venue Booking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.