[koa]

I have been using Stripes and Braintree's "Store/Verify then Charge Later" model in SaaS apps I build for customers in the service(Reserving services in advance) industry.

I have found that better that the original Auth/Capture flow since the final amount to be charged can be highly variable. Can anyone shed some light on when/if this auth/capture approach might make more sense in this type of use case?

[cstejerean]

You can follow a model similar to say hotels, where they auth the card for the room charge + expected incidentals, and then charge for the actual amount at the end of the stay. The amount you capture can be less than the amount you authorized.

[dminor]

> The amount you capture can be less than the amount you authorized.

The amount you capture can also be more than the amount you authorized, but how much more depends on the bank and is not known until you try.

[jtdowney]

It actually depends on the merchant category code (MCC) of your merchant account when it is setup. Only certain category codes, such as hotels and gas stations, are allowed to capture for more than they authorize.