- From: Peter Saint-Andre <notifications@github.com>
- Date: Fri, 13 Apr 2018 10:19:50 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 13 April 2018 17:20:18 UTC
@hexalys You raise a very good point. It strikes me that the current flow & API are optimized for one-time, real-time purchases by consumers - not recurring payments (e.g., subscriptions), not split payments (e.g., multiple cards), not hold-then-pay (e.g., reservations or temporary credit charges to lock in a price), not more complicated B2B interactions, etc. I'm not sure what to do about that (all of those scenarios add complexity), but we should be aware of the limitations... -- 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/payment-request/issues/701#issuecomment-381203959
Received on Friday, 13 April 2018 17:20:18 UTC