beaus-tolling

Integration Blueprint

Integration Thesis

Tolling platforms do not succeed because they have elegant code alone. They succeed because they can connect to messy roadside estates, external agencies, financial partners, identity providers, and operational reporting demands without becoming brittle.

Beaus should treat integration as a product capability.

Core Integration Zones

Roadside

Purpose:

• ingest lane events
• link image evidence
• synchronize operational context between field and backoffice

Pattern:

• Kafka event contracts
• evidence object references
• no shared transactional database

Identity and Access

Purpose:

• workforce sign-in
• role mapping
• application access control

Pattern:

• Azure AD / Entra ID
• gateway-style SSO
• session plus token strategy for UIs and services

Payment Providers

Purpose:

• capture and refund flows
• settlement reference
• payment method token handling

Pattern:

• isolated payment adapters
• idempotent commands
• audit-safe transaction records

DMV and Registration Sources

Purpose:

• owner enrichment
• plate validation
• state-specific operational workflows

Pattern:

• service-specific adapter layer
• throttling and retry controls
• request and response audit history

Collections and Out-of-State Partners

Purpose:

• external exchange
• exception routing
• notice escalation and enforcement support

Pattern:

• integration queues
• contract versioning
• replay and audit capability

Reporting and Executive Consumption

Purpose:

• trusted KPI dashboards
• finance reporting
• compliance packs

Pattern:

• event-fed read models
• export and dashboard APIs
• separation from transactional write stores

Contract Governance

All integrations should follow these rules:

• topic names are versioned
• payloads are explicit
• trace and correlation identifiers are preserved
• ownership of each contract is clear
• breaking changes require version evolution, not silent mutation

Canonical references:

• Back-office contract catalog
• Back-office versioning policy
• Roadside contract registry

Example Topic Families

• roadside.trip.captured.v1
• roadside.device.status.changed.v1
• roadside.image.evidence.received.v1
• trip.posted.v1
• case.created.v1
• payment.captured.v1
• notification.requested.v1

Why Buyers Care

Integration discipline is not just an engineering preference. It directly affects:

• implementation risk
• vendor lock-in
• future extensibility
• confidence in phased rollout

That is why the integration story should be visible in both presales and engineering documentation.