Separate by design

How the Connection Will Work

A future secure API will connect clearly owned information without combining accounts, databases, or security boundaries.

A future booking journey with clear authority

1

Authorised information

Caravan Management supplies approved unit, price, rule and availability information with stable UUIDs and revisions.

2

Public presentation

KMH presents the accommodation to guests on its own website and retains authority for the public listing.

3

Fresh availability control

Before accepting payment, KMH validates current availability and establishes a temporary hold or another authoritative control.

4

Booking transaction

KMH creates the guest checkout, payment transaction and public booking confirmation.

5

Signed event

KMH sends a signed, timestamped and idempotent booking event to Caravan Management.

6

Operational fulfilment

Caravan Management creates or updates the operational record used by authorised owners, staff and cleaners.

Security boundaries do not disappear

The systems will not share databases, database users, WordPress salts, sessions or credentials. WordPress post IDs and user IDs are local implementation details, never cross-system identifiers.

Future requests and events must use versioned contracts, signed payloads, timestamp checks, replay protection, idempotency keys, audit records, retry controls, reconciliation and key rotation. Each environment will have separate credentials.

Current status: This repository contains a disabled management-side connector foundation and local mock adapter only. It has no live KMH endpoint or credential.