#dustinnutrisense
tired shuttle
cobalt glen
Hi there 👋 I don't think it's possible to create Subscriptions such that their Invoices's Payment Intents use a Separate Auth & Capture flow, but I'm double checking that.
While I do that, can you help me understand how using a hold would help here? I don't think that is clicking for me. Is your goal to create a hold sooner in the process? The problem with that and Invoices, is that an Invoice doesn't generate a Payment Intent until it's finalized.
tidal gulch
@cobalt glen We want to have a synchronous failure for our members when they provide a payment method that cannot handle our initial charge. We believe that a hold should (generally) handle this.
We cannot just charge them immediately because our tax is just estimated but not finalized until we have an invoice line added from our third party. After that invoice line is added, we know the exact amount to charge
cobalt glen
I confirmed it's not possible to use our Separate Auth & Capture flow with Subscriptions or Invoices. My follow-up question, had that been supported, would have been how you would know what amount to create the authorization for, if you don't yet know the total amount that you actually need to charge the customer. Would you always assume a higher amount in case the actual tax was higher than expected (you might have run into problems trying to overcatpure if you tried to capture an amount higher than what was originally authorized).
tidal gulch
Would you always assume a higher amount in case the actual tax was higher than expected
Yes this was the plan Toby
@cobalt glen Do you have any context on how other companies solve this for subscription models?
cobalt glen
Honestly, it sounds like you have solved, it sounds like you have a flow that works given the limitations you're working with (primarily that you have to wait for input from a third-party).
The problem I see with always assuming a higher amount than you'll actually charge, is doing so could cause artifical insufficient funds issues. What if the customer has enough funds to pay the right amount, but not enough for the authorization of the higher amount to be successful?
I'm not really sure how you would be able to detect payment failures in your flow sooner than when the payment is processed.
tidal gulch
@cobalt glen We don't have it solved unless we block customers at our checkout until we charge them (rather than placing a hold on a card).
In our case, this will be a bad experience.
Is there no use case for other users of Stripe where they need to synchronously place a hold on a payment method for a subscription plan without immediately charging?
cobalt glen
Not that I've helped anyone through.
tidal gulch
@cobalt glen Is there any way to do the following?
- Create a subscription with a draft invoice
- Somehow attach a payment intent with a hold
- Attach more invoice items
- finalize payment intent and collect