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

# Paysafe Configuration

| Payment Provider | Geographies | Currencies | Payment Methods | Retain Support | Automatic Chargeback Feed | Account Updater | API Version | Microservice? |
| - | - | - | - | - | - | - | - | - |
| Paysafe Payment Processor | Global | [Supported Currencies List](https://developer.paysafe.com/en/rest-apis/card-payments/card-not-present/test-and-go-live/) | \*\*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**- *Yes* **Partial Auth** - *No* **Forced Deposit** - *Yes* | No | No | V1 | Yes |

## Required Merchant Information

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

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

| Name | Expected Value | Value | Description |
| - | - | - | - |
| PaySafe:account | 1002234150 |   |   |
| PaySafe:password | 1002643614 |   |   |
| PaySafe:username | 1002643614 |   |   |
| Does provider need to whitelist IPs | No |   |   |
| Does a merchant need to grant access to Vindicia | No |   |   |
| Chargeback feed | No |   |   |
| Account Updater | No |   |   |

## Desired Merchant Configuration

| Name | Value | Comments |
| - | - | - |
| PaySafe: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). |

* **[Paysafe Merchant Setup Instructions](../topics/paysafeConfiguration_r#)**

* **[Paysafe Detailed Information on Integration](../topics/paysafeConfiguration_r#)**

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

## Paysafe Merchant Setup Instructions

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

To configure a merchant to use Paysafe 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 Paysafe to **Merchant Payment Providers**:

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

   1. Select **Paysafe (1055)** 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 Paysafe.

   | Ordinal | Payment Provider | Value | Rule Method | Active |
   | - | - | - | - | - |
   | 1 | Paysafe (1055) |   | default\_method(1) | 1 |

   1. Select **Paysafe (1055)** 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

The below api\_key value is an example for Vindicia internal testing and should not be shared with merchants.

| ID | Name | Value |
| - | - | - |
| 100012273 | Paysafe:username | vindrestwsdev |
| 100012274 | Paysafe:password | vindrestwsdev1! |
| 100012275 | Paysafe:account | 44 |

**Parent topic:**[Paysafe Configuration](../topics/paysafeConfiguration_r#)

## Paysafe Detailed Information on Integration

Vindicia supports the following Payment Operations for JusPay:

| 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 |   |
| 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 | Yes |   |
| 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 | No |   |
| Support Card Type identification (from BIN or API) | Yes | This is an internal function and not exposed to merchants. |
| Support Visa/general "Stored Credential" flags | Yes |   |
| Account Updater/Amex Card refresher | Yes | Direct Connect to AMEX |
| Automated/manual chargeback feed | No |   |
| **Retain Support** |   | |
| Support token as payment method | Yes |   |
| Support detokenization to full PAN | No |   |
| Support detokenization to get BIN | Yes |   |
| Support Partial Authorization | No |   |
| Support Balance Retrieval | No |   |
| Support Forced Deposit | Yes |   |

### Payment Processor Documentation

Links to docs:

* [https://developer.paysafe.com/en/cards/api/#/reference/0/authorizations](https://developer.paysafe.com/en/cards/api/#/reference/0/authorizations)

**Parent topic:**[Paysafe Configuration](../topics/paysafeConfiguration_r#)


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