ayushh_docs

[floral rampart]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1332432112057454674

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[proven pine]

Hi there! That feature is currently in a preview state and we aren't familiar with it yet. You can reach out to support if you have questions on it: https://support.stripe.com/

[limber prawn]

okay, so can I instead capture payments 2 times?

with regular checkout

is it a good practise?

[proven pine]

That would be possible for users on IC+ pricing, though there are some considerations around availability: https://docs.stripe.com/payments/multicapture

[limber prawn]

I m not sure about this one, lemme explain what I am thinking

suppose if I have a Service and the price is 100$

the due date is on 31-1

so if I book today on 25 the price I need to pay is 50$

so I will have 2 columns for payment in the database session

initial_payment, due_payment

initial_payment will store the first 50$

and on 29 I will send the customer a payment link through email about the remaining 50$

I am planning to use checkout sessions for both of the transactions

is it considered best practise?

[proven pine]

Is it important for your customer to actively submit the payment (be present in the checkout flow) rather than you simply charging them at the pre-agreed time for the second installment?

[limber prawn]

I want to collect payments in 2 phases, it is important

like I will generate 2 checkout sessions for them

one at the beginning

and the other one before 2 days of due date

[proven pine]

Right, but my question is does the customer need to actively submit the payment on the second installment? Your integration could save their card on the first payment resulting from a Checkout session and then charge them again on the pre-agreed date for the second installment without their involvement

Which some people might consider a better experience for the user, depending on the nature of your business relationship

[limber prawn]

oh, without their involvement in the second pre-agreed date I can charge? how can I do that?

[proven pine]

You would use this parameter when creating the Checkout Session: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage

and then you would use the PaymentIntents API to charge the Payment Method you get from the Checkout Session later. See this guide also:

https://docs.stripe.com/payments/save-during-payment

[limber prawn]

I m unsure how to use this one

can you explain me the flow?

[proven pine]

You provide that parameter when creating a Checkout Session

[limber prawn]

okay

[proven pine]

see our guide here: https://docs.stripe.com/checkout/quickstart

please let me know what you don't understand

[limber prawn]

I know how to use checkout session

my question is

Let's say

[limber prawn]

if I turn on that parameter

how can I tell them again to pay for the pending 50%

that I don't get it

[proven pine]

You call the PaymentIntents API from your backend when its time to collect another payment

[limber prawn]

can you explain me the flow with docs?

[proven pine]

The flow, in principle, is described in the guide below. The difference is that in your case you would use Checkout to create the initial payment and save the card for later use. Step 7 in the guide shows you how to charge the PaymentMethod later: https://docs.stripe.com/payments/save-during-payment#charge-saved-payment-method

[limber prawn]

ok thanks

[proven pine]

No problem!