When I tried logging into my Crypto.com account, I kept receiving the message: "Sorry, there was an issue processing your request. Please try again later or contact s******@crypto.com." I decided to delete the app and reinstall it, but now it won’t accept my account credentials at all. This is incredibly frustrating, especially since I have funds in the account. I expect Crypto.com to resolve this issue immediately and restore my access. It’s unacceptable for a financial platform to fail this way, leaving users without access to their own money. I urge Crypto.com to fix this and provide a clear explanation for the problem. This situation has shaken my trust in their reliability.
I've been unable to access my Crypto.com account for a whole month now. I've sent 10 emails to customer support, but it seems like no one has been abl...
Crypto.com’s payment system is incredibly frustrating and poorly managed. I attempted to process a payment, but they claimed the transaction failed because I didn’t include my email in the explanation field. The funds were deducted but added back to my balance, forcing me to repeat the transaction. ...
Until yesterday, I had no issues accessing my Freebitco.in account. Everything was working smoothly. However, right after I submitted a withdrawal request, the platform suddenly logged me out and now refuses to let me log back in. I keep getting an error saying "information error," and despite multi...
I am a customer of Crypto.com and have been regularly sending money without any issues. My account is active, and all necessary verifications have been completed. However, when I needed to withdraw funds (USDT) last Saturday, my account would not allow it. It keeps prompting me to contact support. I...
I’m currently unable to access my Crypto.com exchange account because my Google Authenticator app was deleted, and now I can’t provide the required 2FA code. I’ve already submitted a video verification to customer support, but I haven’t received a response yet. This is causing a significant delay, a...
Comments