#MarcusStripe
shell anchor
opal stag
The issue is the postal code, as the error indicates
It's not the line 1 address
We do perform some validation on postal codes by country to ensure they meet expected formats, where we can
You can omit the postal code if you don't have a valid one, but for testing purposes any DE postal code would work
In terms of detection and surfacing, the error contains this info:
code: "postal_code_invalid",
doc_url: "https://stripe.com/docs/error-codes/postal-code-invalid",
message: "Invalid DE postal code",
param: "company[address][postal_code]",
You can key on that code
lost coyote
Is tha tthe only thing validated, as I asked?
opal stag
I'm not aware of other validation, but its possible. Are you encountered other errors?
lost coyote
No... but that doesnt mean there couldnt be others... I have the issue right now with the postcode.. and if I dont handle it in some way.. then the customer will see a 500 server error
so I am currently thinking of either just leaving out the postcode.. or leaving out the entire company address in the prefill
that would mean that the customer has to type it twice.. but on the other hand.. my assumption might be wrong anyway -
On our end... this address is the INVOICE address.. but that could differ from the legal company address, I guess
When I create a Stripe connect account from my backend..
is there a time when the customer looses the ability to create an onboarding link, to finish up the account creation,
or will it sit and wait basically forever?
Because, at the moment, our customers apply, and we will async check and decide about the application,
and then initiate Stripe connect account creation from our end... but maybe I should instead only
(in the positive case) enable them to initiate the account creation from their end,
followed by a account onboarding link creation shortly after?
opal stag
You should be able to wait before sending them through onboarding to finish up, if needed
lost coyote
?
this was a bit unspecific, unfortunately
Lets give an example - the onboarding link we create just in type when the user clicks the link on our end and then forward the suer to the stripe url... to prevnet it from expiring... which it can.
the account itself -
when not finished up with all necessary data - can it expire in some way?
like created today, no create onboarding link used, no data send.. will the account still be as it was.... 1 year later?
opal stag
The actual onboarding link expires, yes if that's what you mean. they are short lived, but you can generate another later when needed.
The account itself can sit without onboarding for some time, though i don't know about a year. If it was a year before the account onboarded, i might suggest deferring your account creation
Depending on where you get in the onboarding, and what kind of verification requirements are created, you may hit due dates that lead to disablement:
https://stripe.com/docs/api/accounts/object#account_object-requirements-current_deadline