- From: Krystian Czesak <notifications@github.com>
- Date: Tue, 08 May 2018 00:00:11 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/payment-request/issues/145/387304667@github.com>
>From what I gather, it might have been sparked because of a recent call where Andre (https://github.com/lyverovski) mentioned some experiments we've been running around Payment Request. See minutes here: https://www.w3.org/2018/05/03-wpwg-minutes > lyver: We've been running some experiments for several months with PR API running on a number of enterprise level clients ... we are putting together a brief that we will share with this group ... there are two points that I want to raise: merchants are not necessarily skittish; they have trusted us as a platform ... but what's missing for them is support for discount codes. Up to half of people have dropped out since they want to go through legacy UX to get the discount code. I think that is missing from the focus of the next six months ... the other thing is that buyers themselves are skittish...they see the payment sheet open and has little merchant branding, which may scare some off. If this is truly what re-opened the discussion and what you were asking about; our experiment allowed the customer to click a "Discount or gift card?". That would bring them to our normal checkout rather then them being able to apply a coupon code and then proceeding with Payment Request. As Andre mentioned, we'll be sharing the rest of the learnings and the experiment setup soon. -- 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-request/issues/145#issuecomment-387304667
Received on Tuesday, 8 May 2018 07:00:47 UTC