> ## 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. # Paymentech Configuration | Payment Provider | Geographies | Currencies | Payment Methods | Retain Support | Automatic Chargeback Feed | Account Updater | API Version | Microservice? | | - | - | - | - | - | - | - | - | - | | (Chase) Paymentech Payment Processor | US-Based Merchants | All | \*\*Credit/Debit Cards -\*\**Yes* **SEPA DD**- *No* **Tokenized Credit Card**- *Yes, Safetech Tokens* **Hosted Pages** - *No* **Alternative Payments** - *No* **Digital Wallets** - *Yes, Apple Pay, Google Pay* | **Tokenized Credit Card** - *Yes* **Network Token** - *Yes* **Detokenize PAN** - *Yes* **Detokenize BIN**- *Yes* **Partial Auth** - *Yes* **Forced Deposit** - *Yes* | Yes | Yes Real -Time AU also supported if merchant enabled | 3.0 | No | ## Required Merchant Information \[ ]\(../images/Paymentech.xlsx) | Name | Expected Value | Value | Description | | - | - | - | - | | Paymentech:divisionNumber | | | Division number(s) from merchant (can route multiple divisions) | | Does provider need to whitelist IPs | No | | | | Does a merchant need to grant access to Vindicia | Yes | | Production PID: 029305 Staging PID: 053174 | | Chargeback Feed | Yes | | Need DFR form | | Account updater | Yes | | | | A trial with Chase Paymentech requires that the merchant email their Chase Paymentech representative requesting that Vindicia be authorized to submit transactions and refunds to the Chase Paymentech Salem platform on behalf of the merchant. | | | | The merchant performs this by requesting that Vindicia’s Presenter Id (PID)\[1] be mapped to their merchant account (company id). The email contents described below will be emailed to the merchant. This asks the merchant forward the email to their Chase representative so that the necessary configuration in Chase can be made. Vindicia **MUST** be copied on the email to Chase so that we can confirm that the configuration changes have been performed based on the response back from the Chase representative. *Vindicia cannot present transactions until this configuration has been completed.* **Processor approval email contents:** This email formally authorizes Vindicia, Inc. (“Vindicia”), acting on our behalf, to submit transactions against our Company ID number and Division ID numbers. Please map Vindicia’s PID and/or Submitter ID as follows: * Our Company ID: ***\[INSERT HERE]*** * Vindicia’s PID: **029305** * Vindicia’s Submitter ID: **105745** Vindicia will be submitting transactions against the following Division ID’s: * Division ID: ***\[INSERT AS APPLICABLE]*** * Division ID: ***\[INSERT AS APPLICABLE]*** ## Desired Merchant Configuration | Name | Value | Comments | | - | - | - | | Paymentech:mccNumber |   | MCC code from merchant | | Paymentech:customerServiceNumber |   | CS number for billing descriptor, from merchant. | | Paymentech:auth\_response\_priority |   | The order that authorization response codes are prioritized when deciding to retry Transactions. Supported Authorization Response Codes: Payment Provider (auth\_code) Response (P), MAC Merchant Advice code for Visa cc or Mastercard (M), Network Response (N) | * **[Paymentech Merchant Setup Instructions](../topics/paymentechConfiguration_r#)** * **[Paymentech Detailed Information on Integration](../topics/paymentechConfiguration_r#)** **Parent topic:**[Payment Provider Specific Configuration](../topics/PaymentProvidersSpecificConfiguration) ## Paymentech Merchant Setup Instructions The following Instructions are written for Vindicia CTS and services delivery staff. To configure a merchant to use Paymentech 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 Paymentech to **Merchant Payment Providers**: | Payment Provider Name | Account Number | PP Type | Active | | - | - | - | - | | Paymentech (1010) | \ | BRD(1) | 1 | | Paymentech (1010) | \ | Chargeguard(2) | 1 | 1. Select **Paymentech (1010)** as the payment provider and click **ADD**. 2. Set **Account Number** to merchant ID from Chase. 3. Set **PP Type** as **BRD**. 4. Set **Active** to **1**. 5. For a chargeback feed, set the **PP Type** as **Chargeguard** and set **Active** to **1**. ### Routing Rule 1. Add a **Routing Rule** for Paymentech. | Ordinal | Payment Provider | Value | Rule Method | Active | | - | - | - | - | - | | 1 | Paymentech (1010) |   | default\_method(1) | 1 | 1. Select **Paymentech (1010)** 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:**[Paymentech Configuration](../topics/paymentechConfiguration_r#) ## Paymentech Detailed Information on Integration Vindicia supports the following Payment Operations for Paymentech: | 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 | (Via Cardinal Commerce) | | 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 | Yes |   | | 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 | Also supports Real-time Account Updater if merchant-enabled. See [NVP](https://docs.vindicia.com/bundle/subscribeMerchantConfiguration/page/topics/accountUpdaterNVP_r.html) for RT AU enablement | | Automated/manual chargeback feed | Yes |   | | **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 | Yes |   | | Support Forced Deposit | Yes |   | ### Payment Provider Documentation Link to Paymentech API guides: (need to sign up) [https://developer.jpmorgan.com/](https://developer.jpmorgan.com/) **Parent topic:**[Paymentech Configuration](../topics/paymentechConfiguration_r#) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.