All work

Case study 05 / 06

Backend engineering · Event-driven workflows · Integrations

TripSecure+ / Voyager Travel Insurance

ASP.NET Core services and webhook-driven workflows for travel insurance: Cirium flight data for delay and cancellation payouts, database-driven claim rules, S3 document storage and partial-submission state.

Role
Built backend services and integrations (Engineer Trainee)
Company
ICICI Lombard
Stack
  • .NET
  • ASP.NET Core
  • AWS S3
  • Cirium APIs
  • REST APIs
  • Webhooks
TripSecure+: Cirium flight data and webhook events feed ASP.NET Core services that apply database-driven claim rules, store documents in S3 and persist partial submissions.INBOUNDCirium flight dataDELAY · CANCELLATIONWebhook eventsEVENT-DRIVENCustomer submissionMULTI-STEPASP.NET Core servicesCLAIM WORKFLOWClaim rulesDATABASE-DRIVENDocumentsAWS S3Partial stateRESUMABLE→ FLIGHT-DISRUPTION CLAIM PAYOUTSIMPLIFIED, PUBLIC-LEVEL VIEW
Simplified, public-level view of the documented architecture

01

Overview

Backend services for travel-insurance workflows, including flight-delay and cancellation claim payouts driven by external flight data.

02

Context

Claims for flight disruption need trustworthy flight status, supporting documents, and a process that tolerates users leaving and coming back.

03

Problem

Connect flight data, documents and claim rules into a workflow that can react to external events and resume partially completed submissions.

04

My contribution

  • Built ASP.NET Core services and webhook-driven workflows for travel insurance.
  • Integrated Cirium flight data for delay and cancellation claim payouts.
  • Worked with configurable, database-driven claim rules.
  • Used AWS S3 for document storage.
  • Worked on partial-submission and state-persistence workflows.

05

Architecture

Flight events in, claim decisions out

Flight data from Cirium and webhook events feed ASP.NET Core services. Claim rules are read from the database rather than hard-coded, documents are stored in S3, and partially completed submissions persist their state so users can resume.

  • Inbound: Cirium flight data and webhook events.
  • Processing: ASP.NET Core services applying database-driven claim rules.
  • Storage: S3 for documents; persisted state for partial submissions.

06

Impact

  • No numeric outcome is recorded for this work, so none is shown.

Described at a public level — no confidential company, customer or system details.