Product boundary
Pausier offers five deployment routes. The organisation chooses the route that fits its customer journey, staff workflow and systems.
Route status identifies the setup path: Available, Available by partner configuration, Custom implementation, or Enterprise implementation. Partner routes require the matching Pausier configuration, commercial boundary, support handoff, and data-boundary review before an organisation uses that route.
Production activation requires client-specific details and approval. No route requires collecting passwords, OTPs, full card numbers, bank logins, private keys, or recovery phrases.
App + Web Dashboard
Use the Pausier Business app and web dashboard for organisation setup, users, roles, sector dashboards, billing, daily checks, reviews, records, and app download handoff.
- Best fit: Organisations that want Pausier as the direct business workspace. Teams that need owner, manager, and worker workflows without a partner build.
- Setup requirements: Business organisation workspace Owner, manager, and worker role model Configured sector dashboard Web billing or approved manual invoice handoff App download path through approved business app release gates Worker to manager to owner review workflow
- Security boundary: Tenant-scoped Pausier organisation workspace with business roles, safe report wording, audit records, and no partner runtime credentials.
- Commercial model: Starter, Team, Plus, Enterprise, or manual enterprise invoice where approved.
Use Pausier BusinessHosted Partner Flow
Route a partner journey into a Pausier-hosted decision-support flow with agreed entry context, support handoff, and record boundary.
- Best fit: Partners that want a Pausier-hosted step in their customer or staff journey. Organisations that prefer Pausier to operate the decision-support surface while the partner manages the surrounding journey.
- Setup requirements: Approved partner configuration Agreed entry and completion URLs or handoff rules Tenant and sector mapping Support and escalation ownership
- Security boundary: No sensitive partner context in URLs; partner handoff data must be minimal, tenant-scoped, and approved before activation.
- Commercial model: Contact sales. Setup and monthly platform pricing. Custom enterprise contract where needed.
Discuss hosted flowEmbedded Widget
Embed a Pausier decision-support surface inside an approved partner web journey with operator-configured widget ID, exact allowed origins, reviewed placement, wording, accessibility, and data boundaries.
- Best fit: Partners that need Pausier guidance inside a partner-controlled web workflow. Organisations with customer or staff journeys where a custom embedded pause and verification step is the right route.
- Setup requirements: Reviewed partner web placement Operator-configured widget ID and exact allowed origins Active Hosted Partner Flow mapping Approved wording and accessibility checks Tenant and sector mapping Event, retention, and support boundaries
- Security boundary: Widget scope must be limited to approved decision-support fields and must not expose partner secrets or collect forbidden sensitive data.
- Commercial model: Contact sales. Setup and monthly platform pricing. Custom enterprise contract where needed.
Plan embedded widgetPartner API + Webhooks
Use enterprise API and webhook handoffs for scoped decision checks, URL checks, case references, outcomes, and signed status events after security and contract review.
- Best fit: Enterprise partners with server-side systems that need structured Pausier handoffs. Organisations that need API and webhook integration under an enterprise implementation plan.
- Setup requirements: Enterprise contract and technical design Approved API scopes and webhook events Operator-created API credential hashes and webhook endpoint metadata Monitoring, audit, outbound delivery activation, retry, and support procedures
- Security boundary: Server-to-server access must use approved scopes, hash-only credential storage, signed webhook payloads, event logs, monitoring, and tenant isolation.
- Commercial model: Contact sales. Setup and monthly platform pricing. Usage-based pricing available for API routes. Custom enterprise contract.
Discuss API and webhooksNative SDK / Deep Integration
Native SDK / Deep Integration is an enterprise custom deployment route. It is activated through approved partner onboarding, security review, route configuration, and production approval.
- Best fit: Enterprise partners that need native or deeply embedded Pausier workflows. Organisations that require custom product, security, governance, and release planning before integration.
- Setup requirements: Enterprise product and technical design Private TypeScript SDK scaffold and React Native wrapper target Short-lived partner session token or partner server proxy Platform-specific security and release review Approved SDK or deep-link boundary Support, telemetry, retention, and audit plan
- Security boundary: Native/deep integrations must preserve tenant isolation, minimal data exchange, approved telemetry, support access rules, and safe release controls.
- Commercial model: Contact sales. Setup and monthly platform pricing. Custom enterprise contract.
Discuss native integration