#RahulRaval-connect
mental pelican
But suppose if a customer has authorized $100 ( so on bank account 100 would be reserved right?), and when items are fulfilled we charge the amount directly from the account. Suppose we charged $50, and if we don't update the auth amount then customer would think we charged extra $50 and not from the authorized amount, as that would show intact, right?
regal urchin
The bigger concern here is that you can't do multiple captures against a single auth.
mental pelican
no, I want intent to do captures using that auth, I'll store the customer card at checkout time, and charge the amount directly from the card once we have items fulfilled.
The auth I'm doing is just to ensure that customer have that much amount in card, once the order is fulfilled I'll void that auth.
regal urchin
In that case, after the first charge you'd void the initial auth and then create a new one for the lower amount. But this seems unnecessary as you already have authorized the total amount.
mental pelican
Can we create an auth without needing customer interaction or authentication?
Also, suppose we void the amount, and if the customer's account goes below the next required charge amount in between, then, in that case, we won't be able to charge the next amount.
regal urchin
Do you know the split of the funds beforehand? Could you create multiple auths up front?
mental pelican
ok, so you mean we create multiple auths to diff account from the checkout page?
regal urchin
Oh, didn't realize you were using checkout.
mental pelican
yes without checkout can we create multiple auth? I mean suppose we create single intent when customers checkout and then save the card too.
So with the given data in hand can we create multiple auth without needing customer auth again?
regal urchin
You could use a setup intent with the checkout process to collect the payment method details, and then auth/charge later in the flow. Circling back to something you mentioned in your original post:
We can't capture all payments in a single account and distribute later due to some legal things, so that's out of the picture
Does this mean you're going to be using Direct Charges?
regal urchin
I need to step away so I’m going to archive this thread. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact
thin gate
heya @mental pelican! I've reopened the thread, how can I help?
mental pelican
Does this mean you're going to be using Direct Charges?
What @regal urchin mean as the direct charge?
mental pelican
ohh got it, no we won't do direct charges, the vendor will pay the commission at end of the cycle.
Can you guide me through how I can create multi-auth later on?
So I'm thinking this could be the flow:
- create an auth of the whole order amount from checkout, also store customer card details to charge it later on
- When an order is placed, we will create multiple auths based on the details we stored ( if possible ), and then void the main auth created at the checkout time. Can you confirm here that we can create auth such a way, and capture it later on?