> ## 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.

# Elavon Configuration

| Payment Provider | Geographies | Currencies | Payment Methods | Retain Support | Automatic Chargeback Feed | Account Updater | API Version | Microservice? |
| - | - | - | - | - | - | - | - | - |
| Elavon Payment Processor | [Supported Counties List](https://www.elavon.com/country-selector.html) | [Supported Currencies List](https://developer-eu.elavon.com/docs/dcc/supported-dcc-currencies) | \*\*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** - *No* **Detokenize BIN**- *No* **Partial Auth** - *Yes* **Forced Deposit** - *No* | Yes | No | 1.0 | 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/Elavon.xlsx)

| Name | Expected Value | Value | Description |
| - | - | - | - |
| Elavon:ssl\_merchant\_id |   |   | Merchant/Division ID from Elavon. Can be used for routing. |
| Elavon:ssl\_user\_id | VindiciaAPI |   | Will be this value for all merchants |
| Elavon:ssl\_pin |   |   | PIN for each merchant ID. Used for routing. |
| Elavon:ssl\_vendor\_id | sc777001 |   | This will be the value for all merchants. |
| Elavon:ssl\_partner\_app\_id | BP |   | This will be the value for all merchants. |
| Does provider need to whitelist IPs | No |   |   |
| Does a merchant need to grant access to Vindicia | No |   |   |
| Chargeback feed | Yes |   |   |
| Account Updater | No |   |   |

## Desired Merchant Configuration

| Name | Value | Comments |
| - | - | - |
| Elavon:multi\_currency |   | Binary, comes from merchant |
| Elavon:sftp\_username |   | For chargebacks, comes from merchant |
| Elavon:sftp\_password |   | For chargebacks, comes from merchant |

* **[Elavon Merchant Setup Instructions](../topics/elavonConfiguration_r#)**

* **[Elavon Detailed Information on Integration](../topics/elavonConfiguration_r#)**

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

## Elavon Merchant Setup Instructions

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

To configure a merchant to use Elavon payment provider, do the following:

### Define Elavon as Payment Provider

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 Elavon to **Merchant Payment Providers**:

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

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

### Define Elavon Routing Rule

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

   | Ordinal | Payment Provider | Value | Rule Method | Active |
   | - | - | - | - | - |
   | 1 | Elavon (1070) |   | default\_method(1) | 1 |

   1. Select **Elavon (1070)** 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.

**Parent topic:**[Elavon Configuration](../topics/elavonConfiguration_r#)

## Elavon Detailed Information on Integration

Vindicia supports the following Payment Operations for Elavon and in the following geographical areas:

| Payment Operation | Yes/No | Notes |
| - | - | - |
| **Standard Implementation Features** | | |
| Verification (no Auth) | Yes | ccverify |
| 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 | ccauthonly |
| Void | Yes | ccvoid |
| Cancel/reverse authorization | Yes | ccvoid |
| Conditional deposit (auth and capture combination) | Yes |   |
| Capture (stand-alone capture) | Yes |   |
| One-time transactions (real-time) | Yes |   |
| Recurring transactions (flagged recurring) | Yes | ssl\_recurring\_flag |
| Refunds - Full | Yes | Using ccreturn |
| Refunds - Partial | Yes |   |
| 3DS | No |   |
| CITMIT/Card On File | Yes | Support CITMIT |
| 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 | No |   |
| Support detokenization (Subscribe retrieves full PAN/CC details | No |   |
| 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 | No |   |
| Account Updater/Amex Card refresher | Yes | We connect directly to AMEX. Merchant must have it enabled at Amex. |
| Automated/manual chargeback feed | Yes | Via an Elavon add-on "payment core 365 platform" merchant must subscribe. |
| **Retain Support** |   | |
| Support token as payment method | Yes |   |
| Support detokenization to full PAN | No |   |
| Support detokenization to get BIN | No |   |
| Support Partial Authorization | Yes |   |
| Support Balance Retrieval | Yes |   |
| Support Forced Deposit | No |   |

### Payment Processor Documentation

Links to docs:

* [https://developer.elavon.com/na/docs/converge/1.0.0/overview](https://developer.elavon.com/na/docs/converge/1.0.0/overview)

**Parent topic:**[Elavon Configuration](../topics/elavonConfiguration_r#)


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