> ## 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 2021.08 Release

Release Date: August 24, 2021

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

## Subscribe Features

### REST Infrastructure and Loggly Improvements

* All REST Subscription create and update calls now include pm\_type metadata. To search in Loggly for a Subscription that uses MAP Payment method, use the following search:

  `json.api_route:"Subscription::create"` and `json.metadata.pm_type:"MerchantAcceptedPayment"`

* REST API Requests now include metadata tags for the start and end of a request. In Loggly this can be searched for by `json.start_request:1` and `json.end_request:1`

* Request headers: Accept-Encoding, X-OneTimeLogin, X-OneTimeLoginHMAC. Logging of these has been moved to a subhash named headers: `json.headers.Accept-Encoding:"gzip"`.

(VIN-11386, 12268, 12350)

### Push 2.0 Framework

Push 2.0 is new service for Push Notifications that is transparent to customers and provides the same functionality as Push 1.0 but is based on modern infrastructure.

It is being released gradually to merchants. Contact Customer Engagement team before enabling Push 2.0 for a merchant.

To move a merchant to Push 2.0, add the following name/value pair to the Merchant configuration:`push_2_enabled` set to 1.

Merchants must add the Push 2.0 IP's to their network allowlist. See the [2021.08 Release Notes](https://docs.vindicia.com/bundle/Subscribe_Release_Notes/page/2021.08_tp_subscribeReleaseNotes.html).

Merchant configuration for Push Notifications are currently not automatically synchronized from Subscribe to Push 2.0. A manual process is required to add or update Push Notification changes to Merchant configurations done in the Subscribe Portal to Push 2.0. It is expected that this will be automated in the very near future. Until then, engage CloudOPS to manually update Push 2.0 configuration when any Merchant Configuration changes are made in Subscribe.

## Payment Features

### Paysafe Integration Enhancement Supporting BIN Storage and Retrieval

From this release, PaySafe payment processor integration will support the storage and retrieval of BINs (bank identifiers) from the payment method token as required for Retain functionality. This will be performed through the **Payments Microservice that is not yet available**.

PaySafe merchants typically store the credit card only and do not hold the BIN number. BINs are required for Retain forced deposit (L3/L4), which needs to be validated against the BIN's blocklist. Using the Payments Microservice (not yet available in production), 2 API calls are used to get the BIN.

1. **get-profile-using-merchant-customer-id**: Use the merchant-customer ID as an input and get the Profile\_Id in response.
2. **get-profile-including-subcomponents**: Use profile\_id as an input and get BIN and PaymentToken from response.

If the PaymentToken received through these calls matches the PaymentToken in the BillTransaction API, the BIN is stored for use with failed transactions.

### PaySafe: Card On File Support

Vindicia is providing CIT/MIT parameters support for PaySafe through Payments Microservice from this release. At this time,**the Payments Micro-service is not yet available** in production so the support is only communicated internally.

(VIN-10304)

### Elavon Integration Enhancement Supporting Custom Data

From this release, Elavon payment processor integration supports Name-Value pairs that hold customized merchant-specific data.

Elavon setup used by Lee automatically updates the Customer record when Transactions become Captured in Elavon, which is before the final status is returned by Retain in fetchBillingResults. Each time a Transaction is submitted to Elavon, a new value is generated in their billing system for **lee\_submit\_id** and sent to Elavon, which is then used by the Lee system to track back the customer record for the scheduled Transaction and to update the final status as paid after the Transaction is Captured in Elavon.

The Retain integration will pass all 3 Name/Value Pairs, so the Elavon integration is just updated to pass these Name/Value Pairs to Elavon without needing to look at the merchantTransactionId for the FailedTransaction submitted or the divisionNumber.

Transaction Name Value Pairs:

* lee\_bizdb\_id

* lee\_submit\_id **(critical)**

* lee\_terminal\_id **(critical)**

**Note:** Additional NVP can be created by Lee (in the Elavon Portal) and passed to Subscribe in the same way.

(VIN-12011)

## Internal Fixes

| Ticket | Description |
| - | - |
| VIN-10805 | Pause subscription did not send relevant Push Notification. Functionality was tested in Push 2.0 and not observed. |
| VIN-11097 | Resume Subscription send relevant relevant Push Notification. Functionality was tested in Push 2.0 and not observed. |
| VIN-12516 | Stop and Start entitlement Push notification order issue was tested in Push 2.0 and not observed. |
| VIN-11958 | Paymentech Transaction communication errors cause capture delay. Issue was verified with the Chase Paymentech team and a response files was resent. Capture delay was due to the missing response file. The issue has been fixed. |
| VIN-12107, PORT-1923 | Improved Vindicia Admins ability to log in to Portal 2.0 and move between merchants with consistent permissions and results. |
| VIN-12550 | Reports schedulerd has been hardened against an exception being thrown during a running task. schedulerd will now do task cleanup and will still attempt to schedule the next execution of the task if it is repeated. |

## Internal Known Issues

No Internal known issues in this release.


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