Accéder directement au contenu
Créez un compte
ou
connecter-vous
Logo de la documentation Stripe
/
Demander à l'assistant IA
Créez un compte
Connectez-vous
Démarrer
Paiements
Revenus
Plateformes et places de marché
Gestion de fonds
Outils de développement
Aperçu
Gestion des versions
Journal des modifications
    Présentation
    Basil
    Acacia
    Versions précédentes
Mettre à niveau votre version de l'API
Actualiser votre version du SDK
Outils de développement
SDK
API
Tests
Workbench
Destinations d'événements
Workflows
CLI Stripe
Shell Stripe
Dashboard des développeurs
Boîte à outils des agents
Intégrer des LLMStripe pour Visual Studio CodeAlertes d'intégrité de StripeChargements de fichiers
Sécurité et confidentialité
Sécurité
Confidentialité
Extensions Stripe
Stripe Apps
Connecteurs Stripe
Partenaires
Partner ecosystem
Certification des partenaires
AccueilOutils de développementChangelogBasil2025-03-31.basil

Remarque

Cette page n'est pas encore disponible dans cette langue. Nous faisons tout notre possible pour proposer notre documentation dans davantage de langues et nous vous fournirons la version traduite dès qu'elle sera disponible.

Adds new error codes for required verificationsBreaking changes

What’s new

Adds the following error codes to the requirements.errors 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_missing 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_signator 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_failed_authorizer_authority 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_rejected_ownership_exemption_reason 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.

Changes

valeursModifierénumérations
information_missinginvalid_signatorverification_failed_authorizer_authorityverification_rejected_ownership_exemption_reasonAjouté
Account.future_requirements.errors[].codeAccount.requirements.errors[].codeBankAccount.future_requirements.errors[].code
 + 5 de plus
BankAccount.requirements.errors[].codeCapability.future_requirements.errors[].codeCapability.requirements.errors[].codePerson.future_requirements.errors[].codePerson.requirements.errors[].code

Upgrade

  1. View your current API version in Workbench.
  2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
    • If you don’t use an SDK, update your API requests to include Stripe-Version: 2025-03-31.basil
  3. Upgrade the API version used for webhook endpoints.
  4. Test your integration against the new version.
  5. If you use Connect, test your Connect integration.
  6. In Workbench, perform the upgrade. You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Cette page vous a-t-elle été utile ?
OuiNon
Besoin d'aide ? Contactez le service Support.
Rejoignez notre programme d'accès anticipé.
Consultez notre log des modifications.
Des questions ? Contactez l'équipe commerciale.
LLM ? Lire llms.txt.
Propulsé par Markdoc