-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Top Up issue back again full force #526
Comments
Same issue here, quite annoying. Have they refunded users / credited the accounts automatically when this was an issue in the past? |
2 days and no word on this issue from anyone is insane, I just tried again and lost more money. What an unreliable service. |
@CODJointOps Please give me your Mysterium ID. I will approve payment immediately |
0xba75a9c7b14b485d0571094577c9307b44197d63 |
Nothing? It's almost been a WEEK since I made my purchase and got nothing in return. |
Y'all really just a bunch of scammers huh 😂. "immediately". |
you guys are such scammers, why aren't you giving people what they paid for |
Describe the bug
User tries to top-up for MYST using crypto, or google.
To Reproduce
Steps to reproduce the behavior:
Go to Wallet
Click Top-up
Select Currency
Select the amount
Click the Start payment button
Send payment to the mentioned address,
Expected behavior
Wallet balance should increase to the amount which was purchased.
Screenshots
Desktop (please complete the following information):
OS: [e.g. Windows 10]
App Version [e.g. 4.1.0]
Additional context
Mysterium Ids who faced this issue and coingate links (when user does not know ID):
0x4b0070b110ef2587cba310d39225cf97264732fc
0x71c2516da944e9c71ec86f35655eb6e823294e64
0x2e998981e507adfe48fb71782054c907e85344d5
0x2e998981e507adfe48fb71782054c907e85344d5
0x65a47d8ab4099ecedf5b3d131d75aa8609a1803f
0x0313bfd1ba12860619403ba637baf05790256759
0x398cd8a90a868c3fd27914bef7f6e05e75392ebd
0x1aa5cb40e606f11b32c8d96e34d50c10aa16f54f
0x7a96372968f4d6aca996477f30930934f7f99feb
0xca846866d22f3b3c99064daa131dd37d031bee0c
0x0313bfd1ba12860619403ba637baf05790256759
The text was updated successfully, but these errors were encountered: