#calmcup_code
1 messages ยท Page 1 of 1 (latest)
๐ 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.
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
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
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
I don'y see them there
I see only 200s from the POST
/v1/accounts
Im using npm package
"stripe": "^8.220.0",
In the filters on that page, in the More section, can you also make sure "Outgoing Connect requests" is checked?
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
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?
We have a shell script you can use to test this out here: https://github.com/stripe/stripe-reachability
hi
yes I can confirm that
let me try using a newer version of the npm package just to rule that out
To be clear, have you run the shell script? What is output you received?
Okay so that's looking good
the npm package update actually worked
and I see the onboarding dialog now
I've updated it to "stripe": "^16.12.0",
latest
Okay, so everything is working as expected now or are there still some outstanding issues?
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
I'd like to skip the 2FA setup for my connected accounts
This isn't possible
We require 2FA for Connect accounts
can I make it a phone code somehow instead of google authenticator
my users are not particularly tech savvy
Hmmmm.... I know we use OTPs for the initial onboarding (one time passwords). Are you referring to ongoing 2FA?