#NickH
orchid stirrup
You're just trying to update business_profile via the API, right?
sharp wagon
So what I want to do is by the time we get to the onboarding process for new Stripe account, I want the product_description to be pre-filled so the user doesnt have to do it...
for Stripe Express
orchid stirrup
Are you using OAuth or Account Links for onboarding?
orchid stirrup
Okay, good. I'm looking at your code and I'm a bit confused about what all of this is doing. It also looks like you're trying to fetch() Stripe, but that request will likely fail with a CORS error, no?
sharp wagon
done via Zapier
Server-side via NodeJS in a Zapier action
I'm just following the API docs 🙂
its basically setting the parameters to urlform-encoded and then POSTing them off to Stripe's API
if I remove the part about business_profile it works
Bit I want prepopulated...
orchid stirrup
Which line is throwing this error Invalid object param: business_profile
sharp wagon
ah thats what the Zapier console said was the output back from Stripe
from your servers
Maybe I could try creating the account and then calling a separate update API call?
or maybe could try using 'individual' ...
orchid stirrup
Did the attempt generate a Request ID on Stripe's side?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
orchid stirrup
Ah, okay. So you're passing in an object literal, instead of the key-value pairs that the API is expecting.
sharp wagon
hmmm maybe it needs to be business_profile[production_description]
orchid stirrup
Yeah, that might be worth a try
sharp wagon
product*
yes I think it works one sec
OK I think it worked - it doesnt ask for the product description in onboarding anymore
orchid stirrup
Woo!
sharp wagon
Developer Feedback: Update the API doc to specify that you may need to use "business_profile[product_description]" rather than business_profile.production_description
just a thought 🙂
product_description*
(the latter seems more natural to me as a dev of 10+ years)
((that's just me though!))
orchid stirrup
Which doc are you looking at?
sharp wagon
all the entries there it has object.field notation
hence why I tried that in the first instance 😉
orchid stirrup
Totally valid feedback. Happy to raise that
sharp wagon
Thanks!
can I ask - is it wise to populate the website field too as well as product description?
or is it only necessary to provide product description
(just tihnking for your KYC processes etc.)
orchid stirrup
The account should already have a URL via a different attribute on the account object, but I don't see any reason why it would be a bad idea to populate it in a description
sharp wagon
"I operate as a Sleepfriend, which is someone who helps people relax deeply and fall asleep via video/audio call. I get paid by Sleepfriend.org who provide me with clients."
howzat?
would that be OK for your KYC process?
PS. couldve totally done with a Sleepfriend last night, v tired today!
orchid stirrup
We don't have a lot of KYC visibility, so I can't say if that would help (though I'd be surprised if it contributed to KYC at all)
If you want to ask more KYC questions, you may want to reach out to support: https://support.stripe.com/contact
sharp wagon
Ah ok... what I meant was, would that description be sufficient for Stripe, in principle?
sterile epochBOT
sharp wagon
for the suppliers who create Stripe Accounts
"I operate as a Sleepfriend, which is someone who helps people relax deeply and fall asleep via video/audio call. I get paid by Sleepfriend.org who provide me with clients."
orchid stirrup
Yes, that would be fine, but again: I don't know what KYC requirements are in play here, as we can only really speak to the developer side of things. That description is fine though.
sharp wagon
Thanks 🙂
How could I check? Shall I email support @ ?
One more thing -on reauth - is it OK to create a new account object via /account again? I'm guessing it doesnt get persisted in your DB until onboarding is finished
wheat rampart
Yes, you can contact support for specific guidance on description and whats appropriate for your platform & accounts: https://support.stripe.com/contact (you can submit via the webform there instead of emailing)
You can create accounts as needed, sure. They'll stick around even if not onboarded, but in a disabled state when test/live verification info is not provided.
sharp wagon
OK thanks 🙂 maybe to keep it clean Ill try to pass the account ID in the reauth URL
trust that'll be OK
(then can resubmit and get a new redirect URL via Ajax or something to a Zapier hook)
wheat rampart
Yes if you need to do further onboarding, you'd want to auth via your own logic before provide the sensitive account link
sharp wagon
we will email the onboard link so that should suffice...
wheat rampart
Passing account ID is fine. YOu can also use some internal proxy for it, but up to you. IDs are safe to expose, just not keys.
sharp wagon
perhaps on reauth we can have "Email the link to me again"
if they click, it the redirect URL gets regenerated and emaailed again
wheat rampart
Yea up to you how that flow works --the account links are short-lived though so any emailed ones are likely to expire before being used, pushing through the re-auth flow. Instead you could email a link yo auth on your site then generate the account link & redirect after that, but up to you
sharp wagon
that could work also 🙂
nice idea
so email our own link - and our own link on the fly does regeneration of redirect link etc and then redirects
bit of simple JS should do it I hope...
AJAX call to a Zapier hook + window.location or whatever
*With a fallback of "Click here if youre not redirected"