kristin_EverCharge

[woeful ermine]

Yes they can. Can you clarify why you are making this move? Are you basically not making an upfront charge anymore and just want to collect payment method info?

[frail hemlock]

We're delivering a variable product and don't know the cost until the service has been delivered. We were using PaymentIntents with the manual capture, but have discovered we're missing out on substantial revenue because the auth amount wasn't high enough, and raising to a 'safe' level would be a potentially deterrent to our users.

We've decided that we're willing to take the risk of not authorizing users before they start our service

We have a fall-back plan of using setup_future_usage for the PaymentIntent, but don't love the idea of incurring a fee for each test payment at the start of the user flow

[woeful ermine]

Gotcha, that makes sense.

Can you clarify a bit on that last scenario?

Is that basically you would place a hold on the card and save it for future use, then if the final amount is over the hold, charge that extra amount as well?