northwestern_scent_7270

On our verification system we do have the ability to replace the number if not working, have you used this functionality? We also have automatic refunds if paid by card, if by crypto its unfortunately manual. I would be happy to refund you if you wish, please contact us via our support channels.

Hey, We've been suffering from a lack of numbers recently, which is probably why you've received the same number (we've had a bug). Good news is that we have been now able to acquire more numbers, which means that our verification service has been improved significantly, that being said, if you wish I can also provide a refund for your session, please message us via our support help page in the dashboard.

Hey, We've been suffering from a lack of numbers recently, which is probably why you've received the same number (we've had a bug). Good news is that we have been now able to acquire more numbers, which means that our verification service has been improved significantly. We do explain that the verification session is 30 minutes (we've actually increased it from 20 minutes to 30 minutes, with 20 minutes being quite standard). If you wish, I can also provide a refund for your session, please message us via our support help page in the dashboard. Please let me know, thanks!

Hi, thank you for the feedback! We do want to flag that both issues you've mentioned are covered by notices we have actively displayed in-app and on our website, the number issue is UK-specific and temporary, and numbers from other countries should be available as normal. Email forwarding is currently in beta, meaning it can be intermittently unavailable, which we also communicate upfront. We're sorry the experience was frustrating, and we'd genuinely love to help get things sorted for you, please feel free to reach out to our support team.

I just wanted to reply here and say that we have successfully helped this customer with their payment issue, unfortunately our guest system that was implemented yesterday didn't account for all cases and shown wrong XMR transaction amount where it didn't include the transaction fee, this caused the payment process to get stuck even though our Monero instance returned that the payment was detected and had 40/10 confirmations it wouldn't let it through as the payment complete status was false due to unknown to the customer transaction fee (pico amounts). We've modified the process now to process all new transactions with the correct amount and also allow any payments made before to go through as well. As for the other suggestions, I'll let our team know and put it in the pipeline to be improved or fixed. Thanks!