- From: Rouslan Solomakhin <notifications@github.com>
- Date: Wed, 30 Aug 2017 08:03:31 -0700
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 30 August 2017 15:04:21 UTC
The user agent fires the `AbortPayment` event only in the currently invoked payment app. From user perspective, that's after the user has selected a payment app and clicked [PAY], while the user is waiting for the payment app to complete. From implementation perspective, that's after `PaymentRequest` event has been fired, but before `PaymentRequest.updateWith()` promise has been resolved. At this point, the user has given explicit consent for the merchant website's information to be passed into the payment app to facilitate the payment. Hence, the risk of `AbortPayment` event is low. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-handler/pull/207#issuecomment-326019318
Received on Wednesday, 30 August 2017 15:04:21 UTC