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

Yes, they can - additionally you may want to actually place a hold on the payment instrument, or verify the amount you might charge in the future is actually present right now (the same is true for periodic billing - you may not be charging the user for another 30 days, but you want to verify now they actually are likely to be able to cover the charge).

Sometimes this charge isn’t necessarily visible or clear to the user, but still happens (Uber is a good example, you aren’t charged until the ride is completed, but there is still a charge being placed for an actual amount when you call the car).

> On Feb 10, 2016, at 11:47 AM, Rouslan Solomakhin <notifications@github.com> wrote:
> 
> Regarding the payment methods that don't support zero amount authorizations: do these payment methods support periodic billing or future charge?
> 
> —
> Reply to this email directly or view it on GitHub <https://github.com/w3c/webpayments/issues/65#issuecomment-182547483>.
>