> ## 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 2022.01 Release Release Date: January 25, 2021 **Parent topic:**[Vindicia Subscribe - 2022.01 Release Notes](2022.01_tp_subscribeReleaseNotes) ## Subscribe Features ### Subscribe Portal 2.0 - Admin Access for Reports From this release, Admins can access Subscribe Merchant Portal 2.0, select the relevant merchant and access the merchant's reports. (VIN-13179) ### Subscribe Portal 2.0 - Transaction Query Response Times In this release, query response times improvements were made for Transaction searches by date range. (VIN-13050) ### External Billing: Configuration via Portal 1 and Logging Enhancements From this release, the following enhancements are supported for External Billing: * In this release, logging enhancements were made for External Billing and the following error messages were added to loggly. * **sftp\_connect failed for merchant\_id: \$merchant\_id**: This error indicates that the sftp\_connect has failed forthe merchant. There should be prior error messages from the sftp\_connect to indicate the issue. * **No prior timestamp to compare to - reading all files for merchant\_id: \$merchant\_id**: This error usually indicates a missing timestamp. If this is the first time that the merchant is processing transactions, then the error is expected. * **Problem parsing timestamp out of error file $filename for merchant\_id: $merchant\_id**: This error is used to recognize an empty filename problem. * **failed to parse a dtg from $filename for merchant\_id: $merchant\_id**: This error indicates that the filename fails to conform to the expected form, so no time stamp can be resolved. The function will return an undefined response and prevents an empty value from being passed. * **Could not create datetime object from presumed iso8601 date**: This error indicates an issue with the timestamp. It includes the name of the file, the merchant\_id, and the error that was observed. * **skipping $filename file is older than the most recent error file for merchant\_id: $merchant\_id**: This error indicates that the file referenced is older than the current oldest file. * **skipping $filename file has been already processed for merchant\_id: $merchant\_id**: This error indicates that the file referenced is listed as having already been processed. VIN 13525 * From this release, External Billing configuration is available in Subscribe Portal 1.0. * **For existing merchants**: the External Billing Configuration is displayed when the database's external billing configuration table is in use for the merchant and populated with entries. * **For new merchants**: an External Billing routing rule should be defined for the configuration table to appear VIN-13530 The following fields appear in External Billing Merchant Configuration: | Field | Description | Required and (default value) | | - | - | - | | Primary SFTP Server | The address of the SFTP site where charges and refund files will be located. It can be either an IP address or a domain | Yes (empty) | | Secondary SFTP Server | The alternative site for SFTP - in case the primary one is not accessible. The system will retry both addresses in alternation until we connect | No | | SFTP Primary Port | The merchant-provided port of the SFTP site. | Yes (default is 22) | | Login Name | The login name to use to connect to the SFTP server | Yes (empty) | | Login Password | The password for server access. | No (we require either password or validation file access) | | RSA File Location | The path to the location of the RSA validation fiIe. When identification is key-based, this file will be used. When identification is based on both password and validation file, this file will be used first. | No (depends whether password or validation file access is being used) | | Charge & Refund Files Directory | The directory in which charge and refund files will be placed. Must be a writable location for the SFTP user (login). | Yes | | Error Files Directory | The directory to check for error files. Must be a readable location for the SFTP user (login). | Yes | | Time allowed for errors to be received | Number of whole days to allow before capturing payment. Must be at least one day longer than the Billing System processing interval. **Best practice for daily processing**: 3 days After this time, errors received will not be processed. | Yes (default is 3) | | Immediate Activation of Subscriptions | If set to True, Subscriptions created with an ExternalBilling PaymentMethod will be immediately set to Active/Good Standing status and billing\_state, respectively.**Note:** Creation of Subscriptions with an ExternalBilling PaymentMethod **MUST** either not define the**validate\_for\_future\_payment policy** parameter or explicitly set it to `False`. If this is not implemented correctly, immediate activation defined in this field will NOT work. | No (default set to `False`) | ## Payment Features ### Payway Integration The new Payway integration must be enabled in the Portal 1.0 Merchant Configuration. Additionally, Payway is a microservice that requires the Payments Service. For details on configuring the microservice, see [the wiki Payments Service page](https://wiki.sm.vindicia.com:8443/x/1wdQB). (VIN-10305) ## Retain Features This release includes the following new Retain features: ### Enhancement for Adyen Processor - Support for merchantTransactionId From this release, Retain allows to set the original merchant transaction ID as the reference ID in Adyen instead of the final captured Vindicia transaction ID. In order to enable this, use the following NameValuePair custom data in Merchant Configuration: * Name: **Adyen:InitialSelecttransactionForReferenceCode** * Value: set to **1** (VIN-13177) ## Internal Fixes | Ticket | Description | | - | - | | VIN-13844 | External Billing Error files that have multiple incorrect VIDs were not being processed. This has been fixed. | | VIN-14426 | Fixes for the campaigns page in Portal 2.0 including:- Create new element name for campaign name was spelled incorrectly - The naming of the Campaigns breadcrumb element was corrected - Improvements to element Ids were made for test automation support. | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.