Adds new error codes for required verificationsBreaking changes
What’s new
Adds the following error codes to the requirements. array in the Accounts API, Capabilities API, Persons API, and Bank Accounts API.
information_missing invalid_signator verification_failed_ authorizer_ authority verification_rejected_ ownership_ exemption_ reason
The information_ error code is more generic than previous error codes. Use the associated requirement and reason fields to learn what information is missing. For example, some Singapore accounts might see:
// GET /v1/accounts/{{CONNECTED_ACCOUNT_ID}} { ... "requirements": { "currently_due": ["documents.proof_of_ultimate_beneficial_ownership.files"], "errors": [ { "code": "information_missing", "requirement": "documents.proof_of_ultimate_beneficial_ownership.files", "reason": "We identified that your business is owned by holding companies that require additional information to be collected. Please provide documents that include information for each applicable holding company. For more information, see https://support.stripe.com/questions/beneficial-ownership-verification-for-holding-companies. The new holding companies we have identified are: ACME INC." } ], ... }, ... }
We return the invalid_ error if you uploaded a Letter of Attestation as your proof of Ultimate Beneficial Ownership document, and we couldn’t verify the professional body that notarized the document.
{ ... "requirements": { "currently_due": ["documents.proof_of_ultimate_beneficial_ownership.files"], "errors": [ { "code": "invalid_signator", "requirement": "documents.proof_of_ultimate_beneficial_ownership.files", "reason": "We could not verify the professional certifying body of this document." } ], ... }, ... }
We return the verification_ error if you designated a Person as the authorizer on your account and we couldn’t verify their position of authority within your company. See Representative Authority Verification for more information.
{ ... "requirements": { "currently_due": ["{{AUTHORIZER_PERSON_TOKEN}}.relationship.authorizer"], "errors": [ { "code": "verification_failed_authorizer_authority", "requirement": "{{AUTHORIZER_PERSON_TOKEN}}.relationship.authorizer", "reason": "The authority of the authorizer could not be verified. Authorizers must be one of Director, Chief Executive Officer listed on acra.gov.sg." } ], ... }, ... }
We return the verification_ error if you submitted an exemption for providing your Ultimate Beneficial Owners, and we rejected the exemption request.
{ ... "requirements": { "currently_due": ["documents.proof_of_ultimate_beneficial_ownership.files"], "alternatives": [ { "original_fields_due": ["documents.proof_of_ultimate_beneficial_ownership.files"], "alternative_fields_due": ["company.ownership_exemption_reason"], } ], "errors": [ { "code": "verification_rejected_ownership_exemption_reason", "requirement": "company.ownership_exemption_reason", "reason": "The ownership exemption reason was rejected." } ], ... }, ... }
Why is this a breaking change?
Some Connect integrations might require an update to handle the new error codes.
Impact
You’ll be able to handle new error codes for the upcoming requirement updates in Singapore.