Re: [w3c/payment-request] Support for gift cards and discount codes (#145)

@adrianhopebailie wrote
> 1. The word coupon. I'm not sure it's universal terminology. Maybe discount code would be better?

Agree that the name is not great and totally open to bikeshedding. The reason I didn't go with `discountCode` was that it might not always be a "discount". 

Few options, from [Wikipedia's coupon entry](https://en.wikipedia.org/wiki/Coupon):  "coupon codes", "promotional codes", "promotion codes", "discount codes", "keycodes", "promo codes", "surplus codes", "portable codes", "shopping codes", "voucher codes", "reward codes", "discount vouchers", "referral codes" or "source codes". 

My personal choice would be: `promoCode`, as it's fairly generic, doesn't talk about discounts, and covers the "you get a free thing" use case... other option, `offerCode`.  

@adrianhopebailie, wrote:
> 2. The user should be allowed to change the code even if the merchant has accepted it.

Ah, can you help me understand this a bit more? do you mean remove it? Like, this user story:
 
 1. "Let's see what this gives me!", user enters code "MYSTERY-SAVINGS".
 1. "Oh! I get 10% off everything!... maybe I should save this for next time I do a big purchase". 
 1. User removes code somehow. 
 1. User hits "Pay". 

Or, this user story:
 
 1. "I have 2 codes, but I can't remember which is better. Gonna try the first...".
 1. User enters code. 
 1. Merchant responds with "10% off!".
 1. User removes first code, User enters code 2. 
 1. Merchant responds with "You get a free Widget!".
 1. User decides they prefer 10% off, so renters code 1. 
 1. User hits "Pay". 

So, with the above, the payment sheet should have the following affordances: 

 1. enter promo code. 
 1. edit a promo code - even when not in error.
 1. remove a promo code.
 1. display error - allowing the code to be fixed or removed. 

@mnoorenberghe wrote: 
> I don't think we would really need couponAccepted… if the merchant doesn't return an error from the event then we can assume it's valid.

Agree! Will drop `couponAccepted`. 

> I also think we shouldn't restrict to a single applied coupon as that will still not be flexible enough for sites and we'd have to fix that later.

Yes, I was thinking the same thing. My limited personal experience was that I'd only ever seen the ability to apply a single code. Folks who know better: @andrewpaliga, @michelle-stripe, @jenan-stripe, your feedback is critical here:

 * Do you have stores that accept more than one coupon code? 
 * If yes, does the number of coupon codes allowed need to be limited by the merchant? 


-- 
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-386950179