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
Démarrer une intégration
Produits
Global Payouts
Capital
Émission de cartes
    Présentation
    Fonctionnement d'Issuing
    Disponibilité mondiale
    Gérer la fraude
    Cartes bancaires
    Choisir votre type de carte
    Cartes virtuelles
    Cartes physiques
    Gérer des cartes bancaires
    Portefeuilles électroniques
    Cartes de remplacement
    Programmes de cartes
    Gestion de programme
    Issuing pour les prestataires de paiement
    Personnaliser votre programme de cartes
    Ajoutez des fonds à votre programme de cartes
    Credit Consumer Issuing
    Contrôles
    Contrôles des dépenses
    Outils antifraude avancés
    3DS
    Étapes de détection de la fraude
    Autorisations en temps réel
    Gestion des PIN
    Issuing et Elements
    Gestion des tokens
    L'obtention de financements
    Solde
    Post-financer votre intégration à Stripe
    Post-financer votre intégration avec les réserves dynamiques
    Achats
    Autorisations
    Transactions
    Litiges
    Tests
    Catégories de marchands
    Utilisation des distributeurs automatiques
    Données enrichies sur les marchands
    Issuing avec Connect
    Configurer une intégration pour Issuing et Connect
    Mettre à jour les Conditions d'utilisation du service
    Financement Connect
    Comptes connectés, cartes et titulaires de carte
    Désinscription des comptes connectés inactifs
    Intégrer l'interface utilisateur pour la gestion des cartes
    Crédit
    Présentation
    Configurer des comptes connectés
    Gérer les conditions de crédit
    Enregistrer d'autres décisions de crédit et gérer les avis de décision défavorable (AAN)
    Communiquer les données réglementaires requises pour les décisions de crédit
    Gérer les obligations des comptes
    Tester une intégration de crédit
    Informations complémentaires
    Choisir un type de titulaire de carte
    Service de support dédié à Issuing et Treasury
    Liste de surveillance Issuing
    Recommandations pour le marketing (Europe/Royaume-Uni)
    Recommandations pour la conformité des produits et du marketing (US)
      Communications client
      Validation des adresses pour la gestion des fonds
Treasury
Gérer vos fonds
AccueilGestion de fondsIssuing cardsProduct and marketing compliance guidance (US)

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.

Validate addresses for money management products

Learn how to submit address information that meets Stripe validation standards.

Effective July 1, 2025, all current and future Issuing, Treasury, Opal and Corporate Card accounts must meet enhanced validation for business and account representative addresses. These controls detect and prevent addresses associated with the use of registered agents, physical mailbox services, and virtual address services.

Remarque

Corporate Card is integrated with Opal. Opal is Stripe’s private preview money management account that enables businesses to store money with Stripe, send or receive money using ACH and wire in the US, save recipients to pay bills, and make payments toward an Opal balance.

Types of addresses subject to validation

  • Registered agent addresses: Designated locations where a third party receives legal documents and government notices on behalf of a business. Many companies use registered agent services, especially when operating in states where they don’t have a physical presence.

  • Commercial Mail Receiving Agency addresses: Private businesses that provide mailbox rental and mail forwarding services, such as UPS Stores, FedEx Office locations, or virtual mail services.

Physical address requirements

To comply with financial partner requirements, Stripe verifies that all accounts have a physical presence in the United States. This means Stripe can no longer allow addresses for registered agents, mailbox services, or virtual address services. These requirements apply to both:

  • The business entity’s address, regardless of the business type.
  • The address of the account representative.

Address validation

Stripe enforces several types of address validation for Issuing, Treasury, Opal and Corporate Card.

Existing validations

Stripe already validates and enforces that addresses are:

  • Valid and deliverable US addresses.
  • Not PO Boxes, Highway Contract Boxes, or private mailboxes.

New validations

Stripe is adding two new address validation requirements:

  • Not a Commercial Mail Receiving Agency (CMRA) address
  • Not a registered agent address

These new validations focus on addresses that might be technically valid but don’t represent a genuine physical business presence.

Address validation process

Starting July 1, 2025, new merchants onboarding to Issuing, Treasury, Opal or Corporate Card must provide a compliant physical address that meets all validation criteria. Stripe blocks onboarding until you provide a valid physical address.

Existing merchants

Existing merchants using Issuing, Treasury, Opal or Corporate Card with addresses that Stripe has identified as registered agent or CMRA are:

  • Notified about the address validation issue.
  • Given a 30-day grace period to meet the requirement.

If you don’t update the address within this period, Stripe disables account capabilities until you provide a valid address.

Integrate address validation

If the address validation fails, Stripe notifies you in the following ways:

  • You receive an email from Stripe that outlines the incomplete requirements.

  • A user task and banner appear in your Dashboard with instructions to update the address or submit supporting documents.

    • For connected accounts, Stripe lists the incomplete requirements on the Connect Accounts page.
  • If you have a webhook integration, you receive an account.updated webhook event with details in the requirements object.

Below are some examples of the requirements section you will find in Accounts API or account.updated webhook event when your address is flagged.

CMRA addresses

For a business address:

{ "requirements": { "current_deadline": null, "currently_due": [ "company.address.line1" ], "errors": [ { "code": "invalid_address_private_mailbox", "reason": "The address you provided appears to be associated with a mailbox or virtual address service, which we can't accept. Please update your address to proceed.", "requirement": "company.address.line1" } ], "eventually_due": [ "company.address.line1" ], "past_due": [ "company.address.line1" ], "pending_verification": [] } }

For a representative’s address:

{ "requirements": { "current_deadline": null, "currently_due": [ "person123.address.line1" ], "errors": [ { "code": "invalid_address_private_mailbox", "reason": "The address you provided appears to be associated with a mailbox or virtual address service, which we can't accept. Please update your address to proceed.", "requirement": "person123.address.line1" } ], "eventually_due": [ "person123.address.line1" ], "past_due": [ "person123.address.line1" ], "pending_verification": [] } }

To remediate, update your business address to a physical location where you operate. You can’t use CMRA addresses and there isn’t an appeal process.

Registered agent addresses

For a business address:

{ "requirements": { "alternatives": [ { "alternative_fields_due": [ "company.address.line1" ], "original_fields_due": [ "documents.proof_of_address.files" ] } ], "currently_due": [ "documents.proof_of_address.files" ], "errors": [ { "code": "verification_address_registered_agent_address", "requirement": "documents.proof_of_address.files", "reason": "The address you provided appears to be associated with a registered agent, which we can't accept. Please update your address to proceed." } ], "eventually_due": [ "documents.proof_of_address.files" ], "past_due": [ "documents.proof_of_address.files" ], "pending_verification": [] } }

For a representative’s address:

{ "requirements": { "alternatives": [ { "alternative_fields_due": [ "person123.address.line1" ], "original_fields_due": [ "person123.verification.additional_document" ] } ], "currently_due": [ "person123.verification.additional_document" ], "errors": [ { "code": "verification_document_failed_other", "requirement": "person123.verification.additional_document", "reason": "The address you provided appears to be associated with a registered agent, which we can't accept. Please update your address to proceed." } ], "eventually_due": [ "person123.verification.additional_document" ], "past_due": [ "person123.verification.additional_document" ], "pending_verification": [] } }

To remediate, update your address to a physical location where you operate.

Test the integration

Use the following value in address line1 field of the Accounts API or Person API to trigger different scenarios in testmode.

Descriptionline1
CMRA address. The address requirement won’t be satisfied.Address CMRA
RA address. The address requirement won’t be satisfied.Address RA
Normal address. The address requirement will be satisfied.Any non PO Box, HC Box, or PMB address.

Voir aussi

  • Physical presence requirement FAQ
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