Mehdei

[valid vapor]

(moving into thread to clear main thread) It's optional to provide in the API call, but it will be required eventually to allow for business transactions.

The API documentation only defines the requirements of the actual API calls, not the legal requirements for accounts.

[undone aspen]

Hi, that is expected per legal requirements. The API just shows what is required to pass.

[fast summit]

thanks for you guys, I understand

Sorry to bother you, one more quastion.. It's about accept the terms of service for this connect standard account
how to accept it via my web app (not via stripe web pages), because Stripe pages inforce the user to login with his email and unset password

[valid vapor]

I'm pretty sure that for STANDARD accounts (which are independent entities/businesses) Stripe has to record the TOS after the user has completed onboarding.

Same for Express. For Custom accounts (where the Platform is fully responsible), the platform can provide this setting

[fast summit]

So, I have to use the custom accounts to avoid Stripe pages

[valid vapor]

to avoid Stripe pages completely? Pretty much, yeah - but you take on a LOT more responsibility if you do.

Usually, the support engineers here only recommend Custom accounts if you have a very extensive development team.

I use Express - for day-to-day operations, my "sellers" have no need to look at Stripe pages - but for PCI compliant issues, and PII information, I rely on Stripe to represent the "very best" in security to make my sellers comfortable

[fast summit]

you are correct, thank you so much bro, and sorry to bother you 😊

[valid vapor]

No bother at my end - I troll here a fair bit to catch issues I hadn't thought of yet during development