Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111)

Regarding use cases for recurring payments, it may be worth separating different aspects of persistent payment authority:

* Variability of the value: Some authorities will allow the merchant to change the transaction value on each charge, which is useful for metered services like AWS or your mobile phone bill. Others theoretically don't need that ability, say a digital subscription (though prices do rise with inflation so in practice merchants often build the ability to do that into their initial agreement with the subscriber)
* Variability of the schedule: Some methods allow merchants to charge whenever they like, others might require the merchant to submit no more than one charge per month, for example.
* Strength of the authority: In the UK the most common recurring payment mechanism is direct debit, which offers merchants variable value, variable schedule authority, but offers payers a guarantee of any dispute being instantly resolved in the payer's favour.  Conversely [continuous payment authorities](http://www.moneysavingexpert.com/banking/recurring-payments) are much harder to revoke and are often used for loan repayments.  Of course whether the payer has a contractual obligation to pay the merchant is out of scope here but the level of invasiveness of the payment method is probably of interest.



---
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/browser-payment-api/pull/111#issuecomment-207179053