Cybersource Decision Manager

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

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.

Cybersource Decision Manager screens transactions for fraud. Only the fraud-check flows are implemented, checkout and transaction. Every payment flow behind the block is an empty implementation: Authorize, PSync, Capture, Void, refund Execute and RSync 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: 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(), get_webhook_event_type() and get_webhook_resource_object().

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 and Cybersource Decision Manager transformers.