#-sam_api
pale nacelleBOT
đ 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/1347134413237915668
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
swift lantern
Can you share the ID (req_xxx) of the API request? https://support.stripe.com/questions/finding-the-id-for-an-api-request
chrome badge
req_7TbrJAqx5AmPxF
swift lantern
What's the desired outcome here?
Just confirmed, that params is not supported for cards. Agree we should clarify that somewhere
If you can explain usage I can help!
chrome badge
What's the desired outcome here?
preauth on the card, and later capture the funds after 3 days of trial
using the single use mandate
swift lantern
preauth on the card, and later capture the funds after 3 days of trial
Why not just use manual capture? Sounds like a better use case if there an initial hold: https://docs.stripe.com/payments/place-a-hold-on-a-payment-method
Otherwise you can't denote a card as single use. You'd just need to set it up without, and then detach it after use
chrome badge
I do understand your point,
but when using manual capture and cancelling it later the funds can take time depending on the bank.
I believe pre-auth and manual capture payment (pending capture) are both different or am I missing something?
swift lantern
If by 'pre-auth' you mean saving the card, yes they're different. But to clarify a Setup Intent only validates the card details and handles 3DS/auth, it doesn't ascertain whether the card/account has sufficient funds to be charged at a later date
So you may save the card today as you are, come to charge $100 in 3 days and it is declined because there's no money. That's the benefit of auth/capture as the $100 is held at time of auth so you know they have the funds
Overall it depends on your business requirements, really
chrome badge
Why not just use manual capture? Sounds like a better use case if there an initi...
in this case if the intent status is requires capture, can the payment still fail?
I have seen something like revocation_of_authorization in the docs
swift lantern
I'm not aware of a failure path once in requires_capture state other than it being canceled/released
Not sure what revocation_of_authorization is
chrome badge
Not sure what `revocation_of_authorization` is
swift lantern
I think that's less related to the auth concept and more a bank/issuer decline. AFAIK capturing won't fail
But in any case, there's still the same chance of failure/decline in your other flow. Your integration needs to handle that
chrome badge
But in any case, there's still the same chance of failure/decline in your other ...
so only thing we need to focus is listen on payment_intent.succeeded / charge.succeded to fulfill the final subscription of the customer (We do not use stripe subscriptions, we have our own custom flow).
swift lantern
Yes, succeeded is a terminal state indicating that the payment has been completed: https://docs.stripe.com/payments/paymentintents/lifecycle
chrome badge
Thanks!
Also, I believe this https://docs.stripe.com/api/setup_intents/create#create_setup_intent-single_use should be updated in the docs