#dannnnnnnnnnnnnnnnnnnnnn_unexpected

1 messages ¡ Page 1 of 1 (latest)

umbral meteorBOT
#

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

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

pure vigil
#

You should switch to path params path/to/{param1}/{param2}...

finite kraken
#

but is there no way around this? that would be a lot of work for us to do and it's something we can think about in the future but for now just need a quick fix

#

and just out of curiosity, what's the reasoning for removing get args?

pure vigil
#

Stripe adds it's own qeury aprams, like the setupintent id for example

#

Let me double check for confirmSetup first...

#

I did a test and the query params are conserved for SetupIntents too

#

Apologies for the confusion initially.

#

Could you please share a SetupIntent Id ?

finite kraken
#

yeah ofc and no worries

#

2 secs

#

Setup intent ID: seti_1RojVuAyaQeh2nqystJ7Qs4h

#

just in case you need it, thats on the test mode of our account with ID acct_1MpE3nAyaQeh2nqy

#

I imagine I know what's causing it, it's probably because we return to a url which has a return_url itself with a GET arg. Maybe there's a better way on our side we could be doing this, was just wondering if this was something you'd encountered before

pure vigil
#

Actually, I tested with this return_url http://localhost:3030/?test=value1 and I got back the test query param

#

AH I think the issue, is that you are specifying a wrong redurect url, here what you passed (req_Kdxul4hbrqw7of)
http://localhost:8000/stripe/payment-methods/client/136/card/add/success/?redirect_url=http://localhost:8000/testagency/stripe/payments/invoices/137/pay-card-anon/136/?t=eba923dcb0c46188f42d69fd18685bcfc5034ea7

#

You should pass just:
http://localhost:8000/testagency/stripe/payments/invoices/137/pay-card-anon/136/?t=eba923dcb0c46188f42d69fd18685bcfc5034ea7
No ?

finite kraken
#

nah so it's the correct redirect url, we just also want another redirect after, that's like a middleground that does a few bits a pieces before taking the user to a page

#

so for example we add a few actions and make sure the card will display to the user before redirecting them back to the anon pay by card page

#

but tbf this has been helpful, cause maybe what we should be doing instead, is having ?url=&token= and then if they exist grab them that way

#

I think I know what we need to do on our end now, Thanks for the help!

pure vigil
#

Then you should probably encode the redirect_url

#

nah so it's the correct redirect url, we just also want another redirect after, that's like a middleground that does a few bits a pieces before taking the user to a page
In that case the middle page should build the redirect url by it self and redirect the customer

finite kraken
#

Yeah that makes sense, will give those a go, thanks for the help here!