Skip to main content
An application moves through seven states, from the issuer’s first draft to your decision. This page is the reference for reviewers and admins who need to know what each state means, who can change it and what happens next.

Key concepts

How it works

The Compliance Hub labels a declined application Denied. Earlier versions of these docs called it Rejected. It’s the same state.

State reference

Transition rules

The Compliance Hub checks each action against the current state. An action outside these rules fails with Invalid application state for this operation.

Multi-step approval

Approve doesn’t always end the review. If the form’s approval workflow lists several approvers, each Approve marks the current approver done and assigns the next active one. The application stays In Review until the last approver approves. Then it becomes Approved and the credential is issued.

Worked example

An issuer submits a Digital Asset License application. It enters Pending Review and the workflow assigns your first approver, a Reviewer. They click Accept, so it moves to In Review. They spot a missing reserve report and click Request for information. The state becomes Request for Info. The issuer adds the report, which puts the application back in Draft, and resubmits. It returns to Pending Review, the Reviewer accepts and approves it. The workflow assigns the second approver, an Organization Admin. They click Approve, the state becomes Approved and the credential is issued.

Errors and troubleshooting

FAQ

Yes, within limits. You can approve a Denied application, and decline or request information on an Approved one. You must be the assigned reviewer.
Filing forms issue their credential when the issuer submits. They go straight from Draft to Approved. Use an application form if you need to review first.
No. You archive it instead. Regulators can archive Denied applications. Issuers can archive their own Draft.
It’s a filter, not a state. It shows applications in Pending Review or In Review together.