w3c / webpayments-ig

Web Payments Interest Group
22 stars 29 forks source link

Add discovery use case idea based on liability? #7

Open ianbjacobs opened 9 years ago

ianbjacobs commented 9 years ago

The first is to add a use cases under discovery of accepted schemes. The use case brought to my attention is where the payment schemes acceptable to the merchant may depend on the merchant’s existing relationship to the customer. I understood that in some cases, the merchant may prefer to accept payments using a particular scheme that may be less expensive to use, but with fewer fraud protections. The merchant may prefer this scheme for well-known customers or suppliers, but prefer a different scheme for first-time customers or where there is greater perceived risk.

Thus, we might add something like this:

Customer Relation: Tim is a frequent customer of HouseAndTools. Because he has logged in and is trusted, HouseAndTools offers @@need a payment scheme name@@ as the preferred (@@or only?@@) acceptable payment scheme. Goals: Lower Costs Motivation: Knowledge (and trust) about the payer can inform the payee’s choice of acceptable payment schemes.