Onboarding outcomes

After the application is submitted, the bank’s pipeline returns one of three outcomes. Each one needs a different response from your product.

Outcome	What happened	What you do
Instant approval	The bank approved automatically. The Organization is live and the deposit account is open.	Route the user into your banking experience. Listen for `bank_account.created` to know when the account is ready.
Manual review	The bank needs more time — usually because something on the application needs a human look.	Tell the user they’ll hear back by email. The application stays `SUBMITTED`; the account materializes later if the review clears.
Denied	The bank declined to open the account. Most often fraud signals or risk policy.	Surface a clear, non-leaky message. Do not retry the same application — denied is terminal for that application.

You learn about the outcome through the bank account lifecycle, not through the application object itself. The application moves from SUBMITTED to COMPLETE when the bank’s pipeline finishes; the resulting bank account’s status carries the actual outcome. See the application lifecycle states for how this maps to API state.

KYB data Overview

⌘I

Getting started

Authentication

Organizations

Users

Bank account applications

Bank accounts

Webhooks

Money movement

Transactions

Embedded components

White-label

Onboarding outcomes