A held payout has not been released because one or more readiness checks still need attention. Start with the status explanation and reason codes on the payout record. They show what the current flow is waiting for, without making you recreate the payment.
Checks that can hold a payout
- The workspace, identity, or active workspace membership cannot be resolved for the current instruction.
- Identity verification is required for this flow and is not approved.
- A payout policy or default beneficiary has not been configured.
- The beneficiary is missing, cannot be found, belongs to a different account context, or lacks destination details.
Do not confuse held with another status
- Imported means a Payment Run file exists but has not been processed.
- Pending approval means the item is waiting for an approver, not a readiness fix.
- Approved means execution is a separate available action for an authorized role.
- Processing means an initiated operation is still underway.
- Failed or completed with failures needs row-level review before retrying.
What to review next
- Open the payout detail and read the status explanation and reason codes.
- Complete the named readiness item, or send the reason code to the teammate who owns the workspace, identity, payout policy, or beneficiary setup.
- Check the payout again after the underlying record updates. A cleared readiness check allows the flow to be evaluated again. Final approval and execution can still be separate actions.
When you contact support, include the payout ID and the reason code shown on the record. That gives the team a precise place to start.