LogoLogo
Explore with DeepWikiJoin Slack CommunityContact Us
  • About Hyperswitch
    • Exploration Guide
    • Overview
    • Payments Suite
    • Payments Modules
      • Cost Observability
      • Revenue Recovery
      • Vault
        • Server to Server Vault tokenization
        • Vault SDK Integration
        • Hyperswitch Vault: Pass Through Proxy Payments
      • Intelligent Routing
      • Reconciliation
        • Getting Started with Recon
      • Alternate Payment Method Widgets
        • Hyperwidget Integration Guide
    • Roadmap - Q2 2025
      • Previous Roadmap - Q1 2025
      • Previous Roadmap - Q4 2024
      • Previous Roadmap - Q3 2024
      • Previous Roadmap - Q2 2024
      • Previous roadmap - Q1 2024
      • Previous roadmap - Q4 2023
  • Use-Cases
    • For SaaS Businesses
    • For B2B SaaS Businesses
    • For E-Commerce Businesses
    • For Marketplace/Platforms
  • Explore Hyperswitch
    • Payment Orchestration
      • Accept Payments
        • Connectors
          • Activate Connector on Hyperswitch
          • Try a Payment
          • Available Connectors
            • ACI
            • Adyen
            • Airwallex
            • Authorizedotnet
            • Bambora
            • Bank of America
            • Billwerk
            • Bluesnap
            • Braintree
            • Checkout
            • Coinbase
            • Cybersource
              • Apple Pay
              • Google Pay
            • dLocal
            • Fiserv
            • GlobalPayments
            • GoCardless
            • Klarna
            • Mollie
            • MultiSafepay
            • Nuvei
            • OpenNode
            • Paypal
            • PayU
            • Prophetpay
            • Rapyd
            • Shift4
            • Stripe
            • TrustPay
            • Volt
            • Worldline
            • Worldpay
            • Zen
            • Netcetera
              • Authenticating Payments via Netcetera Through HyperSwitch SDK
        • Setup Payment Methods
          • Cards
          • Wallets
            • Apple Pay
              • Web Domain
              • iOS Application
            • Google Pay
            • PayPal
          • Pay Later
          • Banks
            • Bank Debits
            • Bank Redirects
            • Bank Transfers
            • Open Banking
          • Crypto
          • Test Credentials
        • Payment Links
          • Configurations
          • Create Payment Links
          • Secure Payment Links
          • Setup Custom Domain
        • Save a Payment Method
        • Manual Capture
        • Incremental Authorization
        • Tokenization & Card Vault
          • Network Tokenisation
        • Supported Payment Workflows
        • Co-badged Cards
        • Webhooks
      • Process Payouts
        • Getting Started with Payouts
        • Using Saved Payment Methods
        • Smart Router for Payouts
        • Smart Retries in Payout
        • Payout Links
      • Smart Routing
        • Rule Based Routing
        • Volume Based Routing
        • Default Fallback Routing
      • Smart Retries
        • 3DS Step-up Retries
      • 3DS / Strong Customer Authentication
        • Setting up 3DS Decision Manager
        • Native 3DS Authentication
        • External Authentication for 3DS
      • Fraud & Risk Management
        • Activating FRM in Hyperswitch
        • Fraud Blocklist
      • Subscriptions
        • PG Agnostic Card Forwarding
        • Zero Amount Authorization
      • Split Payments
        • Stripe Split Payments
        • Adyen Split Payments
        • Xendit Split Payments
    • Checkout Experience
      • Customizable and Native Integrations
        • Web
          • Node And React
          • Customization
          • Error Codes
          • Node and HTML
          • Vanilla JS and REST API Integration
        • Android
          • Kotlin with Node Backend
          • Customization
          • Features
        • iOS
          • Swift with Node Backend
          • Customization
          • Features
        • React Native
          • React Native with Node Backend
          • Card Widget
          • Customization
        • Flutter
          • Flutter with Node Backend
          • Customization
        • Headless SDK
        • Server Setup
      • Click To Pay
        • Visa Click to Pay: V1 to V2 Migration
      • Payment Methods Management
    • Payment Operations
      • Managing Accounts and Profiles
        • ⚙️Control Centre Account setup
        • Hyperswitch Account Structure
      • Manage Your Team
      • Analytics & operations
        • Exporting payments data
      • Disputes / Chargebacks
      • Surcharge
        • Surcharge Setup guide
      • Multi-Tenancy
      • Data migration
        • Import data to Hyperswitch
        • Export data from Hyperswitch
    • Security and Compliance
      • PCI Compliance
      • Data Security
      • GDPR compliance
      • Identity and Access Management
    • E-commerce Platform Plugins by Hyperswitch
      • 🔌WooCommerce Plugin
        • Setup
        • Roadmap
        • Compatibility
        • FAQs
      • Saleor App
        • Setup
      • Automatic Tax calculation for Express Checkout wallets
  • Hyperswitch open source
    • Overview
      • Run Hyperswitch Locally Using Docker
        • Run Additional Services
      • Development Environment Setup
        • Backend
          • Configure and Run the Application
          • Try out APIs
        • SDK (Frontend)
        • Control Center
    • Deploy on AWS
      • Deploy on AWS using CloudFormation
      • Component-wise Deployment
        • Deploy app server
        • Deploy Control Center
        • Deploy web client
          • Production ready deployment
          • Integrate web client on your web app
          • Playground deployment for prototyping (optional)
        • Deploy Card Vault
          • Production ready deployment on AWS
          • Cloud setup guide
    • Deploy on Kubernetes
      • Deploy on GCP Using Helm Charts
      • Deploy on Azure Using Helm Charts
    • Account setup
      • Using Hyperswitch Control Center
      • Test a payment
      • Using postman
    • Troubleshooting
  • Testing Payments
  • Check list for Production
    • Going live
      • For SaaS Setup
      • For On-Prem Setup
        • Monitoring
        • PCI compliance
          • Get started
          • Completing the SAQ
        • Data Security
        • Updates
  • Learn more
    • API Reference
    • Connectors Supported
    • SDK Reference
      • React
      • JS
      • Custom Events
    • Hyperswitch architecture
      • Router
      • Storage
      • A Payments Switch with virtually zero overhead
    • Payment flows
    • Blog
  • Community Guidelines
Powered by GitBook

Compliance

  • Vulnerability Disclosure
  • PCI DSS 4.0
  • ISO 27001:2022

Community

  • Slack
  • Discord
  • GitHub Discussion
On this page
  • Pre-Authorization Flow
  • Post-Authorization Flow
  • FRM status and decisions
  • How to Get Started with Hyperswitch FRM Integration

Was this helpful?

  1. Explore Hyperswitch
  2. Payment Orchestration
  3. Fraud & Risk Management

Activating FRM in Hyperswitch

You can enable the FRM solution of your choice with few clicks and very minimal code changes. Below are the two scenarios for activating FRM within Hyperswitch.

Prerequisites

Before activation, ensure the following:

  1. Payment Method Information: Required for configuration.

  2. FRM Solution Signup: Obtain API keys from your selected FRM provider.

Pre-Authorization Flow

The Pre-Auth flow is executed before payment authorization. When a customer initiates a payment, transaction details are analyzed by the FRM solution to assess risk using parameters like historical behavior, location, transaction patterns, and device data.

  • Goal: Prevent fraudulent transactions before authorization.

  • Steps:

    1. Transaction details are sent to the FRM solution for analysis.

    2. Based on the risk score or recommendation, actions are taken:

      • Continue on Accept: Proceed with the transaction.

      • Halt on Decline: Mark the transaction as cancelled.

Post-Authorization Flow

The Post-Auth flow occurs after payment authorization by the processor. It serves as a second validation layer, analyzing the transaction using updated and historical data to detect potential fraud.

  • Goal: Act as a safety net for suspicious transactions.

  • Steps:

    1. Post-authorization details are sent to the FRM solution.

    2. Transactions flagged as fraudulent are queued for manual review.

    3. Merchants review and decide whether to:

      • Continue on Accept: Continue with the transaction.

      • Halt on Decline: Mark the transaction as cancelled.

      • Approve/Decline on Review:

        • Hold the transaction in manual review state. Merchants can list and review such transactions.

        • If approved: Capture the payment.

        • If declined: Void the payment.

If the connector doesn’t support manual capture, Post-Authorization manual review should be avoided during configuration setup for the respective connector.

FRM status and decisions

FRM connectors generally provide a decision based on rules or data models along with a risk score associated with the transaction. Some integrations require providing the model to be used explicitly. For example, Signifyd can be configured to respond with only scores or decision + scores, etc.

Fraud detection can be done via the below methods:

  • Rules: Uses a static set of rules for deciding on the outcome.

  • Scores: Uses a range of numbers for associating risk with the transaction.

  • Decisions/Recommendations: Uses ML data models for predicting and recommending the outcome.

  • Chargeback Guarantee: Uses ML data models for responding with a binary outcome (Accept vs Decline).

Currently, Hyperswitch offers only a single way of integrating with the underlying FRM connector:

  • Signifyd: Decision/Recommendation.

  • Riskified: Chargeback guarantee.

How to Get Started with Hyperswitch FRM Integration

  1. Log in to Your Hyperswitch Account

  2. Navigate to the 'Fraud & Risk' Tab

    • Select the Fraud and Risk Management (FRM) processor you want to integrate.

  3. Configure Payment Methods and Actions

    • Set up the payment methods and define preferred actions for each enabled payment method.

  4. Provide API Credentials

    • Enter the API credentials for the selected FRM processor.

  5. Integrate and Test

    • Start testing payments with fraud checks to ensure the setup works as expected.

FAQs

What are the prerequisites for integrating with the Hyperswitch FRM platform?

Depending on your chosen FRM processor, you may need to pass additional parameters, such as order fulfillment data, via a webhook to Hyperswitch. Refer to the relevant documentation for detailed instructions.

Can I adjust fraud prevention measures based on specific payment methods and connectors?

Yes, the Hyperswitch FRM platform allows customization of fraud prevention strategies. You can configure pre-authorization and post-authorization checks for individual payment methods and processors, along with their corresponding actions.

Last updated 4 months ago

Was this helpful?

Access your .

Access the to integrate the FRM API.

Hyperswitch account
API Documentation
Test a payment