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

# Vindicia Internal Notes for Subscribe 2023.07 Release

Production Release Date: August 2, 2023

**Parent topic:**[Vindicia Subscribe - 2023.07 Release](2023.07_tp_subscribeReleaseNotes)

## Report Features

### New internal\_bin\_etc Database Table

With this release, changes were made to ensure seamless compatibility between the BIN details received and the card types displayed in our reports. We have introduced a new table, **internal-bin-etc**, which allocates BINS to their respective banks and countries. This table provides more precise and reliable analytic data and facilitates better decision-making. The **bin\_detail** and **internal\_bin\_etc** tables are kept together based on whether **internal\_bin\_id** is null in the **credit\_card** table.

As part of this update, the **prod\_prep** and **report** now display data from the **internal-bin-etc** and **bin\_detail** tables.

(CAT-85)

## Payments Features

### Chase Paymentech Integration - New Name/Value Pairs to Support Real-Time Account Updater

Real-Time Account Updater by Chase Paymentech updates the transaction response when they are available. Depending on the Account Updater response, Vindicia may immediately retry the transaction with new card information.

To support the upcoming certification of Real-Time Account Updater for Chase Paymentech, the **Paymentech:paymentech\_enable\_RTAU** Name/Value Pair has been created to bypass the Real-Time Account Updater response until Vindicia can handle the response code in a future release.

(VIN-18346)

### Litle Integration - Chargeback API Updates

With this release, the chargeback feed API endpoint for the Litle integration has been updated.

* Was: [https://services.vantivcnp.com/services/communicator/chargebacks/webCommunicator](https://services.vantivcnp.com/services/communicator/chargebacks/webCommunicator)
* Now: [https://services.vantivcnp.com/services/chargebacks](https://services.vantivcnp.com/services/chargebacks)

The structure of the response has also been changed. The previous chargeback details were returned with a **caseActivity** tag. The new response is now **ChargebackCase**, and the activity tag comes under it. We can also get multiple **caseActivity** responses under the **ChargebackCase** response.

Example response:

```
 <chargebackCase>
        <caseId>261184676657311</caseId>
        <merchantId>4230552</merchantId>
        <dayIssuedByBank>2023-04-27</dayIssuedByBank>
        <dateReceivedByLitle>2023-04-26</dateReceivedByLitle>
        <litleTxnId>8472932401614181</litleTxnId>
        <cycle>First Chargeback</cycle>
        <orderId>215939562_20</orderId>
        <cardNumberLast4>xxxx</cardNumberLast4>
        <cardType>MasterCard</cardType>
        <chargebackAmount>xxxx</chargebackAmount>
        <chargebackCurrencyType>USD</chargebackCurrencyType>
        <originalTxnDay>2023-04-10</originalTxnDay>
        <chargebackType>D</chargebackType>
        <reasonCode>4837</reasonCode>
        <reasonCodeDescription>No Cardholder Authorization</reasonCodeDescription>
        <currentQueue>Merchant</currentQueue>
        <acquirerReferenceNumber>xxxx</acquirerReferenceNumber>
        <chargebackReferenceNumber>9162191662</chargebackReferenceNumber>
        <merchantTxnId>160411967314436</merchantTxnId>
        <bin>541071</bin>
        <historicalWinPercentage>32</historicalWinPercentage>
        <paymentAmount>8388</paymentAmount>
        <replyByDay>2023-06-06</replyByDay>
        <activity>
            <activityDate>2023-04-26</activityDate>
            <activityType>Receive Network Transaction</activityType>
            <fromQueue>New</fromQueue>
            <toQueue>Litle</toQueue>
            <settlementAmount>8388</settlementAmount>
            <notes>9162191662</notes>
        </activity>
        <activity>
            <activityDate>2023-04-26</activityDate>
            <activityType>Assign To Merchant</activityType>
            <fromQueue>Litle</fromQueue>
            <toQueue>Merchant</toQueue>
            <settlementAmount>8388</settlementAmount>
            <notes>Auto assigned - Provide proof that you have a positive AVS (address +5or 9 zip match) and that you shipped to this same AVS approved address; or that a credit was processed; or that issuer did not respond to your CVC2 request (response U)</notes>
        </activity>
    </chargebackCase>
```

(VIN-23547)

## Security Features

### Enhanced Key Management and Encryption Algorithm

Enhancements to Vindicia's internal Credit Card security were made. These comply with PCI requirements and prioritize security.

This update includes:

* Upgraded RSA 4096 Encryption Algorithm using OpenSSL, providing stronger data security.
* Improved AWS Key Management Service (KMS) Integration, ensuring centralized and robust key management.
* Enhanced handling of cryptographic keys to prevent plaintext exposure.
* Transition to Role-based Credentials for encryption servers and lockdown of AWS KMS key to decrypt data exclusively on authorized servers, minimizing potential vulnerabilities.

This is an internal security enhancement and does not affect merchants.

(VIN-20823)

### Account Hashing - **Dark Mode**

For PCI compliance, Vindicia has enhanced the internal security hashing algorithm from SHA1 to SHA512. This upgrade is vital for maintaining the security of our platform and protecting user data.

The new SHA512 algorithm provides a more robust cryptographic hash function that reduces the risk of collision attacks and brute-force attacks. This ensures that hashed sensitive information is more secure and less susceptible to security breaches.

This feature is released in dark mode to assess any potential merchant impact.

(VIN-13001)

## Internal Fixes

The following issues were solved in this release:

| Ticket | Title | Description |
| - | - | - |
| PORT-3175 | Subscribe Merchant Portal 2.0 - Path Field for SFTP Configuration Not Required for Running Recurring Reports | The **Path** field was not a required field when users were running recurring reports and selected **Upload report to SFTP server**. This issue has been fixed. |
| VIN-24266 | SYSERROR Related to Hashing | Multiple SYSERRORs were caused by a non-existent hashes function in CreditCard.pm. The non-existent **creditCard** > **hashes** call has been removed without affecting functionality. |
| VIN-23925 | Expired Campaign Codes Added to Subscriptions | Users were able to apply expired campaigns to both new and existing subscriptions. This issue has been fixed. |
| PORT-3240 | Subscribe Merchant Portal 2.0 - In Billing Invoice Format Dropdown List Unable for Second Time Value Selection | An error occurred when users selected values in Billing Invoice Format dropdown list for a second time while creating a new subscription. This issue was fixed. |
| PORT-3255/3234/3229/3212/3211 | Stackable Discount Fixes | The following changes were made to improve stackable discounts in Subscribe: - For stackable discount related invoices, the **Total** value on the **Invoice** page **Total** was blank. This issue was fixed. - In **Subscription Items**, when item was expanded an additional **Campaign** field appeared. This issue was fixed. - **Invoice** pages with a status of **Overdue** and **Paid** appeared blank for merchants that enabled stackable discounts. This issue was fixed. - The **Campaign ID** value sometimes overlapped with the next attribute for merchants that enabled stackable discounts. This issue was fixed. - For stackable discounts, the **Stackability** dropdown menu option **Unspecified** was changed to **Undefined** in the **Campaign** search page filters. |

### Known Issues

This release has the following known issues.

* In Subscribe Merchant Portal 2.0, the **Merchant User** Report may show incorrect status for merchant users that use identity providers to login to the Portal.
  * Merchants using Vindicia IDP, can view user status in the Vindicia IDP Care Console.
  * Merchants using external Identity providers, such as OKTA or MS Azure, can check user status in their respective IDP Portals.


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