ICO365 的问题

[Shuxy]

问题解决了！
Problem Fixed.

你好，

首先先让我说我的中文不太好，请理解，谢谢。四天前，我用了Lykke (https://lykke.com) 发送了Ether进我的ICO365的账户。因为Lykke是用Smart Contract来发送那个Ether，ICO365处理不了。所以修然我的钱包里看得见那些Ether，ICO365里却看不见。我写了好几次给ICO365的ZenDesk，可是没人回复。过后，我加入了ICO365的QQ，终于找到了365的员工。

我让她知道了我的问题，还拍了很多截图给她看。我主要的是要我的ICO365的账户能看得见我的钱包里的Ether 。我不知道他们怎么解决，可是他们没问我却发送了我的Ether去多一个不是我的地址！

后来，她们说会发送那些Ether回ICO365的账户，可是我已经等了两天却还没收到。今天早上，ICO365的员工又说是因为我原本发送错，然后她就突然跟我在QQ不是朋友了所以我无法跟她说话。我不知道她怎么做可是我跟她说话的历史也不见了。

https://etherscan.io/address/0x19d2684bd9fc30ccab908417ef0d8225d9312a35 就能看到一切了。

Hi all,

Sorry for the above paragraph, I can speak Mandarin but it's been a long time since I wrote, and my written Mandarin is somewhat off. I'm facing an issue with ICO365 and I hope someone from ICO365 can help. 4 days ago, I sent some Ether from Lykke (https://lykke.com) to my ICO365 Ether Wallet. Lykke sents out Ether using smart contracts, so it shows up as an internal transaction. Unfortunately, while the Ether is in my ICO365 Ether Wallet, ICO365 itself does not reflect that, I can only see it when I check Etherscan.

I wrote in to ICO365 numerous times, but no one responded. In the end, I had to join the QQ Group and finally found a support staff from ICO365 there. All I needed was for them to update my ICO365 account so that it shows the Ether that's in my wallet. However, they decided to refund the Ether, but without first checking with me on the address! In the end, they sent it to some address (that is not mine). Subsequently, they said that they would compensate and send the Ether back to my ICO365 account, and I've been waiting for two days then.

Unfortunately, nothing happened in these two days, and earlier today, it became my fault again for not sending it the right way. I can accept that perhaps sending with Lykke wasn't a good idea (to be fair I love and use Lykke a lot), but I *cannot* accept that they had refunded to the wrong address, without even letting me know that they are going to refund. Actually to make it worse, they sent the 0.2 Ether which I had sent normally back to the wrong address as well. To make it worse, the support staff unfriended me on QQ and I can't even communicate with her now, so I've no choice but to take it here. in addition, it seems that the entire chat history I had with her has been deleted.

All the details can be seen on Etherscan: https://etherscan.io/address/0x19d2684bd9fc30ccab908417ef0d8225d9312a35.

[Oteman_Btc38]

ICO365 will allocate a unique deposit address for you.
Once you deposit to your address, then your balance will update.
The funds will automatically send to an gathered address.

I'm no longer in ICO365, and build my own ICO site www.3ico.com
but i can help you to contact ico365， please tell me your IM contact information.
As you descriped, they refund your funds to wrong address?

365会给每一个用户分配一个地址，只要你转账到那个地址，那么你的账户就会更新余额。
因为资金是需要汇总的，因此你转账到那个充值地址的之后，充值地址的钱会自动汇总到另外一个地址。
 

[Shuxy]

Thank you so much, I really appreciate your help here. I know. I deposited to the address, but because I sent the funds using Lykke, it shows up as an internal transaction. But the funds are in, just that ICO365 was unable to make it show up in my account. I was trying to get them to do that, but instead of doing that, they went to refund it to another address without first checking with me what address to send to .

Initially, they agreed to compensate me, but I've been waiting for 2 days now and suddenly this morning they said they are still trying to "find" the 2.04~ Ether. I told the support staff there is nothing to find, since it was already sent to an incorrect address. The next time I know, she said I was pressuring her and then she unfriended me on QQ (sigh).

My username in ICO365 is also shuxy. IM contact information for which service?

Thanks again.

Update: I just want to add that all I need is for ICO365 to compensate me that 2.04 Ether which they had mistakenly sent to the wrong address, back into my ICO365 account. I can then login to withdraw it myself. Thank you.

Update: The customer support got back to me, it's fixed now !