News for hackers. Stuff that matters.
Re:Privacy API: Programmable Payments by igetspam on Thursday July 12, 2018 @03:26PM (#17517809)
I use it for everything.

I have unique/monthly limit cards:

  * My kid's swim class has a unique card.
  * Wife's phone (setup before Google started rejecting their cards)
  * Cable bill
  * Netflix
  * Personal AWS bill
  * Gymboree
  * Monthly self-storage
Recently closed one-time cards:

  * Online grocery order
  * Delivery food order (leave some padding for tip)
  * Online clothing retailers
  * Charitable donations paid via CC
  * Tickets to DisneyWorld
  * Every penny that goes through PayPal because I don't trust them for a second
Literally, anything that we pay for over the phone or online.

One place I'm especially happy to have it is my vet. They're really bad at billing. They've double billed me twice. Now I keep a dead card on file (they want a card) and give them a new one with a hard limit every time I have to pay a bill. No more double billing and I can see when they're screwing up.

Re:Privacy API: Programmable Payments by _eht on Friday July 13, 2018 @01:23AM (#17520698)
Do you have any information on why Google would block these CC numbers? I know Google, and many others block VOIP phone numbers for example, to discourage rampant account verification, but I can't think of why they would reject a financial reference number.
Re:Privacy API: Programmable Payments by kingbirdy on Friday July 13, 2018 @12:33PM (#17524398)
I imagine it's to stop people from connecting stolen cards to the service and then generating a bunch of other card numbers that are essentially all stolen. It could potentially allow them to use the stolen card more before it was detected.