#django_api
devout vaultBOT
đ 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/1278719312382918809
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sudden tide
Hello
When you say "payment holding feature" do you mean separate auth & capture: https://docs.stripe.com/payments/place-a-hold-on-a-payment-method ?
devout vaultBOT
tender hollow
yes i do , but also here there is a due_date that stripe expects that the payments are captured after holding them. Since the periode we give the seller and buyer to book there appointment is 2 weeks, and the payment is being held up until then this wouldnt work correct ?
let me be more clear : stripe provides authorization for a payment up to 7 days for some methods. Others have less time to validate the payment.
sudden tide
Yes we document it above the amount of time for each card brand and the different payment method types
No you can't extend that period
You would have to re-authorize if that expires
tender hollow
so to work around this i would have to 1 ) authorize the payment somewhere later in the auction ending flow 2 ) re-authorize the payment that is exceeding the amount of time i have ?
keen light
Hi taking over here as Bismarck has to step away
Yeah you'd either have to do something like that or just use a SetupIntent to collect payment method info and set it up for future use: https://docs.stripe.com/payments/save-and-reuse
tender hollow
that last part sounds a little less developer-unfriendly then what i suggested. I'dd always like to try known ways instead of workarounds ! ill go and check the documentation and if something isnt clear ill make sure to create a new help post ! thanks alot for the guidance.
my question is when setting a payment in the future. And for example within this periode one of two sides declines the auction ( either buyer or seller ) what would happen with the payment ? should i just write code that handles this situation so that the future payment is declined for auctions that get cancelled after that the auction was ended ( forexample : car isnt as described, issues with data provided by seller, stolen car , etc etc )
since im registering this payment somewhat before the buyer checks the state of the product. It is highly possible that the buyer declines after this appointment. Is a validation for this edge case enough to make sure nu future payments are made without anybody accually aggreeing to it ?
keen light
Which implementation are you referring to in above? Separate auth and capture or setupintent?
tender hollow
future payment
keen light
You should read that doc then
In that flow payment isn't created until you're ready to charge the customer
So there's nothing to cancel
tender hollow
I see, ill get coding ! thanks for the advise