[rachel_lithic]

I hear you on this. We’re really sorry for the inconvenience. Unfortunately, this wasn’t fully within our control. To stay compliant with our bank partner’s requirements and network rules we were forced to make this change to existing Visa cards too.

We did explore the card updater[1] and were hoping to be able to use it. Unfortunately it’s not a viable option due to technical limitations. If we could do the updating for you we absolutely would! If you have questions or there's anything we can help with, please reach out to [e-mail]

[1] https://developer.visa.com/capabilities/vau

[dabber]

It's always great to see candid comments like these from the people involved. I appreciate you all and I know I'm not alone.

[troydavis]

Why couch this as an "Exciting Update,"[1] then? Why do none of the FAQ entries[2] answer the obvious question that everyone asked here (why deprecate existing cards, let alone in 3 weeks)?

When forced to by customers, you sort of answered it here, but without details or transparency. The Web site FAQ doesn't even do that much - the question that every single customer will ask isn't listed. Needing to update dozens of cards and merchants for zero benefit is not an "Exciting Update" and Privacy ends up sounding dishonest and, well, stupid for claiming that.

If you were forced to do this by a processing partner, then that's what the FAQ and customer-facing popup should say (and explain why and why your partner agreements allow that with only a few weeks of notice).

I went from being a customer and fan to believing that I can't trust Privacy's decisions nor that those decisions will be described transparently.

[1]: https://support.privacy.com/hc/en-us/categories/441448782555... [2]: https://support.privacy.com/hc/en-us/sections/4414521336855-...

[greyface-]

Can you provide more detail on the partner requirement that forced this?

[bradknowles]

I have hundreds of cards.

I have heard nothing of this problem until now.

Still nothing in the app.

WTF?!?