W3C home > Mailing lists > Public > public-payments-wg@w3.org > January 2016

Re: [paymentrequest] Support for "enrollment" use of API (#43)

From: mattsaxon <notifications@github.com>
Date: Wed, 20 Jan 2016 11:34:58 -0800
To: WICG/paymentrequest <paymentrequest@noreply.github.com>
Message-ID: <WICG/paymentrequest/issues/43/173334880@github.com>
There are 2 sub uses cases to consider here;

1. An identification validation, amount=0 might be a reasonable approach here
2. A deposit/reserve, e.g. a hotel deposit, a common way of doing this to authorise an actual amount, but not make the charge unless something happens, this is known as an "authorisation" without a "capture", effectively these are two seperate transactions when can be bundled as a "sale". The flows we have documented so far don't differentiate these as the distinction occurs between the merchant and the merchant PSP, not between the shopper and the merchant. However it might be prudent to have a distinction in the target model so the user is aware what they are signing up to.

Reply to this email directly or view it on GitHub:
Received on Wednesday, 20 January 2016 19:35:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:13 UTC