Fragmented processing
×Multiple forms
×Disconnected documents
×Manual tracking
×Limited visibility
×Complex follow-up
Passagehubproposal · Interactive Technical Proposal
Digital Infrastructure for Cross-Border Vehicle Permit Management
Modernising Cross-Border Vehicle Permit Management
PassageHub provides a secure digital workflow for managing vehicles, owners, authorised drivers, supporting documents, applications, verification, approvals and permit issuance through one auditable platform.
Independent software platform. Configurable for deployment by authorised organisations and agencies.
Applicant-to-permit flowWORKING MODEL
01Applicant
02Vehicle Registration
03Document Submission
04Application
05Officer Verification
06Approval
07Permit Issuance
01 · Executive Summary
One operational record, from first submission to issued permit.
Cross-border permit programmes may coordinate identity, vehicle, ownership, driver, road-tax, insurance, documentation, payment, review, correction, approval and audit requirements. PassageHub consolidates these processes into a unified digital workflow.
Unified permit lifecycle
✓Unified application
✓Centralised records
✓Structured officer workflow
✓Status visibility
✓Complete audit trail
LIVE PROTOTYPENot Just a Proposal.
Not Just a Proposal.
A Working System Exists.
AINNA has already developed an operational PassageHub prototype demonstrating the core permit-management workflow.
https://ainna.bond/passagehub/OPEN PASSAGEHUB DEMO
✓ Vehicle Registration✓ Owner Management✓ Authorised Drivers✓ Road Tax Records✓ Insurance Records✓ Application Workflow✓ Secure Document Upload✓ Officer Review✓ Application Status✓ Permit Issuance✓ Role-Based Access✓ Audit Trail
02 · Operating Model
Three core roles. Deliberate separation of duty.
Access and responsibilities remain distinct across the application and decision process.
Applicant
- Create account
- Register vehicles and ownership
- Add authorised drivers
- Maintain insurance and road tax
- Start and save application drafts
- Upload supporting documents
- Submit and respond to requests
- Monitor status and configured payments
- Download issued permits
Officer
- Review application queue
- Inspect applicant and vehicle information
- Verify supporting documents
- Request additional information
- Return incomplete applications
- Approve or reject applications
- Issue permits
- Maintain review history
Administrator
- Manage users and officers
- Control roles and access
- Maintain master data/catalogues
- Configure payments and settings
- Administer workflows
- Review audit logs
- Provide operational oversight
03 · End-to-End Journey
Thirteen traceable stages across one lifecycle.
Scroll through the lifecycle to progressively activate the proposed operating sequence.
01Account Creation
02Vehicle Registration
03Owner Information
04Authorised Driver
05Insurance
06Road Tax
07Supporting Documents
08Application Submission
09Officer Verification
10Correction / Resubmission if required
11Approval
12Permit Issuance
13Audit Record
04 · Proposed Architecture
Modular by design. Integration-specific by deployment.
The architecture below is proposed for configured deployments. External connections are optional and require the relevant system access, agreements and approvals.
CURRENT INTERFACEApplicant Web / Mobile
COREApplication Layer
CORE MODULESIdentity · Vehicle · Permit Workflow
COREDocument Management
COREOfficer Review Engine
COREApproval / Permit Engine
COREAudit & Notification Layer
DEPLOYMENT LAYERDatabase + Private Storage
04-A · JPJ Data Integration
API requirements for JPJ data verification.
The API endpoints below define the data required for vehicle and owner verification in the Malaysia context. These are integration requirements to be agreed with JPJ — no live connection is active.
Vehicle Registration
Validate registration number, chassis, engine and vehicle type against JPJ vehicle records.
reg_nochassis_noengine_novehicle_typemake_modelcolour
Road Tax (LKM) Status
Confirm active road tax, expiry date and validity for the nominated vehicle.
lkm_noexpiry_datestatusvalid_from
Owner Identity
Verify registered owner identity and ownership record for the vehicle.
owner_namenricownership_statusjoint_owner
Vehicle Category / Class
Return the registered category and class to determine permit eligibility.
categoryclassgross_weightseating_capacity
Summons / Blacklist Check
Check for outstanding summons or restriction status that may block issuance.
summons_outstandingblacklist_flagrestriction_note
Permit History
Reference prior permit and cross-border movement records where relevant.
permit_historylast_issuedexpiry_history
JPJ integration requires a formal data-sharing agreement, API access approval and the deploying organisation's compliance with applicable data-protection and transport regulations. No endpoint is called without authorisation.
04-B · Indonesian Vehicle Data Integration
API requirements for Indonesian vehicle & owner verification.
For the Indonesia side, vehicle and owner records are administered through Samsat (Sistem Administrasi Manunggal Satu Atap) under Korlantas Polri. The endpoints below define the data required — integration is subject to agreement and approval; no live connection is active.
STNK Registration
Validate the vehicle registration certificate (STNK) — number, chassis, engine and type against the Samsat vehicle record.
stnk_nochassis_noengine_novehicle_typemake_modelcolourdomicile_region
PKB / Road Tax Status
Confirm active annual vehicle tax (Pajak Kendaraan Bermotor) and expiry for the nominated vehicle.
pkb_amttax_yearexpiry_datestatuspaid_at
BBNKB (Transfer) Record
Verify transfer-of-ownership (Bea Balik Nama Kendaraan Bermotor) history for ownership validation.
bbnkb_notransfer_dateprevious_ownerownership_status
Owner Identity (NIK)
Verify registered owner identity against the STNK ownership record.
owner_namenikaddressownership_statusjoint_owner
Vehicle Category / Class
Return the registered category, class and technical specs to determine permit eligibility.
categoryclassgross_weightseating_capacityfuel_type
Blokir / Blacklist Check
Check for blocking (blokir), outstanding obligations or restriction status that may block issuance.
blokir_flagrestriction_noteoutstanding_flag
Permit / Movement History
Reference prior cross-border movement or permit records where relevant.
permit_historylast_issuedborder_crossings
Indonesian vehicle data is administered by Samsat under Korlantas Polri. Integration requires formal authorisation and compliance with applicable Indonesian data-protection and transport regulations. No endpoint is called without authorisation.
PASSAGEHUBTRUST CORE
05 · Security & Trust Architecture
Controls aligned to a high-trust workflow.
Role-Based Access Control
Users only access permitted functions.
Private Document Storage
Sensitive uploads are delivered through authorised routes, not public file URLs.
CSRF Protection
Sensitive web actions use token protection.
Authentication & Session Control
Workflows operate through authenticated sessions.
Audit Trail
Important status and administrative activities can be recorded.
Data Segregation
Applicant, officer and administrative permissions remain separated.
Private Deployment Ready
Architecture can support private-cloud, dedicated or controlled network environments.
06 · Auditability
Every important event can leave a trace.
Operational events can be recorded to provide lifecycle traceability, review accountability and a clearer basis for follow-up.
Application history is part of the working prototype. Exact retention, event scope and reporting rules remain configurable for deployment.
Applicant submitted
Documents recorded
Officer opened application
Insurance verified
Additional document requested
Applicant resubmitted
Officer approved
Permit issued
07 · Configurable Platform
Not a rigid one-country product.
The underlying workflow can be configured for different programmes, rules, forms and permit structures.
Cross-Border Vehicle Permits
Commercial Vehicle Permits
Temporary Entry Permits
Fleet Permits
Visitor Vehicle Registration
Special Access Permits
Transport Operator Licensing Workflows
Agency-Specific Permit Applications
08 · Implementation Approach
Controlled progression from discovery to continuous improvement.
Discovery
Requirements · Existing workflow · Stakeholder mapping · Integration requirements
Configuration
Forms · Workflow · Roles · Rules · Permit structure
Integration
Identity · Payment · Vehicle information · Notifications · Available external APIs
Pilot
Controlled users · Officer testing · Security validation · Operational feedback
Deployment
Production environment · Migration · Training · Monitoring
Continuous Improvement
Analytics · Workflow optimisation · Automation · Additional integrations
09 · Proposed Deployment Models
Infrastructure aligned to organisational requirements.
Cloud Deployment
Managed scalable infrastructure.
Private Cloud / VPC
Dedicated controlled environment.
Sovereign / Private Infrastructure
Deployment within infrastructure controlled by the organisation where architecture and regulatory requirements demand it.
Deployment selection, controls and compliance obligations require validation by the deploying organisation. No unverified certification or compliance claim is made.
10 · Platform Extensibility
A stable core with modular capability.
COREPermit
Management
Management
PaymentNotificationsAnalyticsAPI IntegrationQR VerificationDocument VerificationFleet ManagementOfficer DashboardReportingAI Assistance
11 · Optional Future Enhancement
AI assistance, never ungoverned authority.
Potential AI modules may help classify, prioritise, summarise and search authorised records. They are not required for core permit operation.
GOVERNANCE PRINCIPLE AI remains an assistant to the workflow. Final decisions remain configurable according to organisational governance.
12 · Management Dashboard Concept
Operational visibility without fabricated statistics.
The visual below shows proposed metric categories only. It does not represent live production data.
13 · Why PassageHub
Evaluate the platform through evidence, not slides alone.
End-to-End
One workflow across the entire application lifecycle.
Traceable
Important activities can be captured in an audit trail.
Role-Based
Applicants, officers and administrators operate through separated permissions.
Configurable
Workflows can adapt to different permit programmes.
Integration Ready
Designed to accommodate external services and APIs.
Working Prototype
Stakeholders can experience the system rather than evaluating slides alone.
EXPERIENCE THE WORKING PROTOTYPE
Experience PassageHub Before Evaluating the Proposal.
A working prototype is available for stakeholders to explore the platform concept and understand the proposed applicant-to-officer workflow.
LAUNCH LIVE PASSAGEHUB Live Proof of Concept by AINNA NeuralOpsAPPLICATION
VERIFIEDPERMIT READY14 · Proposal / Contact
From Prototype to Deployment
PassageHub provides a foundation that can be adapted to the operational, security, regulatory and integration requirements of the deploying organisation.
Independent Platform Notice
PassageHub is an independently developed software platform and technology demonstrator. It is not affiliated with, endorsed by, or presented as an official system of LTA, OneMotoring, JPJ or any government authority. Actual deployment and integration requirements are subject to the requirements and approval of the relevant organisation or authority.
