For the second method aka legacy wallet, there is no wallet file, but rather wallet-index.js file and still, the Response tab does not have any payloads.
I confirm I DO NOT have any json file.
You can refer to one of my previous reply for the latest method of getting the correct payload.
Basically, you'll need to know your Wallet_ID and monitor your browser's Developer Menu's Network tab (
should be open before the login attempt and email verification).
Then, your wallet.aes.json's payload should be in the list named as your Wallet_ID at the correct timeframe after you verified your device/IP via Email verification and/or 2FA.
Actual Example (
open in new tab to view full size):
https://www.talkimg.com/images/2025/07/17/UA6D0w.pngIt still works even provided with a random password.
However, downloading the wallet.aes.json is quite unrelated to the issue like I mentioned before because you know your password
and the private keys that you would've exported is still available in their client since it's using the same wallet.aes.json file.
It worth considering if you want to make sure that it's not caused by a bug in their online client though.
As for the possible solution, I'd still stand on my first reply.
I do not have any emails from Blockchain.info from back then.
Thanks.
