#atob-yash
sharp raft
unique urchin
Can you be more specific - what errors are you seeing on the account?
sullen tiger
If you look at the payload associated with that event id:
"requirements": {
"errors": [
{
"code": "verification_failed_tax_id_match",
"reason": "The information on your account could not be verified with the IRS. Please either correct any possible errors in the company name, tax ID, or upload a document containing those fields. Please refer to this support article on verifying tax ID numbers: https://support.stripe.com/questions/using-irs-documentation-as-reference-when-entering-business-name-and-tax-id-number-tin-for-us-based-businesses",
"requirement": "company.tax_id"
}
],
"past_due": [
"external_account"
],
"alternatives": [
],
"currently_due": [
"company.tax_id",
"external_account"
],
"eventually_due": [
"company.tax_id",
"external_account"
],
"disabled_reason": "requirements.past_due",
"current_deadline": 1683479578,
"pending_verification": [
]
},
Earlier, when an account had a error present, the capability would not be active
unique urchin
aha! gotcha - give me a few minutes to look into that
sullen tiger
Sounds good, thank you!
sullen tiger
Any luck @unique urchin ?
unique urchin
Sorry got a bit busy in the channel - from what I can tell, these specific requirements don't actually affect the card_issuing capability. Missing the external_account disables payouts, which is reflected in the account as payouts_enabled: false
sullen tiger
No, I was talking about verification_failed_tax_id_match which is in the errors object, not the past due in requirements
unique urchin
Do you have a different example where verification_failed_tax_id_match changed the card_issuing capability?