Integrations and source ownership

• Online application portal. Send submitted applications with the applicant’s reference and documents into new cases.
• Payment gateway and bank. Send payments into pending fee receipts with the gateway reference, then confirm them against the bank.
• National or state vehicle database. Check VIN and plate against the authoritative register before recording a vehicle.
• SMS and email notices. Send document requests, decisions and renewal notices to applicants and owners.
• Identity provider. Map officer sign-in to People records; removing an officer’s access must also remove their platform access.

Each connection needs an agreed source of truth, a field mapping, a stable event identifier and a retry policy. A repeated payment notification must not create a second receipt, and a repeated portal submission must not open a second case. Keep credentials in the approved secret store and grant the smallest scope the connection needs. Queue rejected records with their source identifier and a visible reason.

Test a provider timeout, a duplicate notification and a revoked credential before turning on schedules. Availability depends on each provider’s API, access agreements and configuration.

Use the implementation plan to agree acceptance criteria for each connection.