Exchange Deposit Address Expired? First Find Its Actual Lifecycle State

An exchange showing a new deposit address does not automatically mean the previous address is expired. Coinbase Exchange currently keeps previously generated addresses associated with the account, Kraken can explicitly expire deposit addresses, Binance has a retirement process with manual credit for certain old-address deposits, and other exchanges use their own migration rules. Before sending, use the current authenticated deposit details. If you already sent to an old address, stop sending more and prove the exact transaction and the receiving exchange's current address policy.

The first distinction: changed is not the same as expired

An exchange may display a different deposit address because it generated a fresh address, migrated wallet infrastructure, changed an address format or retired an old route. Only the provider can tell you whether the historical destination remains associated with your account. Do not infer expiry from the fact that today's Deposit screen shows a different string.

Use the Deposit Address Lifecycle Fork

Classify the address before deciding what to do.

• CURRENT — the authenticated Deposit screen currently presents this address for the exact asset and network.
• OLD BUT ASSOCIATED — the provider explicitly says historical generated addresses remain linked or valid.
• RETIRING — the provider marks the address for future expiry or asks you to migrate during a grace period.
• EXPIRED — the provider explicitly marks it expired, retired or no longer automatically credited.
• UNSUPPORTED — the address type, network, token route or format is no longer supported.

Then split at the irreversible boundary: before send or after send

Before a blockchain transfer exists, the solution is normally to stop and obtain the current deposit instructions. After the transfer is broadcast, the sender cannot simply edit the destination. The task becomes evidence collection and provider-specific recovery.

BEFORE SEND — use the current authenticated deposit page

Open the receiving exchange directly, select the exact asset and network and generate or display the current deposit destination. Copy the current address and any memo, tag or payment ID from that authenticated screen. Do not use an old screenshot, browser history, email, saved note or withdrawal whitelist as the primary source when a fresh deposit page is available.

Do not send a test to an address explicitly marked expired

A small test is not a safety technique when the exchange already says the destination is expired or unsupported. Kraken, for example, warns that deposits to an expired address are not guaranteed to be credited and may be permanently lost. Use a new current address instead.

A saved withdrawal whitelist should be treated as stale until rechecked

If Exchange A has Exchange B's old deposit address whitelisted, compare it against Exchange B's current Deposit screen before the next withdrawal. Address migrations often fail operationally because the sender's saved address remains unchanged even after the receiver updates its infrastructure.

Address and memo can retire together

Some exchange migrations replace not only the blockchain address but also a memo or tag. Binance's retired-address documentation explicitly refers to deposit addresses and memos on old infrastructure. If the receiving page supplies both components, refresh both rather than combining a new address with an old memo or vice versa.

Coinbase Exchange is an example where changed does not mean expired

Coinbase Exchange currently says most deposit addresses change when a new one is generated, but all previously generated addresses remain associated with the account. Its documentation says deposits sent to an old generated address are processed and credited automatically to the corresponding wallet in the default portfolio.

Coinbase policy is not a universal exchange rule

Do not generalize Coinbase's historical-address behavior to Kraken, Binance, OKX or another platform. A blockchain address can still exist on-chain while the exchange's internal ledger no longer promises automatic attribution to your account.

Kraken is an example of real address expiry

Kraken's current support page says cryptocurrency deposit addresses can expire when more than five addresses are created for the same cryptocurrency or when an address type or format is no longer supported. When more than five are generated, the oldest is set to expire in seven days.

Kraken displays the expiry state before the deadline

Kraken instructs users to open Deposit and Manage deposit addresses, where the remaining days are displayed for an expiring address. An address marked New Address or Used Address is documented as acceptable for deposits; one marked for expiry should be retired from your saved destinations immediately.

Binance uses a retirement model with a separate post-expiry credit path

Binance's current support page says selected old deposit addresses and memos can be retired during wallet-infrastructure upgrades. It instructs affected users to obtain a new address. The page currently states that an old address can expire after the user obtains a new address or after the specified notification window.

An expired Binance deposit is not described as automatic credit

Binance says subsequent deposits to an expired retired address are not automatically credited. Its current procedure points users to One Click Arrival in Transaction History when available, or to the Deposit Status Query route when that option is not shown. That is a provider-specific recovery mechanism, not a promise that every exchange can recover an expired-address deposit.

OKX shows why migration grace periods must be read literally

OKX's current help still references a deposit-address update that began in March 2025 and says previously used addresses remained valid during a transition period while users were told to update saved or whitelisted destinations. A migration-specific grace period should never be turned into a permanent rule that all old OKX addresses remain valid.

AFTER SEND — freeze the evidence before trying recovery

If a transfer has already been broadcast to an old or expired address, do not send another deposit to prove ownership unless the exchange's official recovery process specifically requires it. Record the original transaction first.

Build the Expired-Address Evidence Packet

Collect the fields that let the receiver identify both the blockchain transfer and your account route.

• Receiving exchange and account identifier
• Asset and exact blockchain network
• Transaction hash or TXID
• Confirmed recipient address
• Amount actually transferred on-chain
• Source address or sending platform
• Old deposit address as previously shown by the exchange
• Current deposit address for the same asset and network
• Memo, tag or payment ID used, when applicable
• Approximate date the old address was generated or saved
• Screenshot of any expiry, retirement or address-replacement notice
• Current deposit-history status: detected, missing, pending or credited

Verify the TXID on the correct blockchain

Open the transaction on the explorer for the network actually used. Confirm that it succeeded and that the recipient exactly matches the historical exchange address. If the transaction is still pending, failed, or went to a different address, the expired-address diagnosis is not yet proven.

A successful blockchain transfer proves delivery to the address, not exchange credit

The blockchain can prove that assets reached an address, but a custodial exchange controls the keys and the internal mapping between its addresses and customer balances. The receiving exchange therefore controls whether an old-address deposit is automatically credited, manually credited, recoverable for a fee or unrecoverable.

Compare the old route with the current route field by field

The old and current destination should be compared as a complete route, not only as two address strings.

• Same asset?
• Same blockchain network?
• Same token contract where relevant?
• Same account?
• Was a memo or tag required?
• Was the old address explicitly marked expired or merely replaced?
• Does the exchange still recognize the old address in deposit history or address management?

If the old address is still associated, this may not be an expiry incident

Coinbase Exchange currently documents old generated addresses as remaining associated indefinitely. If the provider explicitly confirms the same behavior for your exact route and the transaction has enough confirmations, move to the general confirmed-but-not-credited investigation rather than continuing to treat the age of the address as the main failure.

If the address was in a grace period, preserve the policy that applied at send time

Migration windows can change. Save the provider announcement, account notice or screenshot that was active when the transfer was sent. If the provider said the historical address remained valid during a defined transition, that evidence belongs in the recovery case.

If the address was expired, use the exchange's named recovery path

Do not ask random social-media support whether they can 'restore' the address. Use the receiving exchange's authenticated recovery tool, deposit-status query or support form. Binance currently documents manual credit for its retired-address process; Bitget has a specific old/expired-address recovery category.

Bitget provides a useful example of the evidence a recovery case needs

Bitget's current old/expired-address guide tells users to compare the used address with the current deposit address, verify the TXID on-chain and submit a recovery request containing the token, blockchain, amount, transaction hash, deposit address and account information. It also warns that manual recovery can involve fees and depends on technical feasibility.

Recovery is not guaranteed just because the exchange once controlled the address

Kraken explicitly says deposits to expired addresses are not guaranteed to be credited and may be permanently lost. Other providers may preserve access to an old wallet but no longer support automated attribution. Never write to support as though blockchain ownership alone creates a guaranteed credit obligation.

Do not confuse expired address with wrong address

An expired exchange address was previously assigned or associated with the receiving service. A completely unrelated recipient address is a different problem. Coinbase's wrong-address guidance emphasizes that blockchain transfers cannot be reversed and recovery depends on the owner of the destination.

Do not confuse expired address with wrong network

A historical address can be correct for one network and useless for another. If the asset was sent over a network the exchange does not support for that deposit route, the recovery problem is network incompatibility rather than simple address expiry.

Do not confuse expired address with missing memo

A shared exchange address can still be valid while the memo or destination tag is missing or wrong. That is an attribution problem with a different recovery path. Use the memo-specific guide when the address itself was supported but the additional routing identifier failed.

Do not send another transaction to 'push' the first deposit through

A second transfer cannot rewrite the first transaction's destination or make an expired address current again. It can create a second recovery case and double the amount at risk. Diagnose the existing TXID first.

Do not accept a replacement deposit address from a direct message

A scammer who sees a public complaint can send a plausible-looking 'new exchange address'. Obtain the current destination only inside the authenticated exchange account or its official support workflow. Support does not need your seed phrase or private key to investigate a custodial deposit.

Recovery economics matter for a small deposit

Manual recovery can require technical work and some exchanges charge a fee. Before pursuing a tiny transfer, read the current recovery terms and compare any disclosed fee with the amount at risk. Do not send a larger 'verification deposit' unless an official, authenticated recovery process explicitly documents such a requirement and you understand the risk.

Use five final lifecycle verdicts

End with a state that determines the next action.

• CURRENT — use the authenticated current route after verifying asset, network and memo.
• OLD BUT ASSOCIATED — provider policy explicitly keeps the historical address linked; verify confirmations and move to normal deposit-credit troubleshooting if needed.
• RETIRING — stop future use and update every saved or whitelisted destination before the deadline.
• EXPIRED, RECOVERY PATH EXISTS — preserve the TXID and use the provider's manual-credit or recovery process.
• EXPIRED / UNSUPPORTED, RECOVERY UNCERTAIN — stop sending, preserve evidence and ask the receiving exchange whether recovery is technically possible; do not promise success.

The practical pre-send checklist

Use this before every exchange deposit that relies on a saved address.

• 1. Open the receiving exchange directly.
• 2. Select the exact asset and network.
• 3. Compare the current address with the saved destination.
• 4. Refresh any memo or tag as well.
• 5. Read any Address Replacement, Retiring or Expiring warning.
• 6. Update withdrawal whitelists and recurring payout destinations.
• 7. Do not test an address explicitly marked expired.

The practical post-send checklist

If the transfer already went to the historical address, use this order.

• 1. Stop additional deposits to that destination.
• 2. Save the TXID and verify success on the correct network.
• 3. Compare the on-chain recipient with the old exchange address.
• 4. Confirm the current address, network and memo in the receiving account.
• 5. Classify the provider policy as associated, grace period, retired or expired.
• 6. Check deposit history for a manual-credit option.
• 7. Submit the provider's official recovery form with the complete evidence packet when required.
• 8. Do not assume recovery until the exchange confirms eligibility.

Why this page is separate from confirmed-but-not-credited

The confirmed-but-not-credited guide starts with a successful on-chain transfer and asks which exchange credit gate failed across confirmations, route support, attribution, ledger processing and review. This page is narrower: the historical deposit address itself is the suspected failure point, and it begins even before a transfer when the user sees that an old address changed or expired.

Why this page is separate from the old wallet-address guide

A self-custody wallet controls addresses through keys, while an exchange controls both the keys and the internal customer-credit policy. The old-wallet-address article decides whether the user still controls a historical address. This page decides whether a custodian still recognizes or can recover a historical deposit route.

What can change after August 8, 2026

Deposit-address migrations, grace periods, expiry rules, self-service recovery tools and fees can change quickly. Coinbase Exchange, Kraken, Binance, OKX and Bitget currently demonstrate different lifecycle policies. Recheck the exact receiving exchange before relying on any historical address.

Sources checked on August 8, 2026

Current exchange documentation was prioritized because address retention and recovery are provider-controlled policies rather than universal blockchain rules.

• Kraken — Cryptocurrency deposit address expiry — https://support.kraken.com/articles/201647713-cryptocurrency-deposit-address-expiry
• Binance — Why Is My Deposit Address Being Retired? — https://www.binance.com/en/support/faq/detail/853aaedc7f45430283abc7a25713c428
• Coinbase Exchange — Why did my crypto address change? — https://help.coinbase.com/en/exchange/managing-my-account/crypto-address-change
• Coinbase Exchange — Generating new deposit addresses — https://help.coinbase.com/en/exchange/crypto-transfers/generating-new-deposit-addresses
• Coinbase Exchange — Deposit missing: sent to wrong address — https://help.coinbase.com/en/exchange/crypto-transfers/sent-to-wrong-address
• OKX — Why hasn't my deposit been credited? — https://www.okx.com/help/why-has-not-my-deposit-been-credited
• OKX — Update on deposit addresses — https://www.okx.com/help/update-on-deposit-addresses
• Bitget — How to Deal with Mis-deposit into Old/Expired Address? — https://www.bitget.com/support/articles/12560603820616

FAQ