Deposit authorization status

Code	Status	Description	Remarks
0	INIT	The deposit session has been created via /deposit/initiate, but the user has not yet opened the Binance App or taken any action.	Partner should continue polling /deposit/authorization.
1	AUTHORIZED	The user has authorized in the Binance App. Deposit addresses for all requested networks are available.	Terminal state. depositAddresses will be populated in the response.
2	REJECTED	The user explicitly rejected the authorization request in the Binance App.	Terminal state. Partner may call /deposit/initiate again with a new externalOrderId.
3	EXPIRED	The authorization window has expired without any user action.	Terminal state. Partner should call /deposit/initiate again with a new externalOrderId.

How deposit authorization status transitions

                          +---> AUTHORIZED (1) --- terminal
                          |
INIT (0) -----> user action
                          |
                          +---> REJECTED (2)   --- terminal
                          |
         (no action, time passes)
                          |
                          +---> EXPIRED (3)    --- terminal

Notes:

• All transitions from INIT are one-way. Once a deposit session reaches AUTHORIZED, REJECTED, or EXPIRED, it cannot be changed.
• If the deposit session is REJECTED or EXPIRED, the Partner should create a new deposit session by calling /deposit/initiate with a new externalOrderId.
• The AUTHORIZED state is permanent — deposit addresses for a given user + coin + network combination do not change. Multiple authorization sessions for the same user and network will return the same address.