#esset
1 messages · Page 1 of 1 (latest)
That depends on what you're trying to do. Which API methods are you using specifically?
Account Links are for Stripe-hosted onboarding and account updates. These are hosted by Stripe. Node SDK is a server-side library for making API calls.
I'm creating a new AccountLink for one of our (custom) Connect Accounts to complete onboarding (if some additional docs needs to be uploaded).
This in the SDK:
class AccountLinksResource {
/**
* Creates an AccountLink object that includes a single-use Stripe URL that the platform can redirect their user to in order to take them through the Connect Onboarding flow.
*/
create(
params: AccountLinkCreateParams,
options?: RequestOptions
): Promise<Stripe.Response<Stripe.AccountLink>>;
}
/**
* The type of account link the user is requesting. Possible values are account_onboarding or account_update.
*/
type: AccountLinkCreateParams.Type;
.Type has more things than the jsdocs say
namespace AccountLinkCreateParams {
type Collect = 'currently_due' | 'eventually_due';
type Type =
| 'account_onboarding'
| 'account_update'
| 'custom_account_update'
| 'custom_account_verification';
}
So there isn't really a "recommended" route for updating the Connect Account. Mostly it comes down to preference and how you want to go about it. Obviously the Stripe-hosted option is easier and faster, but you can do the same thing with Node's Account Create and Update APIs (it just requires a lot more custom code on your end)
Do you have any follow-up questions?
Well... Yes, the question still remains. I want to use the Stripe-hosted option for adding additional details to an account.
Like this: https://youtu.be/RYiscsdICrs?t=1222
Join us for our Developer Office Hours and get your questions about the changes to Connect onboarding answered. Our expert engineers will walk you through the basics of building a Custom Connect integration.
Table of contents
Connect Onboarding Overview 1:47
Scaffold Demo 11:48
(hosted) Connect Custom Onboarding 16:00
Custom Onboarding Imp...
I could try using account_update, but was confused by the fact that there were two additional types, prefixed "custom", which made me think that's what we should use?
My guess is that's from an older API version and is no longer relevant. Does passing just account_update give the desired behavior?