#saad-nawaz_api
muted epochBOT
đ 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/1438258489750192198
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
nimble loom
Hello,
For #1 I just tested in test mode and we placed a hold on our test prepaid card. So we will certainly try to hold the funds if you specify capture_method=manual. The hold duration should still be the same but you can have your code check the capture_before property to see when the funds need to be captured by.
For #2, that is the default behavior when charging a card. Basically when charging a card there are two steps: authorization and capture. Placing a hold means we return control to you after the auth step and you initiate the capture step. By default we do both automatically, which means the funds get captured immediately after authorization.
trail snow
The scenario we have is that when user places an order, they have roughly 5 days to make modifications to the order. Hence, we want to place a hold when user places the order and once the time expires to make modifications, we capture. In order to reduce complexity at initial stage, we don't want to capture when user places order. So, if we set capture_method=manual in the PaymentIntent, will that ensure that capture doesn't happen automatically?
nimble loom
Correct!