#sayori-oauth-express
1 messages ยท Page 1 of 1 (latest)
You can't really force them to add a mailing address. We only collect the information that's necessary
Also you really shouldn't use OAuth, it's been deprecated for quite a while
Just create the account via the API and use AccountLink to send them to Stripe to enter all the information they need to
Turns out this information is necessary for tax purposes though, because Stripe doesn't support sending these tax forms electronically for us
Another member in our org reached out, and apparently got this response:
"Enable the address of your connected Stripe accounts to appear on your Stripe dashboard . You need to manually fill this via your API. You can follow this guidelines for your reference: https://stripe.com/docs/api/persons/object#person_object-address
You can also update your OAuth workflow here: https://stripe.com/docs/connect/oauth-express-accounts
This will ensure that during the time you send your OAth to your connected account the field for address is visible for them to fill in."
can you weigh in on the viability of this?
turns out they thought we were talking about emails
yeah I don't get what that answer could mean
taking a step back: what's a "mailing address" in the first place?
An address at which a user may potentially receive tax forms (1099s)
So the address of a company is collected here: https://stripe.com/docs/api/accounts/object#account_object-company-address
and it's a requirement during onboarding
So you must mean something else but I don't follow what. Maybe you have an account manager and are in a secret feature or something? (in which case we can't help here)
That field sounds right, but it's optional in account creation - and I just created an account but can't find a place to add an address on my account in Stripe (connect.stripe.com/app/express is where I'm at)
https://stripe.com/docs/connect/required-verification-information
There are a lot of factors that control what is and isn't collected (country, account type, business type, capabilities, etc.)
I think the best option will be to go back to our support team and ask for further help from them. I don't really grasp what you are describing and what's blocking you. If we don't collect the address upfront it means we don't need it, and will in the future, but there's no way to force require that information in that case. But our support team will be better equipped to look at concrete example accounts and help you debug this directly
Ok, thanks for your help!
sure, sorry I couldn't help more!
all good, this is probably an older system that is in a weird state ๐
Feel free to keep talking here!
Earlier I said that our current entry point is via a OAuth account creation - this was incorrect
So we correctly use API+AccountLink.
On the other hand, I did find an older implementation of Stripe account creation in website that uses OAuth. This one actually correctly requires address upon account creaiton
Basically, I'm trying to determine how that one is correctly requiring address, while our new flow doesn't require address - and how I can adapt our new flow to also require address
I noticed that with the older flow, I'm able to skip adding the address by not filling any fields, but the Stripe Express dashboard shows a place for me to add address and indicates that this is required information before I receive a payout as a customer
On the other hand, the new flow (using API+AccountLink) does not have this menu for adding address. After Name + SSN fields above, it only shows a field for DOB and ID Verification
It also turns out that email support thought we were talking about emails in a prior instance, so we can disregard that message
With account links we determine what is the minimum amount of information we need to collect from the connect accounts, so it's very possible that for those accounts we just don't believe a mailing address is required at that point in time
Do you have an example request where you're creating an account? I just want to take a quick look
I just made a dummy one with account acct_1KK5nfRcd8GATWNc
^I tried something slightly different there - added company={address: {}} as a parameter in the account creation step
Do you want the method call I used to create this account?
No that's okay - let me take a look at what you've already provided
I'm not the most familiar with this, but is there a reason you're using the following in your request:
upfront: {
0: {
disables: "payouts_and_payments"
}
},
0 for tax_id right?
I think this is in order to disable payouts/payments until tax_id is given.
I took a look here: https://stripe.com/docs/connect/required-verification-information#US-full-individual--tax_reporting_us_1099_misc|transfers
with the tax_reporting_us_1099_misc requirement, address is required but only after $599 USD in earnings. I wonder if this is a difference between incremental vs upfront onboarding here?
Ah, you're using a gated feature - I think what's happening here is that by passing in disables: "payouts_and_payments" you're saying you don't want to collect any information that is solely needed for those capabilities until a later point in time. That may be why address is not being collected. Trying removing that and see what happens
I see. Let me try that.
to clarify, change the request so that it says;
"upfront": [],
"requested": True
or just entirely remove the upfront field?
Trying removing upfront entirely
๐
removed upfront, got this error:
Request req_mnrDfJMQO9n53N: Additional verifications must be specified with a threshold.
also tried upfront: [] and got the same error
dang - yeah I'm not exactly sure how this feature works since it's gated
thanks for the help anyway ๐ I'll play around from here, this is a lead
Yeah I do think we're on the right track - you can see in the link you gave https://stripe.com/docs/connect/required-verification-information#US-full-individual--tax_reporting_us_1099_misc|transfers that address is something that is needed specifically for the payouts capability. But the payouts capability has been disabled up front by the request you've made (https://stripe.com/docs/connect/set-additional-verifications#upfront is the gated doc).
If you have a contact that helped get you gated into this feature I'd suggest reaching out to them as well to get help from folks who know more about it