In my experience even that can fail. I had a card number stolen from them, charged to the tune of $200+, and their support refused to even entertain the idea of it being fraud, and when I mentioned a chargeback they basically said "we don't do those, because we have contracts with vendors."
A payment stop at the bank sure worked though.
I'm curious, how did this happen specifically? In my experience, all privacy.com virtual cards default to being merchant-locked to the first place you use them. Did the merchant run an unauthorized transaction on the card?
I've had online payment info compromised once, and privacy.com caught it cold (and also clearly demonstrated that the vendor had mishandled the payment info, despite claiming otherwise).
This was during a big wave of unauthorized activity being attempted on their cards as well, a lot of friends reported blocked charges for random amounts at like a retirement/hospice home(?) at the time.
This was like 3+ years ago, and my only guess now (read: can't remember if this is true) is that the card had never been charged to the merchant, only pre-authed. But even then I'd expect the pre-auth to lock it to a merchant.
0. https://blog.privacy.com/a-different-type-of-card-fraud-anat...
Maybe they think that not sending me to collections after I stopped the payment at the bank and closed my account is "being made whole."
Honestly I'm still confused by the whole thing.
I told them that it was a fraudulent transaction that I didn't approve, they then kept asking me for tracking numbers and finally closed the support ticket, and would close any further ones instantly on me with this reply.
https://i.imgur.com/EyjCGiU.png
Never mind the fact that it was a completely separate issue than what they would keep replying to me about, the fact that they included the line of
> At this point, the only possibility is that the shipment was stolen after the delivery. This is no longer a case where the merchant is at fault. Hence, the case would be concluded in the merchant's favor.
is a complete disregard for visa's rules. The fact that they wouldn't even let me open a dispute is the biggest factor of "wtf" here to me.
Visa is probably easier to deal with in the case of fraud than what it sounds like privacy.com is like.
I use a single CC for everything (that I'm willing to pay with a CC for.) It's been compromised to the point that charges went through 2-3 times over the past decade and a half. CC company caught the fraud each time, automatically charged-back each of the fraudulent transactions, and overnighted me a new card. They also moved all of my recurring charges to my new card (somehow.) From what I understand, all of the big 4 CC companies operate more or less the same in this regard.
This thread has eliminated the chance of me using Privacy.com in the future. If they can't make dealing with fraud at least as easy as a regular CC (which is quite painless, there's no reason to use them.
But I end up having to cancel and get a new credit or debit card about once a year. And this actually is really inconvenient, when you think of all the places you have stored a CC that have to be updated.
I guess my bank doesn't do automatic updates of any recurring subscriptions, I've always had to deal with it manually. (And in charitable contributions, amazon, paypal, stripe, grubhub, etc etc etc).
That was making me consider privacy.com instead... but if I'm doing it cause of that fraud inconvenience, which right now is just an inconvenience which I have no worry whatsoever would result in actual $$ (cause it's happened so many times now and it's never even been a threat), and switching to privacy.com may eliminate having to update card numbers everywhere when fraud happens but actually increases my risk of actually being out the $$ (or increases the amount of time I have to spend dealing or fighting with customer service or fraud recovery support anywhere) -- forget it.
If you're curious about how this works, read up on "Visa Account Updater".
My concern wasn't that Privacy.com knows who is using their service, but with rather how they choose to know that information through a third party (Onfido) and how terrible Onfido's privacy policy is.
Paddle has no excuse for collecting selfies, they are providing services to businesses that can be verified in more humane and secure ways, such as an electronic signature.
Verifying people with selfies is a degrading and insecure practice, especially when you encounter Onfido during the installation process of a bank's app that you already have an account with, opened in person at a local branch in the EU. This bank also asks you to create a video of yourself and submit your speech to configure their mobile banking app. I'm sure the data will be useful for someone when Onfido eventually gets hacked, or just sells your biometric data.
My hope is that biometric data collection for online account verification will become illegal once all EU member states have intoduced electronic IDs which have an NFC chip. The verification should consist of a person holding their ID next to their phone, and the online service would only receive the minimum amount of personal data to complete the verification.
The image of your face and the image (NFC capture) of your ID are stored to prove to auditors that you were indeed verified to required standards.
No one wants your mugshot, it’s a legal requirement they are having to satisfy.
KYC checks are already being tested with electronic IDs, and the identity of the customer is verified by the presence of a government ID, and the input of a PIN. No selfies or similar farces are involved.
"As part of a business transfer. Onfido may disclose your personal information to an actual or potential buyer, investor or partner (and its agents and advisers) in relation to any actual or proposed divestiture, merger, acquisition, joint venture, bankruptcy, dissolution, reorganization, or any other similar transaction or proceeding"
All I remember is using the plaid bank API which is itself probably very dangerous and a poor decision to allow.
I've used privacy.com for years. Never had an issue. Never had to validate my identity. Never had any issues with support. If used as prescribed (setting limits on cards etc) it fits in directly to where it belongs in my threat model.
What a strangely charged article.
I'm not sure what you want privacy.com to do differently.
This seems like a larger security/privacy surface area than the latter approach.
Privacy.com don't have to use Onfido, there are other options out there. There could be a myriad of reasons why they chose Onfido over the competition but the TOS bind the privacy.com users and they don't offer any alternative.
For a company leaning on "privacy" as their primary marketing tool, this is a double standard. It doesn't mean Privacy.com is a bad company with horrible people building a terrible product. They're just calling out a company for doing something seemingly opposite to their marketing, and saying that's why they personally aren't using the product.
You can disagree with OP but doesn't make their point wrong, invalid, or stupid.
If your contractor chooses a bad subcontractor, who do you blame?
This IS a privacy enhancement in many cases.
If there’s a better option for this use case I’m all ears, though. Reading sibling comments that Privacy won’t actually stop charges past set limits is disconcerting.
What merchants out there are cross-correlating credit card numbers to deanonymize people? Can you even do it in a way that's PCI compliant? If you're actually interested in preventing random merchants from tracking you, I think credit card numbers are the least of your worries. Your billing/shipping information, which is almost always collected is much more revealing about you and can't be anonymized. Given this I do think the name of "privacy".com is misleading. At best it's stopunauthorizedcharges.com.
It's mostly about hiding the fact that the same person, you, are paying to merchant A and merchant B. It allows you to easily have a card per merchant, and lock it to the merchant so that when its number is stolen, it can't be used anywhere else.
The domain name is a bit lofty, yes.