- From: Jorge Zaccaro <jorgezaccaro@gmail.com>
- Date: Mon, 20 Oct 2014 10:47:10 -0500
- Cc: Web Payments CG <public-webpayments@w3.org>
- Message-ID: <CAPnSDnP7mPtP_Aun-eesTAcNyVyQsUPtMjbqXdKXgK3gj6nJJQ@mail.gmail.com>
Both buy flows sound good, but how would they answer the question > “Why can’t I just walk up to a cashier with my phone and all that information magically appears?” without the need to swipe a loyalty card or give the cashier a phone number if the payment instrument (e.g. apple pay) and the loyalty card (e.g. MyPanera Rewards) reside in different systems and cannot be linked due to the anonymity constraint? On Mon, Oct 20, 2014 at 10:44 AM, Anders Rundgren < anders.rundgren.net@gmail.com> wrote: > On 2014-10-20 17:33, Manu Sporny wrote: > >> On 10/20/2014 10:56 AM, Anders Rundgren wrote: >> >>> Doesn't loyalty credentials have to be provided before the actual >>> payment request in order to possibly adjust the price? >>> >> >> We've been modeling a loyalty card as just another form of credential >> (in the Credentials CG sense of the word). So, the buy flow would look >> something like this: >> >> 1. Merchant requests loyalty card credential (if you have one). >> 2. Credential is delivered, price is adjusted. >> 3. Customer initiates payment. >> 4. Digital receipt is delivered to merchant. >> >> This whole process could be automated w/ a more streamlined buyflow: >> >> 1. Merchant provides two invoices one with loyalty card and one without. >> 2. Customer is notified of a discount opportunity and is prompted to >> send loyalty card along with payment. >> 3. Payment is made. >> 4. Digital receipt, with embedded loyalty card info, is delivered to >> merchant. >> >> There are some other buy flows that are interesting as well, but the >> general idea here is that a loyalty card is a type of credential (not a >> payment instrument). >> > > That was exactly the answer I was hoping for! > > Anders > > >> -- manu >> >> > >
Received on Monday, 20 October 2014 15:47:40 UTC