A readiness check is a condition the current workflow evaluates before it can move to the next state. The checks are not identical for every workspace or program. When a payout is blocked, use the status explanation and reason codes attached to that record to find the specific missing item.
Readiness reasons implemented today
- Workspace or identity: the workspace or identity cannot be found, the identity is inactive, or active workspace membership is missing.
- Identity verification: KYC is required for this flow and is not approved yet.
- Payout policy: the workspace does not have the required payout policy or default beneficiary.
- Beneficiary: the beneficiary is missing, unavailable, connected to a different account context, or missing destination details.
Separate status from reason
Status tells you where the instruction is in its lifecycle. A reason explains why it cannot move. For example, Held can include a readiness reason; Pending approval means a reviewer decision is needed; Approved can be ready for a separate execution step; Failed needs its row-level explanation reviewed. Do not fix a pending approval by changing bank data, and do not execute a held item without resolving its reason.
Resolve a blocked item
- Open the payout or Payment Run detail.
- Copy the visible status, status explanation, and reason code.
- Open the named source record: workspace access, Verification, payout policy, beneficiary, or payout method.
- Complete the action on that source record and allow the flow to be evaluated again.
- If it remains blocked, share the payout or batch ID and reason code with the teammate or support owner responsible for that record.
A general support request should include references and visible reason text, not identity files, complete bank details, credentials, or access tokens. Program-specific tax, screening, classification, or legal checks should be documented only from the approved source for that program.