eVisa Platform Integration
Unified, secure online visa applications with automated validation, SLAs, and status transparency.
Overview
Multiple embassies and agencies required a single, secure intake that adapts to changing rules. I implemented a centralized workflow with rule-based validations, document handling, and proactive notifications across the submission lifecycle.
Problems We Solved
Approach
- Schema-driven intake
- Destination-specific forms generated from versioned JSON schemas; conditional logic per rule set.
- Validation + documents
- Client and server validation; virus scan; image/PDF normalization; checksum dedupe.
- Status and SLAs
- State machine with timers for review/approval/issue; notifications by email/SMS/webhooks.
- Audit & compliance
- Immutable event log; redaction policies; export for regulators and partners.
Reference Architecture
- Next.js frontends (public portal + back office)
- Node/TypeScript services with workflow engine
- Object storage for documents; signed URLs; AV scanning
- Queue workers for long-running tasks (OCR, checks, batch exports)
Outcomes
- 38–52% faster end-to-end processing time
- 31% fewer rejections due to document or field errors
- 45% drop in “status” support tickets after self-serve tracking
Key Metrics
| Metric | Before | After | Delta |
|---|---|---|---|
| Time to decision | 6.1d | 3.4d | −44% |
| Rejection rate | 19% | 13% | −31% |
| Status-related tickets | — | — | −45% |
Delivery Timeline
- Discovery: 1 week
- MVP with 3 destinations: 3–4 weeks
- Hardening + additional destinations: 3–6 weeks
Stack
- Next.js, Node/TypeScript
- Postgres, Redis, S3-compatible storage
- Queues + webhooks, OpenTelemetry, structured logs
Want to modernize your application intake and cut processing time? Let’s align on your first 2–3 destinations and ship an MVP.
