> 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/payment-processor-capabilities/available-connectors/cybersourcedecisionmanager.md).

# Cybersource Decision Manager

Cybersource Decision Manager runs fraud screening. It does not process payments.

{% hint style="warning" %}
**This connector does not process payments.** Decision Manager is Cybersource's fraud screening service, and that is all this connector implements. The matrix labels it a live payment gateway, which is a declaration rather than a capability.
{% endhint %}

Cybersource Decision Manager screens transactions for fraud. Only the fraud-check flows are implemented, [checkout](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L439) and [transaction](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L533). Every payment flow behind the block is an empty implementation: [`Authorize`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L405-L408), [`PSync`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L410-L413), [`Capture`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L414-L417), [`Void`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L419-L422), refund [`Execute`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L424-L427) and [`RSync`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L429) all fall through to the interface default, which builds no request. Sending a payment to this connector does nothing.

It is also not offered in the control center, so there is no activation form and the shared activation guide does not apply. Arrange setup with the Hyperswitch team.

### Status and capabilities

**Integration status:** live

**Category:** payment gateway

**Webhook flows:** None declared in code

*This connector declares no payment methods. It is a payment gateway rather than a payment processor.*

### Authentication

The connector accepts three credentials as a `SignatureKey` triple, mapped by [`CybersourcedecisionmanagerAuthType`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager/transformers.rs#L68-L92): an API key, a merchant account, and an API secret.

There are no control-center labels to quote for them. Cybersource Decision Manager has no entry in `crates/connector_configs/toml/`, in any environment, which is the same reason it does not appear in the connector list. Ask the Hyperswitch team which values to supply and in what form.

### Before you start

Contact the Hyperswitch team. There is no dashboard setup for this connector, and no connector configuration defines its credential labels, so there is nothing to prepare in the control center. Have your Cybersource Decision Manager account details to hand for that conversation.

### Webhooks

Webhooks are not supported, so there is no event list and nothing to configure. All three handlers return `WebhooksNotImplemented`: [`get_webhook_object_reference_id()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L630-L635), [`get_webhook_event_type()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L637-L643) and [`get_webhook_resource_object()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs#L645-L650).

There is nothing to fall back on for payment status either, since the payment and sync flows are unimplemented too. Fraud-check status is the exception: the fraud-check flows return fraud screening outcomes (legitimate, fraud, manual review) from Cybersource responses.

### Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch `502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5`. See [Cybersource Decision Manager connector source](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager.rs) and [Cybersource Decision Manager transformers](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/cybersourcedecisionmanager/transformers.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/payment-processor-capabilities/available-connectors/cybersourcedecisionmanager.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.