Payment Request API

#1

Post by petethomas » Sun, Sep 17, 2017, 11:53 PM UTC

Payment Request API
w3.org

Re: Payment Request API

#2

Post by aerovistae » Mon, Sep 18, 2017, 12:23 AM UTC

Wonder how this impacts Stripe

Re: Payment Request API

#3

Post by angersock » Mon, Sep 18, 2017, 12:24 AM UTC

Odd that none of the editors are, you know, actually from companies that do meaningful e-commerce. I'd be a lot more interested if it was obvious that folks like Amazon, Stripe, Paypal, Braintree, Ebay, etc. were working on this.

I'm also wary of an API that tries to be all things to all people--as evidenced by the shoehorning in of shipping and delivery options.

EDIT:

Also, we see stuff like so:

> The PaymentRequest API does not directly support encryption of data fields. Individual payment methods may choose to include support for encrypted data but it is not mandatory that all payment methods support this.

What problem is this solving again? How does this make developers' lives easier than existing solutions? I'm kinda thinking it doesn't.

Re: Payment Request API

#4

Post by baybal2 » Mon, Sep 18, 2017, 12:24 AM UTC

Why do we need to put a payment api into a browser?

Re: Payment Request API

#5

Post by litzer » Mon, Sep 18, 2017, 12:27 AM UTC

For anyone else like me who was overwhelmed by all the information and just looking for summaries:

"In one sentence, how does it work?

Payment Request API enables a user to complete a transaction more easily by reusing information stored in the browser or third party payment apps."

https://github.com/w3c/payment-request-info/wiki/FAQ

Re: Payment Request API

#6

Post by stablemap » Mon, Sep 18, 2017, 12:30 AM UTC

litzer wrote: post #5

For anyone else like me who was overwhelmed by all the information and just looking for summaries: "In one sentence, how does it work? Payment Request API enables a user to complete a transaction more easily by reusing information stored in the browser or third party payment apps." https://github.com/w3c/payment-request-info/wiki/FAQ

Maybe this helps too:

https://developers.google.com/web/fundamentals/discovery-and...

Re: Payment Request API

#7

Post by always_good » Mon, Sep 18, 2017, 12:31 AM UTC

baybal2 wrote: post #4

Why do we need to put a payment api into a browser?

To make impulse buys easier.

Re: Payment Request API

#8

Post by Gaelan » Mon, Sep 18, 2017, 12:31 AM UTC

aerovistae wrote: post #2

Wonder how this impacts Stripe

I'm pretty sure it doesn't. It would just let Stripe add a "use credit card data from your browser" button that avoided making users type it in every time.

Re: Payment Request API

#9

Post by tehlike » Mon, Sep 18, 2017, 12:35 AM UTC

aerovistae wrote: post #2

Wonder how this impacts Stripe

"At a high level, the API affects the front end (checkout), not back end. Therefore, merchant's should not have to make changes to backend processing of various payment methods."

Re: Payment Request API

#10

Post by rictic » Mon, Sep 18, 2017, 12:38 AM UTC

angersock wrote: post #3

Odd that none of the editors are, you know, actually from companies that do meaningful e-commerce. I'd be a lot more interested if it was obvious that folks like Amazon, Stripe, Paypal, Braintree, Ebay, etc. were working on this. I'm also wary of an API that tries to be all things to all people--as evidenced by the shoehorning in of shipping and delivery options. EDIT: Also, we see stuff like so: > The PaymentRequest…

The problem it solves is reducing friction on checkout.

For a super quick gist, watch 15 seconds of this video starting at this time: https://youtu.be/NDZw7vtoYnU?t=514