Use Case Review - Adrian Hope-Bailie

[msporny]

Feedback by Adrian Hope-Bailie on 10/1/2014 9:57:17:

Do you have feedback on the Legacy Support design criteria?

This will be essential as a bridge from the old to the new. It is expected that providing this bridge will be seen as a significant commercial opportunity for incumbents so it will be important to consider motivating factors for these incumbents to adopt an open standard.

Put another way it would be useful if there were other ways incumbents could protect their commercial interests while still adopting open payments standards.

Do you have any feedback on the Coupons and Loyalty Cards use case?

Would this be considered a tender type or is it more complex than this?

Do you have any feedback on the Choosing the Attributes of Price use case?

I don't think the value-in-exchange benchmark is necessary. This falls into the scope of smart contracts. For web payments we should assume all transaction details are finalised at the time of processing.

If a seller/payee wishes to offer multiple payment options in multiple currencies this should be explicit so the payer can simply pick the one they favour.

Do you have any feedback on the Push-based Payments use case?

It should be possible for a buyer to complete this flow without the payment processor knowing who the payment is going to (if the payment mechanism supports this). i.e. Payment could be to a psuedo-anonymous payee identifier