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.
- Wellness Retreat Management
- Integrations and source ownership
Integrations and source ownership
Connect payments, accounting, booking channels and identity with clear ownership.
- Wellness Retreat Management
- Card processor and bank
- Accounting
- Booking channels and website
- Identity provider
Systems to connect
-
Card processor and bank. Bring payment references in so the accounts clerk can confirm each payment against what was actually received.
-
Accounting. Send posted charges and confirmed payments to your accounting system for revenue and receivables.
-
Booking channels and website. Bring booking requests in as requested reservations for the front desk to confirm.
-
Identity provider. Map staff and visiting facilitators to user accounts so every record shows who entered it.
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 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 message, 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.
Set up Wellness Retreat Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.