Google Payments API

#1

Post by emwa » Mon, Oct 23, 2017, 7:47 AM UTC

Google Payments API
developers.google.com

Re: Google Payments API

#2

Post by clintonb » Mon, Oct 23, 2017, 1:49 PM UTC

I've been waiting on this since July, when we implemented Apple Pay at edX. They missed the advertised September deadline. Despite signing up for the mailing list, I have yet to be notified about the functionality. Now that I'm seeing all the press about it, there still seems to be no way to register as a merchant. This is quite disappointing.

Re: Google Payments API

#3

Post by reustle » Mon, Oct 23, 2017, 2:05 PM UTC

clintonb wrote: post #2

I've been waiting on this since July, when we implemented Apple Pay at edX. They missed the advertised September deadline. Despite signing up for the mailing list, I have yet to be notified about the functionality. Now that I'm seeing all the press about it, there still seems to be no way to register as a merchant. This is quite disappointing.

Sounds very... Google-y. I love Google but I don't plan on wasting any of my time integrating with their tech anymore.

Re: Google Payments API

#4

Post by TeeWEE » Mon, Oct 23, 2017, 2:12 PM UTC

How does this relate to Android Pay? Is Android Pay deprecated?

Re: Google Payments API

#5

Post by kyrra » Mon, Oct 23, 2017, 2:28 PM UTC

TeeWEE wrote: post #4

How does this relate to Android Pay? Is Android Pay deprecated?

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...

Re: Google Payments API

#6

Post by wiradikusuma » Mon, Oct 23, 2017, 2:38 PM UTC

Before I get my hopes up.. Is this "only for US" (and a small number of countries)?

Re: Google Payments API

#7

Post by dopamean » Mon, Oct 23, 2017, 2:49 PM UTC

wiradikusuma wrote: post #6

Before I get my hopes up.. Is this "only for US" (and a small number of countries)?

Under the section about the rules

> The following terms apply if you access or use the Google Payment APIs in Central America, South America or China: ...

I'm no lawyer but this seems to imply that it at least includes those regions.

Re: Google Payments API

#8

Post by thesimon » Mon, Oct 23, 2017, 2:49 PM UTC

https://stripe.com/docs/pay-with-google

Looks like Stripe supports it. The name is a bit different, but this is probably just Google being Google.

Re: Google Payments API

#9

Post by revelation » Mon, Oct 23, 2017, 3:10 PM UTC

This must be the 5th Google money API/interface to date. It doesn't seem like they learned from the previous attempts.

Re: Google Payments API

#10

Post by etse » Mon, Oct 23, 2017, 4:05 PM UTC

If the purchase is for digital goods, would it need to be for Google Play in-app billing, whereas if the payment is for physical goods, then it qualifies for Google Payments API?

What does a subscription for a membership for physical and digital goods fall under?

Thanks for the pointers.