Resend the OTP for the in-flight closure
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/user/accounts/current/close/otp/resend"{ "code": "BAD_REQUEST", "description": "Bad Request"}{ "code": "UNAUTHORISED", "description": "Unauthorised"}{ "code": "WAITING_LIST", "description": "User is in the waiting list"}{ "code": "TOO_MANY_REQUESTS", "description": "Too Many Requests"}{ "code": "INTERNAL_SERVER_ERROR", "description": "Internal Server Error"}Confirm the OTP for the in-flight closure POST
Verifies the code and moves the closure to OTP_CONFIRMED. The custodian bank then reviews the request; the account becomes CLOSED once the closure is approved. Returns 409 ACCOUNT_HAS_NON_ZERO_BALANCE when money arrived after the closure was started — the balance must be withdrawn before the closure can be confirmed. Returns 404 when no closure is in progress.
Start closing the caller's current account POST
Verifies the account is ACTIVE with a zero balance, registers the closure with the custodian bank, and dispatches an OTP to the account holder via SMS. Returns 409 if the balance is not zero, a closure is already in progress, or the account is not in a closable state. After the OTP is confirmed the custodian reviews the request; the account becomes CLOSED only once the custodian approves.