#bootsy_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1271247773559165038
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there
the fail params should have a failed flag but they don't
what does this mean exactly? Are you following a specific guide here?
Your Mechanic takes the hassle out of car maintenance, including oil changes, tuneups, and brake replacements by bringing certified technicians to your door.
there's no parameters on the url that said the afterpay flow failed
there used to be a few weeks ago
it used to have additional params of &redirect_status=failed
but those are missing so when the user comes back to the site our flow is broken
with the current response, how am i supposed to tell if the afterpay was authorized?
Hm, are you sure redirect_status was included as a query param on Afterpay payments
i misunderstood
yes redirect status was definitely there before
i tested it a million times
how else would i know if it failed or succeeded
We generally recommend retrieving the payment_intent included in the query params and inspecting its status
wow. is that the only way
?
why was the redirect_status removed? or does it only get added in some instances?
I know it doesn't get added for cards (as I frequently test with cards and have never seen this before)
I haven't tested with Afterpay in the last few weeks or so but don't think I paid close attention to the query params
It looks like redirect_status is only included for some payment method types, not all
alright. so the only option is to make a call to stripe with the payment_intent to see what the status is?
Right, that's the safest/most reliable since query params can be manipulated