# 2025.4

{% hint style="danger" %}
**DISCLAIMER**

*Product Information contained within this document, including technical information and functional specifications, is subject to change without notice. Naviga reserves the right to make any changes to the information in this document at any time without notice. Naviga makes no warranty, representation, or guarantee regarding the suitability of its products and services for any particular purpose.*
{% endhint %}

## Release Prerequisites <a href="#release-prerequisites" id="release-prerequisites"></a>

| Integrations                              | Minimum Version                            |
| ----------------------------------------- | ------------------------------------------ |
| ENGAGE                                    | 2025.2.0                                   |
| NCS Circ                                  | <p>2025-2.2 (if PayPal Payway is required) |
| <br>2025-2.0 Otherwise</p>                |                                            |
| Subscribe Extracts                        | <p>Australian Clients - Extract Version 6  |
| <br>Other Clients - Extract Version 5</p> |                                            |
| Sync Jobs                                 | 2025.4.0                                   |
| Circ Pro                                  | 2025-1.1                                   |
| DSI (Saxo Circ)                           | Supported                                  |
| Naviga Pay (if using)                     | 2.2                                        |

### Recommended Engage Version

2025.4.0

## 🔑Key Features

### 1. **🏦**Bank Account Payments for Circpro

Subscribe now supports **Bank Account payments** for CircPro clients in the following payment flows:

* Newstart via Subscription Panel - Real-time
* Restart via Subscription Panel - Queue
* One-time payments, Autopay payment, and Update payment via Self Service - Queue

<div align="center"><figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2FH1iQk5hdRRFprm1CcPkW%2FBank%20Account%20payment%20method%20for-%20CircPro%20in%20SP.png?alt=media&#x26;token=3dfc484f-da5d-49b3-a773-96a4b1304c3b" alt="" width="375"><figcaption><p>Bank Account payment option for CircPro in Subscription Panel</p></figcaption></figure></div>

<figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2F9qVzV2AC6nf6vT4BzgSb%2FBank%20Account%20payment%20method%20in%20SS.png?alt=media&#x26;token=108336d9-e20f-414e-98c3-75ea78bb8108" alt=""><figcaption><p>Bank Account payment option for CircPro in Self Service</p></figcaption></figure>

{% hint style="info" %}
The payment type EFT must be configured with the name *EFT\_payment\_type* in CircPro for successful electronic fund transfers (a form of bank payment).
{% endhint %}

### 2. **🏷️**Variable Pricing - CircPro <a href="#id-1.-variable-pricing-circpro" id="id-1.-variable-pricing-circpro"></a>

The Variable Pricing feature has been implemented in the following payment flows for CircPro clients:

* Newstart via Subscription Panel (SP)
* Restart via Subscription Panel
* One-time payment and Autopay signup via Self Service (SS)

With this feature, when the end user selects a payment method involving a credit card, a credit card processing fee (surcharge) will be applied. Unlike processing fees, this surcharge will not appear as a separate line item; instead, it will be included in the total amount displayed to the user. That means, the surcharge amount is added to the subscription rate (base amount), and the combined total is displayed as the subscription cost to the user. For payments made via Bank Account, users will see a lower total amount for the same offer, as this method excludes the surcharge.

Variable Pricing for CircPro is enabled through the MG2 Control setting: **CircPro.VariablePricing**.

#### 1.1 Variable Pricing for Newstarts & Restarts via SP <a href="#id-1.1-variable-pricing-for-newstarts-via-sp" id="id-1.1-variable-pricing-for-newstarts-via-sp"></a>

For CircPro clients, Variable Pricing feature is now available only for **Realtime Newstarts,** not for Queue Newstarts. Variable Pricing is also available for **Queue Restarts** via SP. CircPro sends the surcharge amount (processing fee) along with rates, which Subscribe consumes to make Variable Pricing available for Realtime Newstarts and Queue Restarts via SP. In the Queue Restart flow, Subscribe performs only the authorization, while fund capture is handled by CircPro.

When Variable Pricing is enabled, the workflow is as follows:

1. The user selects the offer and enters the address details, including the ZIP code.
2. The user selects the payment method and provides the corresponding payment details. For CircPro, the currently available payment methods are:

   * **Credit Card (Including Apple Pay/Google Pay)**
   * **Bank Account**

   The subscription amount varies depending on the selected payment method and is displayed to the user as follows:

   * **Credit Card/Google Pay/Apple Pay** → Rate amount + Credit card processing fee + Tax (if enabled and applicable)
   * **Bank Account** → Rate amount + Tax (if enabled and applicable)
3. The user submits the payment. After authorization and fund capture, the **Order Summary** and the final **Congratulatory** pages are displayed.

<div align="left"><figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2Fxe7sB6vR4HnOsqakdknq%2FVP%20-%20CC.jpg?alt=media&#x26;token=7f3a3cec-a32a-42fd-a964-d4afdfbddcff" alt="" width="159"><figcaption><p>Total cost - Credit Card</p></figcaption></figure> <figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2FHeKs6FFXqIgQuAScKBGT%2FVP%20-%20Bank%20account.jpg?alt=media&#x26;token=0ab449c1-c9df-4e80-ba9c-b7598835c8da" alt="" width="164"><figcaption><p>Total Cost - Bank Account</p></figcaption></figure> <figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2FovXXQVSje14rub6Wv6Qi%2FVP%20-%20GPay.jpg?alt=media&#x26;token=d46de519-e677-49b9-b9e5-4c3bf5521627" alt="" width="154"><figcaption><p>Total Cost - GPay</p></figcaption></figure></div>

#### 1.3 Variable Pricing for One-time payment and EZPay Signup via SS

The Variable Pricing feature is available for **One-time payments** and **EZPay Sign-ups** (both are Queue processes) via the Self-Service portal for CircPro clients.

When Variable Pricing is enabled:

* Two different rates for the same offer are displayed on the Payment page:
  * A higher rate for **Credit Card** payments
  * A lower rate for **ACH** payments
* The user can choose their preferred payment method.
* **Tip** and/or **Donation** amounts can also be added along with these One-time or EZPay signup payments, as before.

The rate terms are fetched from CircPro, the subscription cost is calculated accordingly, and payment information is then submitted back to CircPro. The payment details include:

* Rates **with surcharge** → for Credit Card payments
* Rates **without surcharge** → for ACH payments (Bank Account)

<figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2FnYYXkB3f2jO8qfMnpLvv%2FSS%20Payment%20page.png?alt=media&#x26;token=8814718a-948d-4eaa-b07a-4229d4ce3027" alt=""><figcaption><p>Different rates for payment with Credit Card vs. Bank Account (<em>Amount</em> column shows CC rate, <em>ACHAmount</em> column shows Bank Account rate)</p></figcaption></figure>

**Configuration Notes**:

1. A new MG2 Control setting CircPro.VariablePricing has been introduced.
   1. CircPro.VariablePricing set to 1 - The Variable Pricing feature is enabled.
   2. CircPro.VariablePricing set to 0/Null - The Variable Pricing feature is disabled.
2. Set the MG2 Control settings Flow\.CircProIntegration = RealTime, Billing.CreditCard.ProcessingFee.Enable = 1
3. Enable the CMS property 'CashDiscounting.Enable' under the PaymentMethod V3 component
4. Disable the MG2 Control setting Billing.CreditCard.ProcessingFee.Enable
5. To setup taxes (if required):
   1. Set the MG2 Control Setting AllowTaxes to “1”
   2. Set the MG2 Control Setting Tax Engine as "FastTax"
   3. Validate the setup in NewspaperEventProcessorAssignments for GETTAX event pointing to the FastTax
6. Event GETRATECODEDETAIL should be enabled in NewspaperEventProcessorAssignments.

{% hint style="info" %}
**Note**:

* Enabling Variable Pricing along with ‘Queue’ Newstarts is an invalid configuration.
* If Variable Pricing is enabled on the CircPro side, it is mandatory to set the MG2 control setting *CircPro.VariablePricing* to 1 and enable the CMS property *CashDiscounting.Enable*. Without these two configurations, the Variable Pricing feature will not function correctly. The AddSubscription call will fail with the error message: "Please add the Variable Price."
  {% endhint %}

### 3. **💳**GooglePay/ApplePay/PayPal Payway via NavigaPay

Subscribe supports the following payment methods in Newstart payment flows (SP) via **Payway NavigaPay**.

For NCS Clients:

* **Apple Pay**
* **Google Pay**
* **PayPal**

For CircPro clients:

* **Apple Pay**
* **Google Pay**

This enhancement enables clients to leverage the **NavigaPay Dashboard** to analyze and utilize the payment information captured for each transaction.

All existing configurations supported in the direct integration of Google Pay, Apple Pay, and PayPal Payway (without the NavigaPay middle layer) are also supported in the Payway integration. The above-mentioned payment methods are supported by the API when the selected payment vendor is NavigaPay Payway.

<div align="left"><figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2F4PDYlWw1l5XaGCXbjeui%2FPayment%20methods%20in%20SP.png?alt=media&#x26;token=43856af0-6282-4f25-8041-6dbd9da72d7b" alt="" width="375"><figcaption><p>Payment methods for CircPro clients</p></figcaption></figure> <figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2F3eTjpjAnETZvJn7NrqTS%2FPayment%20methods%20-%20NCS.png?alt=media&#x26;token=afb10a73-38a0-425b-96be-197c02ccfb1a" alt="" width="375"><figcaption><p>Payment methods for NCS clients</p></figcaption></figure></div>

{% hint style="info" %}
**Note**: When payments are processed through Google Pay, Apple Pay, or PayPal Payway via NavigaPay:

* The **payment method** is saved as **Credit Card**.
* The **payment method type** is saved as **Google Pay, Apple Pay, or PayPal**, as applicable, in the database.
* Three new parameters — authorizationCode, transactionId, and paymentSource — have been added to the immediatePaymentWithPromocodeTipNie endpoint of the CircPro MicroAPI for Restart flows. By default, these fields are empty. For GooglePay / Apple Pay Restart payments, these fields will be populated, and the paymentSource will be passed from the Purchase API to the CircPro MicroAPI.
  {% endhint %}

#### 3.1 ApplePay Payway via NavigaPay

ApplePay Payway via NavigaPay supports the following flows in Newstarts:

* Full-page display with a Submit button at the end, where reauthorization is required
* Selecting a new offer through the Abandonment Popover with EZPay
* MPAN/DPAN (with or without EZPay) - supported for NCS
* ApplePay Billing Agreement for promotional offers (with/without Ezpay)\
  There will be no dependency on Ezpay CMS component

**Configuration Notes**:

1. The CMS component “*NavigaPay ApplePay Payway V3*” must be configured with the required properties and should be included in the Presentation.\
   Select an appropriate presentation -> Page V3 > Step V3 > Payment Methods V3 > NavigaPay ApplePay Payway V3 component.
2.

````
```
````

````
config.NavigaPayApplePayPayway = {
	Constants: {
		PaymentDescription: "Payment for news subscription",
		BillingAgreement: "You are purchasing a news subscription"
	},
	CSS: {
		defaultFileName: 'applePayDefault.css',
		simpleFileName: 'applePaySimple.css',
		seamlessFileName: 'applePaySeamless.css',
		commonCSS: 'applePaySimple.css'
	}
}
```

**Note**: CommonCSS is applied to all themes such as Minimal, Sleek, etc., except for Seamless, Simple, and Default.
````

#### 3.2 GooglePay Payway via NavigaPay <a href="#id-2.1-googlepay-payway-via-navigapay" id="id-2.1-googlepay-payway-via-navigapay"></a>

A new component named “*NavigaPay GooglePay Payway V3*” has been introduced in CMS with the following properties:

1. Errors.ReAuthorize
2. Image
3. LearnMore.Show
4. LearnMore.Text
5. LearnMore.Url
6. Title

<figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2F8se8zKIXdlgKYejLF9nP%2FGooglePay%20Navigapay.png?alt=media&#x26;token=5c73200c-f503-4103-8e2b-f01412c2ef82" alt="" width="375"><figcaption><p>NavigaPay GooglePay Payway V3 Component and its Properties</p></figcaption></figure>

**Configuration Notes:**

1. The new CMS component “*NavigaPay GooglePay Payway V3*” must be configured with the required properties and should be included in the Presentation.
2. Select an appropriate presentation -> Page V3 > Step V3 > Payment Methods V3 > NavigaPay GooglePay Payway V3 component.

#### 3.3 PayPal Payway via NavigaPay <a href="#id-2.2-paypal-payway-via-navigapay" id="id-2.2-paypal-payway-via-navigapay"></a>

A new component named “*NavigaPay Paypal Payway V3*” has been introduced in CMS with the following properties:

1. Alt
2. Description
3. Disclaimer
4. Image
5. LearnMore.Show
6. LearnMore.Text
7. LearnMore.Url
8. Messages.ReAuthorize
9. Style.Color
10. Style.Label
11. Style.Shape
12. Title

<figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2Fscc67F37dqfSflzgiseU%2FPaypal%20payway%20navigapay.png?alt=media&#x26;token=36669538-a4a9-4cbe-b25d-946a9e6e2670" alt=""><figcaption><p>NavigaPay Paypal Payway V3 Component and its Properties</p></figcaption></figure>

{% hint style="info" %}
**Note**: With this update, NavigaPay Payway is now integrated with all payment products in Subscribe, except for LTE.
{% endhint %}

**Configuration Notes**:

1. The new CMS component “*NavigaPay Paypal Payway V3*” must be configured with the required properties and should be included in the Presentation.
2. Select an appropriate presentation -> Page V3 > Step V3 > Payment Methods V3 > NavigaPay PayPal Payway V3 component.

**Minimum Circ Version**: NCS 2025-2.2

## 🌐General Enhancements <a href="#general-enhancements" id="general-enhancements"></a>

### API <a href="#api" id="api"></a>

#### 1. Removing validation of Last4 Credit Card Digits <a href="#id-2.-removing-validation-of-last4-credit-card-digits" id="id-2.-removing-validation-of-last4-credit-card-digits"></a>

The validation of the last four digits of the credit card has been removed for already authenticated users logging into Self Service.

With this change:

* After entering the correct username and password, an authenticated user can log in to My Account regardless of the credit card format.
* The credit card value is displayed in the UI (where applicable) exactly as it is received in Self Service.
* If the value contains special characters or is not present, a **NULL** value will be displayed.
* Authenticated users are no longer restricted from logging in due to credit card format validation.

#### 2. Restart Date in Alert Emails to Subscribers&#x20;

Subscribe now captures the *Restart Date* returned by NCS for permanently stopped subscriptions and stores it in the **Subscription** table of the Subscribe database as **LastStartDate** against the restarting subscription.

The restart date parameter is also available as an email attribute `{{subscription.LastStartDate}}`, which can be added to email templates. For example, this attribute can be included in the info mail sent to subscribers who restart their previously permanently stopped subscriptions.

<figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2FG8xGBcskAV9JHGksqnlK%2FEmail%20with%20attribute.png?alt=media&#x26;token=90eb8fcd-2940-4983-9443-00ef1895970c" alt=""><figcaption></figcaption></figure>

#### 3. Account Holder Name in Bank Payments request & Passing it to NCS <a href="#id-4.-account-holder-name-in-bank-payments-request-and-passing-it-to-ncs" id="id-4.-account-holder-name-in-bank-payments-request-and-passing-it-to-ncs"></a>

A new parameter `BankAccountHolderName` has been added to APIs, allowing consumer applications to include the account holder name in their bank payment requests. The value of this parameter is stored in the Payment Method table along with other payment details in the database.

Currently, this parameter is used only in the Billing Change API, which passes billing change information to NCS. Other NCS APIs do not yet support this parameter.

### CMS & Subscription Panel <a href="#subscription-panel" id="subscription-panel"></a>

#### 1. New property "AccountHolder" in Components

A new property "AccountHolder" has been added to PlaceOrder and Confirmation V3 components in CMS. PaymentInformation.BankAccount.AccountHolder is the property name. The parameter is configurable through subcon config, and it will be non-mandatory on UI.

<div align="left"><figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2FUqUV4apndly1J5v3Js3Q%2FConfirmation%20V3.png?alt=media&#x26;token=38fb06e9-f93e-49d8-8a91-74d83bf49917" alt="" width="375"><figcaption><p>AccountHolder Property in Confirmation V3</p></figcaption></figure> <figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2F8o7vGvUmDIuU7KjpJpNP%2FPlace%20order%20v3.png?alt=media&#x26;token=045efaea-3596-4659-bfcb-b59559f2e986" alt="" width="375"><figcaption><p>AccountHolder Property in Place Order V3</p></figcaption></figure></div>

<figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2FW73pkgSv4zljf2pCeN2X%2FBank%20Account%20v3.png?alt=media&#x26;token=1c601077-9919-48d5-a335-37cceff466c9" alt=""><figcaption><p>AccountHolder Property in Bank Account V3</p></figcaption></figure>

The account holder’s name can now be included in the Newstart Presentations for NCS if the payment method is Bank Account. The Order Summary page and the final Congratulatory page will display the Account holder name only if the corresponding label is set and the value is captured in the flow.

<figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2FciAKfc5Tb0BAGtAa4tqh%2FNew%20Account%20holder%20property.jpg?alt=media&#x26;token=19832d9e-0558-421b-bd9c-8e509050e516" alt=""><figcaption><p>The New Account Holder Name field in the Presentation</p></figcaption></figure>

\
**Configuration Notes**:

* Page V3 > Bank Payment component > Account holder property --> On/Off (this behavior exists, not part of this development)
* Page V3 component > Confirmation V3 > Payment Information > Bank Account > "AccountHolder" string value for label in confirmation component
* Page V3 component > Place Order V3 > Payment Information > Bank Account >"AccountHolder" string value for label in Place Order component

**Note**: The *AccountHolder* property must first be enabled in Bank Account V3 for it to function effectively in the Place Order and Confirmation components.&#x20;

### Self Service (SubCon Site)

#### 1. New 'Account Hoder Name' field in Bank payment pages <a href="#id-1.-new-field-for-bank-payment-pages" id="id-1.-new-field-for-bank-payment-pages"></a>

When the payment method is Bank account, a new mandatory field ‘Account Holder Name’ has been introduced on all Bank Payment screens, across all transactions, regardless of whether this information is sent to NCS or not.

<figure><img src="https://976659993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHtWY24ZsNeJjetCpNF%2Fuploads%2Fu5k6KLlKKenJ3z2ZY4CA%2FAccount%20holder%20name%20in%20SS.png?alt=media&#x26;token=0e58f123-f8f5-4f3f-be95-c17148c43695" alt=""><figcaption><p>Bank Account Holder name field in the SS Payment page</p></figcaption></figure>

* Autopay Signup
* Autopay Manage
* Subscription Update
* One-time Payment
* Add Tip
* Subscription Restart

**Configuration Notes**:

The new CMS content property "BankAccount.BankAccountHolderNameLabelText" is added for the BankAccountHolderName label text in all pages where the new field is added.

### Database <a href="#database" id="database"></a>

#### 1. Increasing the size of the Database Column <a href="#id-1.-increasing-the-size-of-the-database-column" id="id-1.-increasing-the-size-of-the-database-column"></a>

The size of the email ID column has been increased so that the users are now able to successfully link the accounts even when the email Id is as lengthy as 100 characters.

## 🛠️ Bug Fixes <a href="#bug-fixes" id="bug-fixes"></a>

#### 1. Tip amount not captured in the EZPay signup flow <a href="#id-1.-tip-amount-not-captured-in-the-ezpay-signup-flow" id="id-1.-tip-amount-not-captured-in-the-ezpay-signup-flow"></a>

The tip amount was not being captured in CircPro during Autopay signup flow with both Tip and Donation. This issue has been resolved.

#### 2. Update payment transactions zeroing out Recurring Tip amounts <a href="#id-2.-update-payment-transactions-zeroing-out-recurring-tip-amounts" id="id-2.-update-payment-transactions-zeroing-out-recurring-tip-amounts"></a>

While placing an update payment method via Self Service on an account that already has a recurring Tip setup, the recurring tip was getting removed for NCS clients. This issue has been resolved. After the fix, while updating the payment method, the already configured recurring tip is not being removed.

#### 3. Issue while signing up to EZPay during upgrading/downgrading susbscription

While signing up to EZPay during upgrading/downgrading a subscription using a Visa card, an error message was received saying, “Credit card type does not match expected credit card type, Visa”. This issue has been resolved. After the fix, the user is able to sign up for EZPay while upgrading/downgrading a subscription using a Visa card without encountering any errors.

#### 4. Issue in the Newstart and Restart flow for CircPro <a href="#id-4.-issue-in-the-newstart-and-restart-flow-for-circpro" id="id-4.-issue-in-the-newstart-and-restart-flow-for-circpro"></a>

During Real time Newstart or Restart flow of CircPro, when the subscription was created with EZPay, the EZPay was turned off after the nightly sync. This issue has been resolved. After the fix, Newstarts or Restarts on EZPay is not turned off after the sync process for CircPro clients.

#### 5. Phone number not captured in Newstarts from SP for CircPro

The Phone number was not getting captured in Circpro after creating a Newstart from SP. This issue has been resolved. After the fix, when a Newstart is initiated and submitted from SP, the Phone number in the user details is correctly captured at the CircPro end.

#### 6. Incorrect cardholder name getting captured in Newstarts for CircPro  <a href="#id-6.-incorrect-card-holder-name-getting-captured-in-newstarts-for-circpro" id="id-6.-incorrect-card-holder-name-getting-captured-in-newstarts-for-circpro"></a>

During Newstarts from SP with ApplePay/GooglePay payment, it was observed that the incorrect cardholder's name (the name entered in the payment iFrame during the newstart purchase flow) was getting captured in the payment-related table. If the name of the user and the cardholder's name were different, instead of the cardholder's name, the user's name in the address details was getting captured. This issue has been resolved. After the fix, during newstarts via SP for CircPro clients, even when the user name and the cardholder name are different, the correct cardholder name is getting captured in the payment-related table.

#### 7. Issues in the Restarts/Newstarts for CircPro clients <a href="#id-7.-issues-in-the-restarts-newstarts-for-circpro-clients" id="id-7.-issues-in-the-restarts-newstarts-for-circpro-clients"></a>

It was observed that when a Restart was initiated from SP for CircPro clients, the subscription was being restarted at a previous rate, which was not expected.

These issues have been resolved, and the Restart flow is now working as expected for CircPro clients.

#### 8. Newsletter Subscription Issue <a href="#id-8.-user-orchestrator-mg2-auth-newsletter-subscription-issue" id="id-8.-user-orchestrator-mg2-auth-newsletter-subscription-issue"></a>

When a user registers on a site, they are automatically subscribed to the newsletter. However, after a client upgrade, it was observed that registered users were not being automatically subscribed. Instead, they had to manually subscribe by logging into their profiles.

This issue has now been resolved. After the fix, users registering on news sites are automatically subscribed to newsletters as expected.

**Note**: *This is applicable only for clients using MG2 authentication.*

#### 9. Issue in ZipOnly Realtime Newstart <a href="#id-9.-addaddressoccupant-failure-and-incorrect-addresstypeid-in-ziponly-realtime-newstart" id="id-9.-addaddressoccupant-failure-and-incorrect-addresstypeid-in-ziponly-realtime-newstart"></a>

The *ADDADDRESSOCCUPANT* event was failing during Realtime Newstart of ZipOnly subscriptions for CircPro clients, resulting in an *“Invalid Input”* message in the returned HTML. This issue has been fixed. After the fix, the *ADDADDRESSOCCUPANT* event processes successfully for ZipOnly Realtime Newstart, and the correct *AddressTypeId* is passed.

#### 10. Issues in ApplePay, GooglePay, or PayPal payments via Braintree for NCS <a href="#id-10.-issues-in-applepay-googlepay-or-paypal-payments-via-braintree-for-ncs" id="id-10.-issues-in-applepay-googlepay-or-paypal-payments-via-braintree-for-ncs"></a>

New start payments were failing for end users of NCS clients when using ApplePay, GooglePay, or PayPal via Braintree. This issue has now been resolved. After the fix, new start payments are successfully processed when end users pay through ApplePay, GooglePay, or PayPal via Braintree.

### Self Service

#### Alignment issues on the Benefits section <a href="#id-1.-alignment-issues-on-the-benefits-section" id="id-1.-alignment-issues-on-the-benefits-section"></a>

The Self-Service Benefits section was displayed misaligned to the logged-in users. This issue has been resolved. After the fix, Benefits section boxes and buttons are aligned on the page as expected.

### SolCon

#### Error message while filtering the Offer <a href="#id-1.-error-message-while-filtering-the-offer" id="id-1.-error-message-while-filtering-the-offer"></a>

Previously, while filtering offers by OfferGroupId in SolCon, an “Index was out of range” error message was displayed. This issue has now been resolved, and users can now filter offers by OfferGroupId on the Offers page without encountering any errors.\ <br>
