Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Overview
Start an integration
Products
Global Payouts
Capital
Issuing cards
    Overview
    How Issuing works
    Global availability
    Manage fraud
    Cards
    Choose your card type
    Virtual cards
    Issue virtual cards
    Physical cards
    Manage cards
    Digital wallets
    Replacement cards
    Card programs
    Program management
    Customize your card program
    Add funds to your card program
    Credit Consumer Issuing
    Controls
    Spending controls
    Advanced fraud tools
    3DS
    Fraud challenges
    Real-time authorizations
    PIN management
    Issuing Elements
    Token Management
    Funding
    Balance
    Postfund your integration with Stripe
    Postfund your integration with Dynamic Reserves
    Purchases
    Authorizations
    Transactions
    Disputes
    Testing
    Merchant categories
    ATM Usage
    Issuing with Connect
    Set up an Issuing and Connect integration
    Update terms of service acceptance
    Connect funding
    Connected accounts, cardholders, and cards
    Embed card management UI
    Credit
    Overview
    Set up connected accounts
    Manage credit terms
    Report other credit decisions and manage AANs
    Report required regulatory data for credit decisions
    Manage account obligations
    Test credit integration
    Additional information
    Choose a cardholder type
    Customer support for Issuing and Treasury
    Issuing watchlist
    Marketing guidance (Europe/UK)
    Product and marketing compliance guidance (US)
Treasury
Manage money
HomeMoney managementIssuing cards

Issuing watchlist

Learn about the Issuing watchlist process and best practices.

Copy page

Stripe automatically screens Issuing users against US and international sanctions lists. For Issuing, we screen all relevant data. Screening can occur based on events such as:

  • Onboarding
  • Updates to sanction lists
  • Creation or update of cardholders

If automated screening flags a user, Stripe opens a manual review for them. Our team reviews any flagged cardholders, and updates information about these cardholders within 24 hours. During the review, this process might impact your business, and all cards decline authorizations with the cardholder_verification_required reason.

Integrating with watchlist events

Make sure your integration listens to the issuing_cardholder.updated webhook events. This is how we notify you when an interesting event occurs.

  1. When a user creates or updates a cardholder, Stripe updates the requirements.disabled_reason to under_review. This notifies the user that a screening is underway.

    "requirements": { "disabled_reason": "under_review", "past_due": [] }
  2. In most cases, we clear the cardholder in a few seconds through our automated review system.

    "requirements": { "disabled_reason": null, "past_due": [] }
  3. If a cardholder might be on a prohibited persons or companies list, we update the requirements.disabled_reason to listed. The past_due field contains information you need to provide before the cardholder can approve authorizations.

    "requirements": { "disabled_reason": "listed", "past_due": [ "individual.dob.day", "individual.dob.month", "individual.dob.year" ] }

    In the Dashboard under Issuing > Cardholders, a banner appears at the top of the page reflecting the information in the requirements.disabled_reason attribute noted above.

    Stripe also sends an email notification to you to provide more information to expedite the verification process. Its a good practice, to monitor the email that you have on file with Stripe.

  4. Stripe might reject the Cardholder if the user is on a third-party prohibited persons or companies list (such as a financial services provider or a government entity). We update the requirements.disabled_reason to rejected.listed. Additionally, the status will be blocked.

    "requirements": { "disabled_reason": "rejected.listed", "past_due": [] }, "status": "blocked", "type": "individual"

Best practices

  • Provide the date of birth when creating cardholders. When our systems raise reviews on Issuing Cardholders without a date of birth, analysts must contact the Issuing platform or the cardholder to obtain this information.
  • For Issuing cardholders, you can order an optional physical card. Be aware that we only ship a physical card after completing the watchlist screening process at onboarding and determining that it doesn’t hit the watchlist.

See also

  • Issuing: Watchlist reviews support
Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc