For operators / 03
Your infrastructure. A clear integration contract.
Keep customer authority and commercial control in your own systems. Use DOMAINTAINS to make the PBX-side service relationship explicit, inspectable and maintainable.
Provider-neutral integration
Your platform.
Explicit hand-off points.
These are public extension contracts. Their real authority, storage and transport come from your implementation.
- 01Operator implementation
CustomerAccessAuthenticate + permit mutation
- 02Operator implementation
SelectionCatalogResolve owned, eligible resource
- 03Operator implementation
OrderingPlatformPersist selection + immutable origin
- 04Operator implementation
BillingIntegrationGuard operation + preflight
- 05Operator implementation
ProvisioningAdapterPreflight + confirm allocation
- 06Operator implementation
BillingIntegrationReconcile confirmed outcome
Integrate around responsibilities, not a vendor.
CustomerAccess and SelectionCatalog establish trusted customer, product and resource scope. OrderingPlatform and OrderingLifecycle connect actual cart, checkout and fulfilment stages. AvailabilityCarrier stays read-only. ProvisioningAdapter and BillingIntegration keep confirmation and commercial reconciliation distinct.
Map the public contractsOne relationship. Separate authorities.
A choice, not an allocation.
The customer chooses a service and expresses a number preference. The operator must independently authenticate them and verify that the product and resource belong to them.
Selecting an offer does not reserve a number or authorise a PBX.
Read the authority model ↗Preserve the origin of every selection.
Per-item fields and scoped evidence prevent accidental cross-item reuse. At fulfilment, receipts must match independently verified immutable order origins. A matching account and product alone are not enough.
Cart and checkout integrationDesign for the operation that only partly succeeded.
Allocation can succeed while billing fails. Durable guards must preserve that outcome and prevent a second allocation. The public orchestration requires explicit recovery and matching confirmation; an in-memory fixture cannot provide your production durability.
Provisioning and billing sequenceProtect the shared carrier boundary.
Five-second start spacing, bounded queuing and private CSV/JSONL auditing are represented in the reference. Inventory all availability consumers before integration. Independent lock files or separate hosts do not magically share a limit.
Availability protection