> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CyberSource Configuration

| Payment Provider | Geographies | Currencies | Payment Methods | Retain Support | Automatic Chargeback Feed | Account Updater | API Version | Microservice? |
| - | - | - | - | - | - | - | - | - |
| CyberSource Payment Provider | Global | All | \*\*Credit/Debit Cards -\*\**Yes* **SEPA DD**- *No* **Tokenized Credit Card**- *Yes* **Hosted Pages** - *No* **Alternative Payments** - *No* **Digital Wallets** - *No* | **Tokenized Credit Card** - *Yes* **Detokenize PAN** - *Yes* **Detokenize BIN**- *Yes* **Partial Auth** - *Yes* **Forced Deposit** - *Yes* | No | No | 1.216 | No |

## Required Merchant Information

\[<img src="https://mintcdn.com/amdocs-slm/ifa3y22T11JlqvtT/portal/vindiciaSubscribeAndNewRetain/subscribePaymentProviderIntegration/images/download_button.png?fit=max&auto=format&n=ifa3y22T11JlqvtT&q=85&s=74864737190e56d2ac71f7232f0900ac" alt="" width="150" height="38" data-path="portal/vindiciaSubscribeAndNewRetain/subscribePaymentProviderIntegration/images/download_button.png" />

]\(../images/CyberSource.xlsx)

| Name | Expected Value | Value | Description |
| - | - | - | - |
| CyberSource:merchantId |   |   | Merchant division ID from processor |
| CyberSource:transactionKey |   |   | Merchant transaction key from processor |
| Does provider need to whitelist IPs | No |   |   |
| Does merchant need to grant access to Vindicia | No |   |   |
| Chargeback feed | No |   |   |
| Account Updater | No |   |   |

## Desired Merchant Configuration

| Name | Value | Comments |
| - | - | - |
| CyberSource:initialSelectTransactionIdForReferenceCode | 0/1 | If enabled, we will send original failed transaction ID as reference field in the request to CyberSource. Recommended value is 1. |
| CyberSource:auth\_response\_priority | | The order that authorization response codes are prioritized when deciding to retry Transactions. Supported Authorization Response Codes: Payment Provider Response (P) and MAC (M) - Visa and Mastercard codes |
| vin: FraudProvider | | Select which fraud provider is in use. Valid values can include:- decision\_manager - fraud\_management\_essential If **fraud\_management\_essential** is used, then AuthService is disabled for CyberSource.**Note:** Only required for Merchants using Decision Manager or Fraud Management Essentials. |
| CyberSource:fraud\_rule\_flag | merchantDefinedData\_mddField\_XX | Defines which MDD field to send the Transaction type to. The Transaction types are classified as:- CardVerification - RealTimePayment - RecurringPayment The **merchantDefinedData\_mddField\_XX** can have a numeric value between 1-100. |

* **[CyberSource Merchant Setup Instructions](../topics/cyberSourceConfiguration_r#)**

* **[CyberSource Detailed Information on Integration](../topics/cyberSourceConfiguration_r#)**

**Parent topic:**[Payment Provider Specific Configuration](../topics/PaymentProvidersSpecificConfiguration)

## CyberSource Merchant Setup Instructions

The following Instructions are written for Vindicia CTS and services delivery staff.

To configure a merchant to use CyberSource payment processor:

### Merchant Payment Providers

1. In Subscribe Portal 1.0, using you’re admin account, go to **Admin** > **Merchant Configurations**.
2. Select the relevant **Merchant** from the drop-down list.
3. Click **Edit Merchant Configurations**.
4. Enter the **Jira Ticket #** for configuring your merchant payment setup.
5. Add CyberSource to **Merchant Payment Providers**:

   | Payment Provider Name | Account Number | PP Type | Active |
   | - | - | - | - |
   | CyberSource (1036) | \<blank> | BRD(1) | 1 |

   1. Select **CyberSource (1036)** as the payment provider and click **ADD**.
   2. Leave **Account Number** blank.
   3. Set **PP Type** as **BRD**.
   4. Set **Active** to **1**.

### Routing Rule

1. Add a **Routing Rule** for CyberSource.

   | Ordinal | Payment Provider | Value | Rule Method | Active |
   | - | - | - | - | - |
   | 1 | CyberSource (1036) |   | default\_method(1) | 1 |

   1. Select **CyberSource (1036)** as the payment provider and click **ADD**.
   2. Add an **Ordinal** value of **1**.
   3. Leave **Value** blank.
   4. Add a **Rule Method** value of **default\_method(1)**.
   5. Set **Active** to **1**.

      **Note:** If the test payment provider is configured, set its **Active** value to **0**.

**Note:** If a merchant account is set up with several payment providers, the payment provider with highest **Ordinal** value has priority. If routing will be shared amongst payment providers, see [Configuration Method - Payment Providers Routing Rules](routingRulesAbout) for examples of possible configurations.

### Name/Value Pairs

Add the required configuration details in **Name/Value Pairs** for the CyberSource configuration.

CyberSource Keys are masked in the portal unless you are in edit mode.

Cybersource keys can be rotated automatically (custom dev done for ATTCAPM)

**Note:** The **ID** is automatically generated and **Value** for each **Name/Value Pair** is unique and must be provided by the merchant. The following is an **example** of **Name/Value Pairs** for an CyberSource configuration.

| ID | Name | Value |
| - | - | - |
| 100005113 | CyberSource:merchantId | vindicia3ds |
| 100005114 | CyberSource:transactionKey | XXXXXXXXXXXXXXX |

**Parent topic:**[CyberSource Configuration](../topics/cyberSourceConfiguration_r#)

## CyberSource Detailed Information on Integration

Vindicia supports the following Payment Operations for CyberSource:

| Payment Operation | Yes/No | Notes |
| - | - | - |
| **Standard Implementation Features** | | |
| Verification (no Auth) | Yes |   |
| Minimal Authorization (\$0) policies, by card type) | Yes |   |
| AVS check with standard result mapping | Yes |   |
| CVV/CVN check with standard result mapping | Yes |   |
| Support real-time authorization (stand-alone Auth) | Yes |   |
| Void | Yes |   |
| Cancel/reverse authorization | Yes |   |
| Conditional deposit (auth and capture combination) | Yes |   |
| Capture (stand-alone capture) | Yes |   |
| One-time transactions (real-time) | Yes |   |
| Recurring transactions (flagged recurring) | Yes |   |
| Refunds - Full | Yes |   |
| Refunds - Partial | Yes |   |
| 3DS | Yes |   |
| CITMIT/Card On File | Yes |   |
| Map error/response/result codes to standard actions (Success/Decline/Reject) | Yes |   |
| **Special Implementation Features** |   | |
| Implemented via Payments Microservice | No |   |
| Retrieve and store paymentProcessorTransactionId | Yes |   |
| Retrieve and store Extended Card/Auth Attributes | No |   |
| Support tokenization (for Retain) | Yes |   |
| Support BIN/Last-4/Expiry Retrieval from external Token | Yes |   |
| Support detokenization (Subscribe retrieves full PAN/CC details | Yes |   |
| Support Card Type identification (from BIN or API) | Yes | This is an internal function that Vindicia uses. It is not exposed to the merchant via the API. |
| Support Visa/general "Stored Credential" flags | Yes |   |
| Account Updater/Amex Card refresher | Yes |   |
| Automated/manual chargeback feed | No |   |
| **Retain Support** |   | |
| Support token as payment method | Yes |   |
| Support detokenization to full PAN | Yes |   |
| Support detokenization to get BIN | Yes |   |
| Support Partial Authorization | Yes |   |
| Support Balance Retrieval | No |   |
| Support Forced Deposit | Yes |   |

### Payment Provider Documentation

Link to CyberSource Simple Order API guides: [https://developer.cybersource.com/api/soap-developer-guides.html](https://developer.cybersource.com/api/soap-developer-guides.html)

**Parent topic:**[CyberSource Configuration](../topics/cyberSourceConfiguration_r#)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.