The application lifecycle
From collection to a released result, with clear ownership of every transition.
On this page
Keep four kinds of state separate
An order is the commercial grouping. A case is one traveler’s application for a product. Financial settlement and delivery have their own lifecycles.
A visa-issued decision does not prove a result has been delivered. A cancelled case does not prove a refund has completed.
Read case stages as milestones
| Stage | What your application should explain |
|---|---|
| inCollection | Information, evidence, and initial payment may still be needed. |
| submitted | Wincora has accepted the application for fulfillment. |
| inReview / inFulfillment | Staff or configured automation is processing the case. |
| filed | A filing fact has been recorded with the authority. |
| additionalInfoRequested | The traveler needs to provide further information. |
| visaIssued / visaRejected | An authority outcome has been recorded. Check delivery separately. |
| cancelled | Case work has been cancelled. Check financial follow-up separately. |
Render the next action, not just a badge
Use nextActions and customer-safe blocking reasons to make status useful. Show what is required, who needs to act, and the permitted next step.
Wincora owns fulfillment progression. Your integration sends typed commands and records authorized facts; it does not set an arbitrary case status.
Release results deliberately
List the case’s released deliverables. Request a fresh download grant when a permitted user opens a file.
Do not save a temporary download URL as the permanent artifact address, or put a download grant into notifications or analytics.
Deliverables reference