#mesei81-connect

1 messages · Page 1 of 1 (latest)

dim orbit
#

@valid hamlet sounds right. What parameters were you expecting?

valid hamlet
#

If the url without any params, I don't know which account has completed the register flow

#

The page that the redirect url refer to just can show the common information, it can't show the information relate with the account.

dim orbit
#

you could change the return_url you pass when creating the account link to include the account ID then if you need that!

#

you probably want a more robust authentication though, like cookies in the user's browser so you can identify them

valid hamlet
#

emm.. cookies?

dim orbit
#

what's the question?

valid hamlet
#

nothing. Let me think about it.

dim orbit
#

to be clear you can do things like

 const accountLinks = await stripe.accountLinks.create({
  account: account.id,
  refresh_url: 'https://example.com/reauth',
  return_url: `https://example.com/return?account=${account.id}`,
  type: 'account_onboarding',
});
#

but overall for most integrations, you're going to need some kind of authentication in general so that you can map users of your system to their corresponding Stripe account IDs reliably.

valid hamlet
#

ok.

#

Now I just use the test mode

#

I'm in the researching state

#

use the curl to test

#

Which account's attribute can indicate that the account has completed the connect register flow?

#

details_submitted, charges_enabled or payouts_enabled?