3 ms·
> [...] sharing credit card numbers like that was a classic "must not" [...] That's indeed a complete no-go. If they did that, they'd have to keep your CVC on
by ffsm8 3y ago
> [...] sharing credit card numbers like that was a classic "must not" [...]
That's indeed a complete no-go. If they did that, they'd have to keep your CVC on file too, and that would end with them losing their certificate to process credit cards entirely. So that probably didn't happen.
Another way it could've gone down is if the payment provider is unchanged. I.e. Google processed payments through global collect and handed your subscription IDs to square space. Now there is no need to pass credit card information as the collecting party hasn't changed. Only the person triggering the collection.
That's just an example however, I don't work for Google nor am i involved in this migration.
- woodruffw 3y agoThanks, that's a plausible explanation. I would be mildly surprised if Google was using a third-party payment provider for Google Domains, but I don't think I have any way to verify or refute this :-) (I suppose Google could remain the payment processor while handing the operations themselves off to Squarespace, as well.)
- itsdrewmiller 3y agoYou can transfer saved cards between gateways without storing CVVs (or card numbers) yourself - they don't like to do it but if you are a big enough fish they still will.