Deposit APIs
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
Code
Notes:
- All transitions from
INITare one-way. Once a deposit session reachesAUTHORIZED,REJECTED, orEXPIRED, it cannot be changed.- If the deposit session is
REJECTEDorEXPIRED, the Partner should create a new deposit session by calling/deposit/initiatewith a newexternalOrderId.- The
AUTHORIZEDstate 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.
Was this page helpful?
Last modified on