I bought a phone from a large retailer here in the UK and they shipped a faulty unit. These things happen, so I return it for a refund and they got it on 6th Aug: Image
They had no other phones of the same spec anyway so they said they were going to refund me. By 13th Aug, still no refund. Image
I chased a couple more times and by 14th Sep, still no refund! They say it will now take them 3-5 days to issue a refund: Image
Of course, I'm not happy with this and the response is that it will still be 3-5 days for a refund: Image
I waited the full 5 days and guess what, no refund! I opened a PayPal dispute to get my money back (because I paid via PayPal) and 2 weeks later they tell me they now won't refund me unless I close the PayPal dispute: Image
If I close the PayPal dispute it gets marked resolved and then I have no protection whatsoever to try to claim again, but they are refusing to refund me unless I resolve the dispute. What are my next steps? Image
Thanks everyone for the comments/suggetions! My concern with going to my card provider (Amex) and doing a chargeback is that it went through my PayPal account for payment and I've read it can cause issues for your account, which gives me cause to hesitate on that option.
I've decided to escalate with PayPal as the retailer is trying to bypass the resolution process and as pointed out to me, they've said they'd refund me twice and haven't, so I don't have much faith they will do it this time! Image
I also just noticed they have responded on the PayPal dispute to apologise and say they'd issued a refund 13 days ago, so that makes three times! Image
Somebody copied the company CEO in to this thread (thanks!) and he said he'd have someone look at it right away. True to their word, this is now resolved. Image
I hope the attention brought to this results in better handling by the company for future customers who may find themselves in the same situation but not be lucky enough to have a social media following.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Scott Helme

Scott Helme Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @Scott_Helme

29 Sep
🚨🚨🚨 5 minutes until the Let's Encrypt R3 intermediate expires 🚨🚨🚨

29 September 2021 19:21:40 UTC
TANGO DOWN 😅
Are we still here?
Read 57 tweets
29 Sep
Working with @spazef0rze is never dull... 🤣 Image
Sadly, this change did not pass our stringent review process. Image
Well.... I really did ask for this didn't I... 🤣🤣 Image
Read 4 tweets
23 Aug
Are you using CSP on your website? You might be getting a patent infringement notice! Buckle up 😎 scotthelme.co.uk/i-turned-on-cs…
We're already working with the @EFF who will hopefully be able to support the cause here, but we need to know about other websites that have received this letter.
If you're legally and/or technically minded, perhaps you could take a look over the letter being sent out: drive.google.com/file/d/1p63IJ6…
Read 21 tweets
16 Nov 20
@BritishGasHelp @srobertson92 A few things to help you out from your friendly British security researcher:

1) Shorter passwords are easier to remember which is what makes them weak and easy to guess. This means it's more likely someone else will have access to it, not less likely.
@BritishGasHelp @srobertson92 2) Allowing someone to have an easy to remember 8-10 character password doesn't mean you need to prevent someone else from having an ultra-secure 64 character password. It's possible for both of these things to coexist, and they should.
@BritishGasHelp @srobertson92 3) Weak passwords do not protect customer data, they do the opposite and put customer data at risk. We should be encouraging stronger passwords and the use of password managers.
Read 7 tweets
16 Nov 20
There's been a lot of discussion about OCSP again recently after the Apple incident caused by Big Sur. I've written up some details about what happened and thoughts for what we could/should do about it: scotthelme.co.uk/deja-vu-macos-…
Apple published a support article to address the concerns raised, here are the details and my update based on their comments: scotthelme.co.uk/deja-vu-macos-…
Apple will introduce "A new encrypted protocol for Developer ID certificate revocation checks" but are we talking OCSP over HTTPS or something else?
Read 5 tweets
2 Sep 20
I'm not sure what's more worrying, that CAs have continued to issue certificates for >398 days or that I'm not surprised that it's happened... 🤷‍♂️
Imagine buying a new certificate that looks like this!
NET::ERR_CERT_VALIDITY_TOO_LONG
Here's the certificate, they definitely missed the deadline:
Validity
Not Before: Sep 1 00:16:16 2020 GMT
Not After : Sep 1 00:16:16 2022 GMT

crt.sh/?id=3318010380
Read 9 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(