W3C home > Mailing lists > Public > public-payments-wg@w3.org > February 2016

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

From: Adrian Hope-Bailie <notifications@github.com>
Date: Mon, 15 Feb 2016 02:53:12 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Cc: webpayments <public-payments-wg@w3.org>
Message-ID: <w3c/webpayments/issues/65/184165280@github.com>
I'm a big +1 to not carrying bad design into our API due to legacy of any underlying systems.
If we want to support various uses we should call them out as valid transaction types.

Payment apps and PSPs should deal with a payment request for a "reservation" or "enrollment" or "some payment type" and translate this into the appropriate set of parameters in their messages to the scheme/network.

Reply to this email directly or view it on GitHub:
Received on Monday, 15 February 2016 10:53:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:14 UTC