#hrach_connect-onboarding-accountsession

1 messages · Page 1 of 1 (latest)

lilac mulchBOT
#

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

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

eager solsticeBOT
#

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.

sinful ether
#

Hello

deep bloom
#

hello

#

thx for connecting

sinful ether
#

Sure

#

Can you clarify a bit here? You are saying you don't want that information to be in a popout modal? You want it inline?

deep bloom
#

As you can see from my screenshots bellow, when I'm hitting add information button, it opens second screenshot in new tab

#

but as I get from documentatnion it is possible to open this in modal

#

what I was trying to reach actually

sinful ether
#

Yeah that has to do with the security around collecting the login information for your user. It isn't possible to open it in a modal or have it embedded. We have heard this feedback already though and have an internal ticket to work on improving this flow.

deep bloom
#

so what is this popup ?

#

I want to achieve this experiance

#

this is screenshot from this channel, another user posted it

sinful ether
#

You can't control that popup -- it is used to collect login information from your user.

#

That screenshot does not show the popup embedded

#

It is just showing it minimized in the foreground?

deep bloom
#

no I dont see this popup on my end

#

so to be clear, correct me If I get it wrong

#

at the beginning it has to be opened in new tab then after auth. when I load setup onboarding again it will open this popup where I will set my account data ?

sinful ether
#

No after the login info is collected via the popup then the rest should take place embedded in your website

deep bloom
#

So what I'm doing wrong? this popup is not openeing in my end, its not blocked, its just not opening instead it opens in new tab where my email is set and asking me to submit , after I hist submit and set my password, new tab is closing and I can see embeded onboarding component

sinful ether
#

Hmm you are saying instead of it being a popup it is opening a new tab on your browser?

deep bloom
#

yes

sinful ether
#

Have you tried doing this with a fresh account?

#

I'll test as well real quick -- I was under the impression that it should be a popup

#

But maybe that has changed recently

deep bloom
#

will try with new account right now

#

as you can see I have tab with this button loading and new tab with "onboarding your account" in stripe

sinful ether
#

Thanks, can you give me the account ID that you just created to test with?

deep bloom
#

acct_1PmzlXD5oVNXENoz

sinful ether
#

Weird... when I test it is a pop up

#

Looking more

deep bloom
#

maybe I'm doing something wrong :/

#

const fetchClientSecret = async () => {
return this.session;
};
this._stripeConnectInstance = loadConnectAndInitialize({
publishableKey: this.publicKey,
fetchClientSecret: fetchClientSecret,
appearance: {
overlays: "dialog",
variables: {
colorPrimary: "#2a2f30",
},
},
});
this.renderOnboardingComponent(this.session);

}

renderOnboardingComponent(accountSessionId: string) {
const accountOnboarding = this._stripeConnectInstance.create('account-onboarding', {
accountSessionId: accountSessionId,
});

accountOnboarding.setOnExit(() => {
  console.log('User exited the onboarding flow');
});

const container = document.getElementById('onboarding-container');
if (container) {
  container.appendChild(accountOnboarding);
}
this.loading = false;

}

#

just getting session and loading coponent with overlays: dialog

sinful ether
#

Yeah I do the same

deep bloom
#

can it be because of localhost?

sinful ether
#

No I'm testing on localhost as well and that shouldn't make any difference

#

What is the URL of the new tab?

deep bloom
sinful ether
#

And can you show me your backend code for how you are creating your Account Session?

#

You don't happen to have a way to host your test site so I can reproduce from my end, do you?

deep bloom
#

this.stripe.accountSessions.create({
account: accountId,
//todo maybe this components needs backend configuration
components: {
account_onboarding: {
enabled: true,
},
payouts: {
enabled: true,
},
payments: {
enabled: true,
},
account_management: {
enabled: true,
},
payouts_list: {
enabled: true,
},
},
});

#

I think this is backend part

sinful ether
#

Still a pop up for me. Can you take a screen capture of exactly what you see and have your Web Console open when you do it as well?

deep bloom
#

It will not be so easy to setup localized version of this functional because its a part of big product

#

so I will try to record

#

oh, just get this error in console

sinful ether
#

Ah okay that helps, let me check on that

#

Likely a CSP issue

#

Can you add those to your policy and test again?

#

Ah actually in this case it is not CSP but your COOP

#

Do you have COOP set to same-origin?

deep bloom
#

so this should be set in backend ?

sinful ether
#

Yes

deep bloom
#

to be clear, on backend server where they are
calling this.stripe.accountSessions.create() they should set this header ?

#

regarding to documentatnion
Cross-Origin-Opener-Policy, unsafe-none. This (unsafe-none) is the default value of the header, so not setting this header works. Other values like same-origin break user authentication in Connect embedded components.

it should be "unsafe-none", and you think it's set "same-origin"

sinful ether
#

No this is based on your server

#

You don't pass this specifically to accountSessions.create

deep bloom
#

so its between our server and my localhost when Im getting “account_seasion”?

#

thx will ask backend to check, can I come back here after checking it with them ?

#

can you keep this tread till tomorrow ?

sinful ether
#

Threads close after a period of inactivity but you can always open a new thread

lilac mulchBOT
deep bloom
#

thx