| This is an implementation of the W3 Payment Request spec I believe: https://www.w3.org/TR/payment-request/ They talked about it at Google I/O earlier this year: https://www.youtube.com/watch?v=hU89pPBmhds (I believe this is how it works, I could totally be wrong here, I haven't read on it too much). This is a way of using forms of payments people have stored with Google (cards added for Play store, android pay, or other services) to pay for things with from merchants. The payments don't route through Google, rather it pulls the card details from Google and send them to whatever merchant you are buying from. EDIT: This is useful: https://developers.google.com/payments/mobile-web-tutorial It looks like websites can request data back as a Gateway_Token (to then run through Adyen, Stripe, Braintree, or Vantiv). Or you can setup a public/private pair[0] and Google will send the card details back of as an encrypted bundle that you can decrypt in a PCI compliant environment. (disclaimer: I work on payments at Google, opinions are my own. I didn't work on this feature and don't really know anything about it). [0] https://developers.google.com/payments/payment-data-cryptogr... |