#calmcup_code

1 messages ยท Page 1 of 1 (latest)

silver bisonBOT
#

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

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

median horizon
#

The preceeding call is
try {
const account = await stripe.accounts.create({
country: req.body.country,
});

return res.send({
  accountId: account.id,
});

} catch (error) {
console.error(
"An error occurred when calling the Stripe API to create an account",
error
);
} which creates the accountId correctly

dark lake
#

Hi ๐Ÿ‘‹ can you share the ID of one or more of your requests that threw an error that I could take a closer look at?
https://support.stripe.com/questions/finding-the-id-for-an-api-request

silver bisonBOT
median horizon
#

I don'y see them there

#

I see only 200s from the POST
/v1/accounts

#

Im using npm package
"stripe": "^8.220.0",

dark lake
#

In the filters on that page, in the More section, can you also make sure "Outgoing Connect requests" is checked?

median horizon
#

now I've got some

#

but they seem to be only from the example embedded onboarding app from github

#

that I was running on port 4242

#

which worked fine

#

what can I try besides using a newer version of the stripe npm package

winter swift
#

Hi ๐Ÿ‘‹

I'm stepping in as my colleague needs to go soon.

The function call await stripe.accountSessions.create triggers an API call to the Account Session API: https://docs.stripe.com/api/account_sessions/create

If this code worked when you were running locally but now doesn't, that suggests the problem is likely with the hosting environment. Can you confirm that your hosting environment can reach Stripe APIs?

median horizon
#

hi

#

yes I can confirm that

#

let me try using a newer version of the npm package just to rule that out

winter swift
#

To be clear, have you run the shell script? What is output you received?

median horizon
#

this is the output

winter swift
#

Okay so that's looking good

median horizon
#

the npm package update actually worked

#

and I see the onboarding dialog now

#

I've updated it to "stripe": "^16.12.0",

#

latest

winter swift
#

Okay, so everything is working as expected now or are there still some outstanding issues?

median horizon
#

just one other question

#

on the first page of that onboarding example there's mobile phone and email for creating the connected accounts

#

while on my site I get only email, and then 2FA app setup

#

I'd like to skip the 2FA setup for my connected accounts

#

if there has to be something, mobile phone is better

#

if I can skip both, the best

winter swift
#

I'd like to skip the 2FA setup for my connected accounts
This isn't possible

#

We require 2FA for Connect accounts

median horizon
#

can I make it a phone code somehow instead of google authenticator

#

my users are not particularly tech savvy

winter swift
#

Hmmmm.... I know we use OTPs for the initial onboarding (one time passwords). Are you referring to ongoing 2FA?

median horizon
#

I;ll check the docs again

#

thanks for your help!