Payment could not be completed
The payment processor reported a failed settlement, so the workspace should not quietly pretend that access is active. Use this view to push the user into a clear retry and recovery path.
Access Path
Retry the upgrade cleanly
Keep the recovery path close to the failed state so the user does not have to guess whether they should go back to pricing, subscription, or a generic locked view.
Recovery routing
Keep billing failures explicit
A failed payment should always leave the workspace with a visible view back into billing instead of trapping the user in an unexplained locked state.
This screen is where support, retry, and invoice detail should converge whenever a payment attempt breaks before confirmation.