thomasnevink

[violet monolith]

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• thomasnevink, 19 hours ago, 13 messages
• thomasnevink, 20 hours ago, 9 messages
• thomasnevink, 4 days ago, 6 messages

[calm ocean]

hello! we'd prefer to open a new thread if you're coming back after a while. How can we help?

[timid coral]

It is basically those 2 last chats for your reference

[calm ocean]

Do you have a new question? Looking at the last thread, you acknowledged what we said and there weren't any new questions

[timid coral]

We are giving a return url with a # symbol but for some reason when doing stripe payments, payment_method_data[referrer] takes the url till the # symbol. i.e, http://localhost:4200

confirm function is failing in ui side, telling that the url is not valid

[swift stratus]

Hi @timid coral there's still a space in the return_url

[timid coral]

Saw that, but even if we remove the space in the return_url, it is throwing this error

[swift stratus]

What's the request ID?

[timid coral]

req_0rZZVgOgctlZGq

[calm ocean]

what error are you referring to?

the request is successful

[timid coral]

Yes, but we are not getting the return url parameters attached to our url

http://localhost:4200/#/order?OrderId=25169&PaymentInfoId=16123&isSaveCard=true

This is what we are getting

http://localhost:4200/order?OrderId=25169&PaymentInfoId=16123&isSaveCard=true&payment_intent=pi_xxx&payment_intent_client_secret=pi_xx_secret_yyy&redirect_status=succeeded

This is what we used to get earlier before including the # symbol in our url

http://localhost:4200/#/order?OrderId=25169&PaymentInfoId=16123&isSaveCard=true&payment_intent=pi_xxx&payment_intent_client_secret=pi_xx_secret_yyy&redirect_status=succeeded

[lilac rose]

I am confused. The last 2 URLs is the same, so you are getting what you used to get earlier?

[timid coral]

The last url we are not getting

After including the # symbol, we are not getting the expected last url

We want this url, for doing post payment processing like recording the payments to db,etc

[timid coral]

The last url is not same to the 2nd url, there is an extra # symbol

@swift stratus @calm ocean @lilac rose

[lilac rose]

Please avoid mentioning! And sorry looking closer

[timid coral]

My sincere apologies

[lilac rose]

Can you list down in bullet points

1. The request id req_xxx you used earlier, and what URL it redirected you to
2. The current request id req_yyy you are using, and what URL it redirected you to

[timid coral]

1. req_RxriL2ia4p0Liw used earlier, "return_url": "http://localhost:4200/order?OrderId=25171&PaymentInfoId=16125&isSaveCard=true",
   "client_secret": "************************************************************",
   "key": "pk_test_*********************************************************************************************tdWalV"

2. current req_bB0sx07JBONGCv, "return_url": "http://localhost:4200/#/order?OrderId=25170&PaymentInfoId=16124&isSaveCard=true",
   "client_secret": "************************************************************",
   "key": "pk_test_*********************************************************************************************tdWalV"

The return_url is the one we sent in request payload

Redirect urls will provide you 1 sec

[lilac rose]

req_RxriL2ia4p0Liw is sent at 2023-11-08 05:47:28 while req_bB0sx07JBONGCv is sent at 2023-11-08 05:42:52 which is earlier? You are probably mixing up the time?

Anyway, we want to see how passed in return_url leads to redirect url