Online payment and repair-financing controls are intentionally disabled in the portable production build. They will return only behind provider-created sessions, signed webhooks, idempotent processing, and reconciliation.
Checkout and financing actions remain unavailable until signed webhook and reconciliation tests pass.
The inherited prototype made financing look complete before a lender integration existed. That is not an acceptable boundary for a CRM handling customer and billing data, so the interactive controls and their database permissions have been removed.
The replacement will be provider-neutral and auditable: the server creates a session for a specific invoice, the provider returns the customer flow, and only a verified webhook can change financial state.
Create estimates, publish them to the homeowner portal, convert approved work into work orders, create invoices, and reconcile offline payments from the staff billing screen. The interface does not claim that an email, card payment, or financing application occurred when it did not.
Provider onboarding, server-side price ownership, signed webhook verification, replay protection, idempotency, refunds and disputes, ledger reconciliation, authorization tests, and operational alerts must all pass in staging before online controls are enabled.
Invoice payment status will come from a trusted provider event or an authorized staff reconciliation flow.
Webhook event IDs and idempotency keys prevent duplicate charges and repeated state transitions.
Every invoice, provider account, and webhook event remains scoped to the correct contractor workspace.
Provider event history and application transitions will support support investigations and reconciliation.
Not in the portable production build. These controls are disabled until a payment provider creates the checkout session and a signed webhook verifies every payment or financing state change.
Teams can create and track estimates and invoices, publish estimates to the homeowner portal, and record an offline payment after reconciling it. Homeowners contact their pool company for payment instructions.
It used illustrative rates and local database records rather than a completed lender integration. SplashIQ will not present that preview as a live financial product.
Provider approval, server-created sessions, signed webhook verification, idempotency, reconciliation, refunds and disputes, role-based tests, and production monitoring.