> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integration-guide/workflows/fraud-and-risk-management.md).

# Fraud & Risk Management

Effectively enhance fraud detection with your preferred FRM engine

The Juspay Hyperswitch Fraud and Risk Management (FRM) workflow offers a comprehensive Unified API designed to cater to your specific payment validation needs, effectively enhancing fraud protection within your payment ecosystem.

### Key Benefits of FRM workflows

* Processor-Agnostic Integration: Single API connect lets you seamlessly connect with an FRM solution of choice.
* Customized Fraud Strategies: Enables users to adjust fraud prevention measures by allowing them to select between Pre-Auth and Post-Auth checks based on specific payment methods and connectors.
* Unified Dashboard: A consolidated interface that displays all flagged transactions, making decision-making on potential frauds a breeze.
* Real-Time Alerts: Immediate notifications are sent when potential fraudulent activity is detected, ensuring quick action and minimal losses.
* Insightful Analytics: Detailed reports on fraud patterns help inform decisions and strategy adjustments.

### Use cases for implementing FRM workflows

* Online Marketplaces: Secure transactions on e-commerce platforms, regardless of payment methods or processors. Benefit from chargeback guarantees, dispute resolution, account security, real-time fraud alerts, and streamlined fraud investigation tools.
* High-Value Transactions: Protect high value orders in luxury retail, or high-end custom services. Ensure payment validity, prevent chargebacks, optimize PSD2 compliance, reduce transaction friction, gain valuable fraud trend insights, and utilize predictive fraud analysis.

### Supported FRM workflows

| Pre-authorization flow                                                                                                                                 | Post-authorization flow                                                                                                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The Pre-Auth flow is executed before payment authorization. This flow is supported for any payment method. Actions supported are: Continue on `Accept` | The Post-Auth flow occurs after payment authorization by the processor. This flow is supported for only cards payment method. Actions supported are: Continue to `Accept`, Halt on `Decline`, Approve/Decline on `Review` |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integration-guide/workflows/fraud-and-risk-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.