#XinJin
1 messages ยท Page 1 of 1 (latest)
Client IP. It's the IP of the account holder's device (the one they used to view and accept the terms).
Randomly? That would be a violation of the Stripe terms of service I believe, as you're providing falsified information. Why would you set it to something random?
Ok. I will use the client ip address.
When I creating stripe connect account.
and attach external account,
which webhook event
accounts for final confirmation to verify all?
Verify all of what?
stripe connect account verification process.
You probably want account.updated.
I was getting
several account.updated.
although I submit all information at once.
and create the external account.
Sorry, not sure I understand. Do you have a question? Getting lots of account.updated events is normal.
Yeah.
I want to
get event of final account.update
At that point,
I need to do some actions.
One thing I want to clarify: based on some of the questions you've asked here it sounds like you're trying to bypass/hide/skip some of the required information collection and account verification steps. I strongly encourage you to not try to do that. If you do anything like that it's likely your account will be flagged and possibly suspended, and your connected account holders will not have a good time.
That's great! Just wanted to make sure you have a good experience. ๐
It's account.updated.
You need to examine the content of the event to determine the disposition of the account.
This guide might help: https://stripe.com/docs/connect/identity-verification-api
when creating stripe connect account,
can I add additional data?
such as userId of whom the user created
So, in webhook event,
You can add that in the Account's metadata, yeah: https://stripe.com/docs/api/accounts/create#create_account-metadata
I want to get that.
Ok.
The webhook event, as I checked,
sometimes I got external_accouont.created
event in last time
and in another case,
account.updated
That event is specific to the external account being created, not the connected account itself.
You may want to read through all of the account.* events listed here to get an understanding of what they're all for: https://stripe.com/docs/api/events/types
Occurs whenever an account status or property has changed.
account status,
If I know the final account status,
I can determine if this is last event or not, I think.
There is no "final" account status. Accounts are dynamic entities and may change their status over time.
I recommend you read this section carefully as it explains in detail what you're trying to do: https://stripe.com/docs/connect/identity-verification-api#determining-if-identity-or-business-verification-is-needed
It's not as simple as checking a single property on the account and then ignoring future updates/events.
Ok, I will see in detail. Thank you.
And when creating paymentIntent,
can I add meta data, too?
Yep. Metadata is available on many Stripe objects. You can check the API reference to see if an object has a metadata property or not.
For example, for Payment Intents, metadata is documented here: https://stripe.com/docs/api/payment_intents/object#payment_intent_object-metadata
And after i added external account,
I want to update a new external account.
with different card.
But seems it is not possible.
You can update the account with a new external_account: https://stripe.com/docs/api/accounts/update#update_account-external_account
Did you have a question about that code?
I created with
bank account token.
So I want to update this token with new.
But the body type
doesn't say like that.
Did you get an error?
You're not supplying the correct arguments. updateExternalAccount takes the account ID, then the ID of the new external account, not an object.
In other words, you're skipping over id there and going to params.
The id should be new token?
Yes.
Can you copy and paste that tok_ ID here, and also give me the connected account's ID?
That Token exists on your platform account, not on the connected account, which is why you're getting the error message.
You need to create the Token on the connected account: https://stripe.com/docs/connect/authentication
I don't understand exactly.
On frontend side,
I am using the stripe api key
And creating payment token
And added to the created stripe connect account.
Is this wrong logic?
Are you initializing Stripe.js with the connected account's ID?
Like this?
var stripe = Stripe('{{PLATFORM_PUBLISHABLE_KEY}}', {
stripeAccount: '{{CONNECTED_STRIPE_ACCOUNT_ID}}',
});
When creating stripe external_account,
I must initialize the stripe in that way, too?
When creating a Token you want to attach to a connected account as their external account you need to create that Token on the connected account, not on your platform account.
If you're using Stripe.js to create the Token you need to initialize it with your platform account's publishable key and the connected account's ID in order to have Stripe.js create the Token on the connected account.
Does that make sense?
Yeah. That makes sense.
I didn't use the created connect account Id to initialize the stripe.js
But creating external_accounts seems successful.
Now
When updating the external_accounts, I got the errors
which I showed you.
But when creating the external_accounts,
I created the token and used it to create the external_accounts
without using the stripe connect account Id to initialize stripe.js
But seems it is successful.
How could you initialize Stripe.js with an account ID that doesn't exist yet?
When you first create the account you can use a Token on your platform because the connected account doesn't exist yet.
Am I understanding correctly?
Can you show me the request ID where it worked so I can make sure I understand? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
req_4mdUhuwcsNwmHw
Strange,
Seems that request was not logged.
Anyway,
by the request,
the account was attached.
req_Lq3b4GX9gYBWkg
Sorry.
This is the last
request.
Ah, okay, I see what you're saying. Hang on...
Wait, maybe I don't see. ๐
So this request worked: https://dashboard.stripe.com/test/logs/req_Lq3b4GX9gYBWkg
What's the request ID of the one that failed?
Ah, okay, so that request has the opposite problem; it's a Connect request but it shouldn't be.
Meaning in your Node code you should not specify the account ID there.
Actually, wait, there are several issues here...
Which line of code led to this error?
Are you trying to update the existing external account or replace it with a new one?
Ah, okay, so that's the issue. You're using the update function when you're trying to replace it instead.
You need to make another API call just like this one: https://dashboard.stripe.com/test/logs/req_Lq3b4GX9gYBWkg
Whatever code you used for that API call is what you need to do here as well.