Re: [webpayments] How can the API support enrollment (future payment) use cases? (#65)

Zach wrote:
> I'm not sure we need to do anything special to support this use case, except perhaps document that authorizations are performed with an amount of "0". 

I can't find my response on this subject earlier in this issue - I could have sworn I posted it.

In any case, we should >not< propagate odd semantics of zero or -1 for amount into our language.  If an acquirer is looking for an amount=0 to mean something, that should be translated out of the standard message, not embedded in it.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/65#issuecomment-183339108