#harish-account-fieldsneeded

1 messages · Page 1 of 1 (latest)

torn oyster
#

Hey @nocturne epoch fields_needed is pretty legacy (deprecated in February 2019). Do you have more specific details?

nocturne epoch
#

@torn oyster thanks for your reply. To be more specific the API response includes this data:

"verification": {
...
"fields_needed": [
"legal_entity.additional_owners",
"legal_entity.personal_address.city",
"legal_entity.personal_address.line1",

"legal_entity.personal_address.postal_code",
"legal_entity.personal_address.state"
],

#

Based on this data, we are showing a message to the user that their Stripe account needs some details to be submitted to complete the verification

torn oyster
#

Sure so what's the blocker? We do need more details for that account to continue accepting payments

nocturne epoch
#

The point is that when logged into that Stripe account, we don't see any issues. The account is fully active and payments are being processed for more than 2 years now. So it feels like what the API returns as fields_needed is misleading for the account.

Similiar issue exists for few other connected Stripe accounts. The API says some fields are needed for verification and we show the message accordingly in our application dashboard. But when the owner of the Stripe account logs into Stripe they don't see any issue in their account. So we have neem receiving complaints from our users about the message that we are displaying based on the fields_needed.

Maybe I am missing something. Is it right to display to our users that stripe needs some details to be submitted, based on fields_needed?

torn oyster
#

Regulations change over time though and we might need more details. My understanding was that we reached out to affected platforms about this