#isaac.mk - setupintent
1 messages · Page 1 of 1 (latest)
Hi! Can you share the request ID (req_xxx)? Here's how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
here is the request id req_7ZC34JJCGVIj2W
here is the request id req_7ZC34JJCGVIj2W
Thanks! This request worked, so what exactly is the issue?
The issue is that I got the url "http:///?setup_intet=*** /#/authentication?merno = " but what I really want is "http:///#/authentication?merno = &setup_intet=*** "
The issue is that I got the url "http:///?setup_intet=*** /#/authentication?merno = " but what I really want is "http:///#/authentication?merno = &setup_intet=*** "
So you want to update the existing SetupIntent to change the URL? Or you want to create a new SetupIntent with the new URL?
No, I think stripe handle the url in a wrong way. It gives me a wrong pattern of the url.
No, I think stripe handle the url in a wrong way. It gives me a wrong pattern of the url.
Maybe this problem happened since I put a special symbol # in the url
No, I think stripe handle the url in a wrong way. It gives me a wrong pattern of the url.
Can you clarify? For example the URL in the SetupIntent ID you shared is "http://192.168.255.121:8080/#/authentication?xxx" So when users are redirected, they should be redirected to "http://192.168.255.121:8080/#/authentication?xxx". It's the same URL.
Yes. what you say is right. But in fact. Stripe redirects the user to "http://192.168.255.121:8080/?xxx#/authentication?".
Yes. what you say is right. But in fact. Stripe redirects the user to "http://192.168.255.121:8080/?xxx#/authentication?". not the http://192.168.255.121:8080/#/authentication?xxx" . you can see the difference between the two url.
Is there a need for the # in your return_url parameter?
Can you provide a reproduction of this?
yes. I need #. what do you mean reproduction. http://192.168.255.121:8080?setup_intents=seti_1KbhhYGIuqZWVOYBPHswTHcR&client_secret=seti_1KbhhYGIuqZWVOYBPHswTHcR_secret_LIIIcNYiVpX3GsgEz62tjmZJAqIBqYh#/authentication?merNo=jxt530946 . is this one ?
Somewhere where I can replicate the behaviour myself
SetupIntentCreateParams setupIntentCreateParams = SetupIntentCreateParams .builder() .setCustomer(scb.getStripeCustomerId()) .setReturnUrl("http://192.168.255.121:8080/#/authentication" + "?merNo=" + requireActionVo.getMerNo()) .setPaymentMethod(resultStripeMethodBind.getPaymentMethodId()) .setConfirm(true) .build(); this is my code.
@astral stone Because we are testing now, we can't give you the place to test.
I'll need to try and recreate this then, give me some time
Can you share your Stripe.js code?
Or where you call confirmSetup?
Anyway, I don't think this is a Stripe issue but the browser enforcing the correct spec: https://superuser.com/a/498625
I am unclear if an anchor tag should come before a query string or after.
http://www.domain.com/search?query=hello#name
or
http://www.domain.com/search#name?query=hello
Or does it matter?
So you'll need to amend your URL structure to accommodate for that