Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30) from mattsaxon on 2015-12-23 (public-payments-wg@w3.org from December 2015)

From: mattsaxon <notifications@github.com>
Date: Wed, 23 Dec 2015 02:49:09 -0800
To: WICG/paymentrequest <paymentrequest@noreply.github.com>
Cc: webpayments <public-payments-wg@w3.org>
Message-ID: <WICG/paymentrequest/issues/30/166861535@github.com>

> @mattsaxon and @mountainhippo can provide some more detail I'm sure.

The scenario that Adrian mention is absolutely a key scenario in use today and going forward. This is where the merchant wants to retain full control of the basket experience, but to delegate the checkout experience (or at least the payment part of it) to a 3rd party (on a separate domain). Today this is commonly done via 3 approaches; 1) Full page redirect 2) iFrame 3) Popup (lightbox).

You can see an example of the first approach here http://www.plantuml.com/plantuml/proxy?fmt=svg&src=https://raw.githubusercontent.com/w3c/webpayments/gh-pages/PaymentFlows/Card/PSPHosted-CardPayment-Current.pml

Approaches 2 & 3 have a similar flow but don't use a full page redirect.

---
Reply to this email directly or view it on GitHub:
https://github.com/WICG/paymentrequest/issues/30#issuecomment-166861535

Received on Wednesday, 23 December 2015 10:49:37 UTC