> ## 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.11 Release Release Date: November 30, 2021 **Parent topic:**[Vindicia Subscribe - 2021.11 Release Notes](2021.11_tp_subscribeReleaseNotes) ## Subscribe Features ### External User Authentication- Internal Fixes and Prep for Connect (ULM) IDP connection In this release, changes were made to the Subscribe - internal object. It was renamed OIDC instead of Okta to enable its re-use for OIDC standard IDPs. This means that when configuring an SSO connection, instead of using the \{"idp\_type": "Okta"}, use the \{"idp\_type": "OIDC"}. This is a one-time change updated on Staging and Production . Additionally, we are modifying key handling when connecting to an IDP, to allow us to communicate with multiple IDPs that support the OiDC standard. The SSO configuration tool has been updated simplify the configuration process. It now will allow the following: * Use the known URL- Build the IDP configuration by specifying the well known configuration URL for the specific IDP * Single run configuration - Specify both the IDP Client ID and Client Secret on the same command line, it will automatically build the secret JSON * Removed client ID from the Secret store so it only has to be specified in one place * Resolved erroneous error message that was displayed when activating a merchant SSO (VIN-12591, 13315, 12430) ### FiServ File Data Gateway Integration FiServ MessageWay file system is being decommissioned. Subscribe has been integrated into FiServ File Data Gateway for all of FDMS batch traffic. This is an internal operational endpoint change for connecting to FiServ for FirstData FDMS Compass. Feature was released as part of RFC-297 (VIN-7448) ## Payment Features ### External Billing Parallel Processing External Billing batch creation is now performed via parallel processing, which should improve billing performance.The number of processes can be configured via **\$VIN\_ExternalBilling\_BRD\_Procs**. Sub\_batch size is 100 transactions. For more details, [Dev-to-Ops wiki](https://wiki.sm.vindicia.com:8443/x/jILlB)page. (VIN-13508) ### ECP Multi Thread Processing ECP update of Transaction status is now performed via parallel processing, which should improve Transaction finalization. Control of the number of processes is via **\$VIN\_ECP\_Timeout\_Procs**. For more details, [Dev-to-Ops wiki](https://wiki.sm.vindicia.com:8443/x/jILlB) page. (VIN-13510) ### Payments Service Release In this release, a new internal architecture for payment processor integration has been enabled, **Payments Service**. This architecture enables quicker payment processor integration by de-coupling Payment Provider logic from Subscribe logic. Payments Service implements a distributed system which interfaces Subscribe to AWS based services. The AWS services interface with a microservice unique to each Payment Provider, which then interfaces to the Payment Provider using their bespoke API. The Payments service is deployed to Subscribe Staging and Production in "dark mode" and requires specific configuration to enable. With this new architecture in place, payment processor integration will consist of an encapsulated microservice that can be developed without requiring in-depth knowledge of an deployed independently with minimal dependencies on the Subscribe platform. As part of this architecture, Subscribe exposes a Unified Payments Request that is then consumed by the specific payment processor microservice which returns a common Payments Response. See the following flow: Payment service Flow The Payments service supports credit card payment method only. The following payment operations are currently supported by the Payments service:​ * Health Check * Partial Auth * Realtime Auth * Realtime Void * Realtime Validate * Force Capture * Capture * Refund * Realtime Authenticate * Finalize Customer Authentication **Migration**: For Payment Provider integration that are implemented in both the legacy architecture and the new one, it will be possible to route Merchant transactions to either of the architecture implementations based on payment operation (auth, capture, void, force deposit, etc.). For example, Subscribe can route authorization operations for a Merchant to their Payment Provider through the Payments Service and the capture operations via the legacy Billing Interface. ​ (VIN-9503) ### Support for Paysafe The new platform is released by using the Payments service release. Only the credit card payment method is currently supported. (VIN-10304, VIN-1174) ### Worldpay 3DS Enhancement In this release, a new Worldpay 3DS (PSD2) authentication option has been added. This option allows customers to choose whether to use 3DS verification through Cardinal Commerce or through Worldpay. The Authentication Provider is determined by VIN\_SCA\_provider, which for Cardinal is 2002. All values for `Cardinal:` names are provided to Vindicia by Cardinal when the merchant is configured. Vindicia is responsible for getting the merchant configured in Cardinal. | Name | Value | | - | - | | VIN\_SCA\_provider | 2002 | | Cardinal:API\_Key | | | Cardinal:ProcessorId | | | Cardinal:MerchantId | | | Cardinal:TransactionPwd | | | Cardinal:ApiIdentifier | | | Cardinal:OrgUnitId | | | (VIN-12761) | | ## Internal Fixes | Ticket | Description | | - | - | | VIN-12661 | Merchant configuration Push Notification does not display selected push event classes. Issue has been resolved. | ## 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.