Statuses and Outcomes

Every Journey Application has a status that describes where it currently is in the Journey lifecycle. When the application reaches a terminal state, Alloy assigns an outcome that represents the final decision. Together, these two fields tell your integration what just happened and what (if anything) needs to happen next.

Core concepts

In-progress status - The application is moving through the Journey but hasn't terminated.
- Includes pending_step_up, waiting_review, pending_action, data_request_evaluation, pending_journey_application_review, etc.
Terminal status - The application has stopped progressing.
- Options are completed (successful path) and error (unexpected failure).
Complete outcome - The final decision, populated only when status is completed.
- Common values: Approved and Denied.
Entity Application status - For multi-entity applications, each entity has its own status. The top-level status is derived from a hierarchy across all entity statuses.

How it works

A Journey Application's status changes as it progresses through the configured Journey. Some statuses are in-progress (the Journey is still running or waiting on an external input) and others are terminal (decisioning is complete).

Alloy emits a webhook event for every status change. Your integration should react to status changes via webhook rather than polling.

The complete_outcome field is populated only when status is completed. It represents the Journey's final decision and typically drives your downstream account-opening flow.

When to use it

Understand statuses and outcomes any time you're handling Journey Application responses or webhooks. Your integration logic for "what to do next" is driven entirely by the current status.

For exact status definitions and the full transition table, see Reference: Journey Application statuses .

How it fits in Alloy

Every Journeys webhook event and every response from the Journeys API carries a status and outcome. Your integration logic branches on these values.