#thomasnevink

1 messages · Page 1 of 1 (latest)

sick jacinthBOT
#

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.

vernal egret
#

we can talk here, what is up?

inland notch
#

You may view the log using req_Pli8j5u5DoFzvo?t=1699346623

vernal egret
#

'oId=16004 &&isSaveCa' has a space and two &s, that is a broken URL

inland notch
#

ok, let me check

#

Payments were working fine earlier but since we implemented HashLocationStrategy, the confirmPayment function from the UI is not giving redirect parameters such as payment_intent=pi_xxx&payment_intent_client_secret=pi_xxx_secret_yyy&redirect_status=succeeded included to the redirect url

vernal egret
#

what is 'HashLocationStrategy'?

inland notch
#

HashLocationStrategy is a LocationStrategy used to configure the Location service to represent its state in the hash fragment of the browser's URL

#

Simply put, we included an additional # symbol inside the url

vernal egret
#

ok, and how does that relate to Stripe? we dont' do anything special, we just redirect to the return_url you pass to the confirmPayment function and we would add URL query parameters as you mention. If you check the Network tab in your browser you would likely find that the browser is correctly redirecting and sending those params, but it's like that middelware or software that you mention on your server strips the details or modifies the URL before your application code sees it.

inland notch
#

ok, just wanted to make sure