Move bindings, then disconnect or discard a connection
What It Does
Closing an account requires resolving every current routing reference first. Administrators can move active bindings individually, then request final disconnection. An unfinished first setup can instead be discarded through the same endpoint.
The Flow
When Something Fails
Display the service’s lifecycle refusal. The account remains open on refusal. Return actionable binding details with the conflict. No binding is silently removed. Report each validation failure. Bindings that fail validation remain on their original account. Return refusals alongside successful moves. Partial movement is possible, and invalid bindings remain unmoved. Reject any binding added or still present since the move. The account stays open until references are resolved. A database error rolls back the database transition. Secret deletion is an external follow-up and does not share database rollback.
Open Design Questions
Invalid current bindings block disconnection but do not participate in the active-binding move. The account-closing journey must make that remaining work clear.