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

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

Received on Friday, 12 February 2016 16:30:34 UTC