> 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/integrations/connectors-integrations/fraud-providers/signifyd.md).

# Signifyd

Integrate Signifyd fraud and risk management with Juspay Hyperswitch to automate fraud decisions and protect against chargeback liability.

Signifyd connects to Hyperswitch as a `FraudAndRiskManagementProvider`. It provides AI-driven commerce protection with guaranteed fraud liability coverage — Signifyd takes on chargeback liability for orders it approves. Signifyd is not a payment processor; it evaluates orders independently of payment authorization.

### Authentication

Signifyd uses `HeaderKey` authentication — a single API key sent as a Bearer token on every request.

| Credential  | Description                                                                                 |
| ----------- | ------------------------------------------------------------------------------------------- |
| **API Key** | Bearer token issued by Signifyd. Found in your Signifyd merchant portal under API settings. |

### FRM Flows

Signifyd participates in the following Hyperswitch FRM flows:

| Flow             | Description                                                                    |
| ---------------- | ------------------------------------------------------------------------------ |
| **Sale**         | Pre-authorization fraud check on the payment attempt                           |
| **Checkout**     | Fraud evaluation at checkout, before payment is submitted                      |
| **Transaction**  | Post-authorization evaluation of a completed transaction                       |
| **Fulfillment**  | Signal to Signifyd that an order has been fulfilled (triggers liability shift) |
| **RecordReturn** | Notify Signifyd of a return or refund on a previously approved order           |

### Webhook Events

Signifyd sends decision updates via webhook. Hyperswitch handles HMAC-SHA256 signature verification using the API key.

### Common Failure Modes

**Decision not returned** Symptom: FRM evaluation times out or returns no decision. Fix: Check Signifyd's merchant portal for order status. Ensure the order details (email, address, line items) are complete — incomplete orders are often held or declined by Signifyd.

**Liability shift not applied** Symptom: Signifyd approves the order but chargeback liability is not shifted. Fix: Verify the Fulfillment flow is being called after shipment. Liability shift typically requires a fulfillment signal.

***

### Activating Signifyd via Hyperswitch

#### Prerequisites

1. A registered Signifyd merchant account. Contact [signifyd.com](https://www.signifyd.com/) for onboarding.
2. A registered Hyperswitch account, accessible from the [Hyperswitch control center](https://app.hyperswitch.io/).
3. API Key from the Signifyd merchant portal.

[Steps to activate a connector on the Hyperswitch control center](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md)

***

Connector implementation: `crates/hyperswitch_connectors/src/connectors/signifyd.rs`.


---

# 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/integrations/connectors-integrations/fraud-providers/signifyd.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.