#manduily_api

1 messages · Page 1 of 1 (latest)

sonic steppeBOT
#

👋 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/1435691182553567415

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

hushed brook
#

Hi there,
when you say "deadline period expires", what do you mean? Just want to make sure I fully understand the question

random sun
#

What I mean is, when doing the payment intent through debit card, there is a 7 days period to manually capture the payment, otherwise it becomes canceled as I understand. I was looking for a way to transfer the funds to the platform automatically, instead of getting in canceled state.

sonic steppeBOT
hushed brook
#

Are setting capture_method=manual when creating a Payment Intent? By default Stripe captures PaymentIntents automatic_async, meaning Stripe asynchronously captures funds when the customer authorizes the payment.

random sun
#

Yes I set the parameter "capture_method=manual", because the platform is booking based. User makes a booking, pays and after the service is completed, the vendor confirms by clicking a button. This button will call the API and capture the funds. The user might cancel the booking though, or it might be in the future beyond those 7 day capturing period.

#

Of course I will do a CRON that will make a check for each payment intents, but want to be extra safe

hushed brook
sonic steppeBOT
random sun
#

Yes I checked that documentation, even if I use payment_method_options.card.request_extended_authorization, then still the only way to capture the funds from the payment intent is manual, I understand that. I guess that there is not automatization on what happens if the authorization period is over, except on getting in canceled payment intent.

severe inlet
#

What would this 'automatization' do? Yes, the way it works is if you do not capture the payment before it expires, it will be cancelled and the funds will be released.

random sun
#

Maybe automatization was not the perfect term. My idea is to provide the opportunity of canceling, only in the capturing period, which let's say is 7 days. If the capturing period expires, instead of releasing the funds and cancel the payment, transfer them to the platform.

severe inlet
#

But why would you do that? The intent for this flow is to hold the funds from the customer's payment method. Then, charge them.

#

If you want to send the funds to the Platform, then you'd just charge the customer no?

random sun
#

Because they might cancel the booking and the business logic is to only capture the funds after the vendor clicks a button when the service is completed. After the service is completed funds will go 20% to the platform and 80% to the connected account. Sometimes the booking might be 2 months ahead, so the funds can't be reserved for such a period, as you stated. In this cases either I capture them, when the vendor confirms within the capturing period or automatically capture them after it's over.

#

Of course I will take care by myself to capture them 1 day before the expiring period, but wanted to have a backup option.

severe inlet
#

In that case, would not you be able to add another auth right before it expires?

random sun
#

Yes I will for sure, just wanted to have another backup safe option, if something happens

severe inlet
#

Once expired, there is not much you can do, no

random sun
#

Okay I understand. Thank you for the support.

#

Have a nice evening/morning depends on where you are 🙂

severe inlet
#

Sure, you as well