01
Travel entry platform
A traveller needs a different government form for every destination. Nothing may be recorded until the money clears.
6destination workflows live in production
- 1Traveller picks a destination
- 2Rules engine shows only the fields that apply
- 3Payment clears first
- 4Application recorded once, reconciled by cron
- 5Encrypted PII, signed document links
Details
Problem. Travellers need a different government form for every destination, each with its own fields, fees and eligibility rules. Originally scoped for tourist visas, the product now runs as an arrival-card system.
My part. Owned it end to end. A payment-first submission model so an application is only recorded once payment clears, made idempotent across the webhook, the return page and a cron reconciler. PII encrypted at rest with AES-256-GCM, documents behind short-lived signed URLs, uploads scanned by magic byte. Ran the QA cycle: test, file, fix, deploy, verify, close.
Outcome. Live in production with multiple destination workflows enabled.





