#nikita-saboo_error

1 messages ยท Page 1 of 1 (latest)

fair gazelleBOT
#

๐Ÿ‘‹ 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/1496214444626280579

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

dim coral
#

Hi there,
can you give me a bit more context how you encounter this error? Do you have like a request ID?

tardy jasper
#

the api called i see is from developer tools.

<html>
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, minimum-scale=1">
<meta name="robots" content="noindex" />

<!-- Prevent Google Read Aloud from reloading the page -->
<meta content="nopagereadaloud" name="google" />
<!-- Force IE9 to use standards mode -->
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<title>Something went wrong</title>
<link type="text/css" rel="stylesheet" href="https://js.stripe.com/v3/linked-accounts-error-screen.css" />
<link rel="icon" href="https://js.stripe.com/v3/favicon.ico" type="image/x-icon" />
<meta id="theme" data-message="light" />
<meta id="error_code" data-message="oauth_complete_error" />

</head>
<body>
<div id="root"></div>
<script src="https://js.stripe.com/v3/linked-accounts-error-screen.js" ></script>
</body>
</html>

#

strict-transport-security max-age=63072000; includeSubDomains; preload x-content-type-options nosniff x-frame-options SAMEORIGIN x-stripe-priority-routing-enabled true x-stripe-proxy-response upstream x-stripe-routing-context-priority-tier livemode-critical x-stripe-server-rpc-duration-micros 1051190 x-wc 3ff

dim coral
#

Ok, give me a moment to take look at this...

tardy jasper
#

sure . Sorry forgot to mention this is in testmode

dim coral
#

Got it. No worries.

#

Are you using Cross-Origin-Opener-Policy: same-origin?

tardy jasper
#

๐Ÿค” in the paymentElement page ?

#

checking

#

Yes

dim coral
#

can you try to change this to 'same-origin-allow-popups'

tardy jasper
#

oo

#

will need a min or two to do this

dim coral
#

No problem. To be fair, it's just an educated guess right now.... but I'll be waiting for you to test this.

tardy jasper
#

aah I see, np let me test this out

dim coral
fair gazelleBOT
tardy jasper
#

No I did not. looking at the financial connection .

dim coral
#

Ok, that might be it then.

tardy jasper
#

I have them configured though.

granite current
#

Gotcha. Trying to figure out the specific error here. Is there a public link to your test site where I can reproduce this for myself?

tardy jasper
#

Not yet. This is still in the developement. We have only CC payment method atm

granite current
#

Makes sense. Can you tell me more about your frontend integration here? Like is that financial connections modal being launched by the payment element or a call to a method like collectBankAccountForSetup?

tardy jasper
#

It is launched by payment element. We first create an invoice and then feed invoice's payment_intent_secrete to the payment element

granite current
#

Gotcha, and does your page use an iframe to show the checkout portion of your page? I have a vague memory that iframes can complicate this stuff a bit but that may not be relevant here

tardy jasper
#

hmm .. not really.. but we just show the PE

#

woah 'Cross-Origin-Opener-Policy', 'same-origin-allow-popups' worked !

#

if you dont mind can you explain me the logic

granite current
#

Nice glad that worked! My colleague who found that had to step away, looking into why that setting is needed and will be back in a minute

tardy jasper
#

sure

dim coral
#

Glad it worked. After some research i found information that a Cross-Origin-Opener-Policy: same-origin policy prevents the Financial Connections authentication flow from maintaining references to opened OAuth popup windows.