ThunderTix logo

Support Forum

How Can I Control Card Authorization Settings in Stripe? - Tue - Jan 20, 2026 - 12:45pm

  • ThunderTix integrates directly with Stripe for credit card processing, and many authorization and fraud-prevention settings are managed within your Stripe dashboard

    While ThunderTix submits transactions to Stripe, approval or decline decisions are ultimately made by the card networks and issuing banks, based on the rules you configure in Stripe. 


    Common Stripe authorization settings you can manage
     

    Within your Stripe dashboard, you can review and adjust: (we HIGHLY recommend these extra step to prevent fraudulent ticket buyers)

    • Address Verification (AVS) checks
      Require the billing street address and ZIP code to match what the card issuer has on file.

    • CVC (card security code) checks
      Decline or review transactions where the CVC does not match.

    • Radar fraud rules
      Create rules to block or review transactions based on:

      • Country

      • IP address

      • Card behavior

      • Risk score

      • Repeated attempts

    • Authentication settings (3D Secure)
      Add an extra layer of verification for higher-risk transactions.


    Where to find these settings in Stripe
     
    1. Log in to your Stripe Dashboard

    2. Navigate to Settings

    3. Select Payments and Fraud

    4. Review options under Radar, Risk controls, and Authentication


    Stripe allows you to fine-tune how strict or flexible your authorization rules are, depending on your organization’s tolerance for risk.
     
    Important notes
     
    • ThunderTix cannot override Stripe authorization decisions.

    • Declines labeled as “generic” or “do not honor” typically come from the card issuer, not ThunderTix.

    • Tightening fraud rules may reduce fraud but can also increase false declines.


    If you’re unsure which settings are best for your organization, Stripe’s documentation and support team can help you evaluate your options.

    To read more about blocking fraudulent purchasers, please read the article below: