2025.2

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.

Release Prerequisites

Integrations	Minimum Version
ENGAGE	2025.2.0
NCS Circ	2025-2.0
Subscribe Extracts	Australian Clients - Extract Version 6 Other Clients - Extract Version 5
Sync Jobs	2025.2.0
Circ Pro	2023-2.0
DSI (Saxo Circ)	Supported
Naviga Pay (if using)	2.2

Key Features

1. Real-time Entitlements for NCS New Start Subscriptions

With this enhancement, New Start subscriptions from NCS are now captured in real-time by the Subscribe application. This means subscribers receive immediate temporary entitlements and can access digital content without waiting for the nightly sync.

For more details on this feature, refer to this link: Real-time Entitlements

2. Upgrade/Downgrade Billing Changes

It is now possible to submit an Upgrade/Downgrade offer request or a StopSaver request through Self Service along with EZPay options. When such a request is submitted, the NCS API now accepts Billing Changes (new rate term or length) and EZPay status.

The three EZPay configurations — EZPay Required, EZPay Optional, and No EZPay are driven directly from the Offer configuration in SolCon. If there is a change in the EZPay status between the current and new offers, the user must consent to the change via a checkbox. Users can upgrade or downgrade any non-stopped subscription, regardless of whether it is currently on EZPay. Whereas in Stopsaver flow, users can only downgrade any non-stopped subscription, regardless of whether the subscription is currently on EZPay.

Note: As before, no payment is required during upgrade/downgrade or StopSaver flows. If a user is not on auto pay and opts for an offer with EZPay enabled, payment details will be collected for future auto-renewals - no payment will be captured during the transactions. If the user selects Bank account or Credit card as the payment method, the corresponding iFrame will be loaded on the payment page.

There is no change in how Upgrade/Downgrade offers are set up in SolCon. Clients are expected to configure Smart Offers only for Standard subscriptions.

API amendments to support the new Upgrade/Downgrade flow enhancement

In the enhanced Upgrade/Downgrade flow, an additional NCS Billing Change API is invoked in the upgrade/downgrade API call. This submits billing changes - such as rate term, rate length, & EZPay status - to NCS Circ. The entire orchestration is handled at the Subscribe micro-API level.

• Additional fields introduced in the Upgrade/Downgrade request are as follows:

  • IsEZPay (boolean)

  • IsEZPayOptional (boolean)

  • ProcessBillingChange (boolean)

  • Billing (object containing billing change details) Note: The new object —Billing with parameters SubscriptionId, RateCode, Term, Length, and PaymentMethodId—will be required in the input payload of the Subscription/{ID}/upgrade and Subscription/{ID}/downgrade API calls only when the value of the flag ProcessBillingChange = ‘true’.

The enhanced workflow:

1. The process begins with the calling of either the FULLDOWNGRADESUBSCRIPTION or the FULLUPGRADESUBSCRIPTION event.

2. Upon successful execution, this event returns a transactionId.

3. Based on the value of the ProcessBillingChange flag from the SubCon Site:

   • If ProcessBillingChange = 'true':

     • The EZPAY event is triggered.

     • This internally invokes the Billing Change API of NCS to process the new rate term and rate code.

   • If ProcessBillingChange = 'false':

     • The EZPAY event is skipped.

     • Only the FULLDOWNGRADESUBSCRIPTION or FULLUPGRADESUBSCRIPTION event will be processed.

Configuration Notes:

Add the CMS content SubscriptionUpdateForm.EZPayOptionalLabelText in the subscriptionUpdate page and StopSaver page in SS so that the label for the optional EZPay checkbox displays correctly on the screen.

---

General Enhancements

Self Service

1. New cookie on Subscription Restart

A new cookie named subscriptionPurchased with the value 'true' will now be generated when a user successfully restarts a subscription via the Self-Service portal. This cookie has a 24-hour expiry.

Previously, even if the user was already logged in to the .com site, restarting a subscription required them to log out and log back in to receive the updated subscription entitlements. With this enhancement, users no longer need to log out and log in again. Refreshing the .com page or clicking an article link will apply the updated entitlements associated with the restarted subscription.

Subscription Panel

1. Twitter icon Replaced with X logo

The Twitter icon in the Subscription Panel has been updated to reflect the new X branding. If the Social Media component is configured in the CMS, the X logo will now be displayed instead of the old Twitter icon.

Implementation Note:

In CMS, configure the Confirmation V3 component --> Social Media component as a child component. Once the social media details are set in the CMS, the X icon will be displayed in the Subscription Panel for Twitter.

2. New cookie on Subscription Purchase

A new cookie named subscriptionPurchased with the value 'true' will now be generated when a subscription is successfully purchased via the Subscription Panel. This cookie has a 24-hour expiry.

Previously, even if users were already logged into the .com site, they did not receive immediate access to content after purchasing a new subscription. They had to log out and log back in to activate the new entitlements. With this enhancement, users no longer need to log out and log in again. Simply refreshing the .com page or clicking an article link will apply the updated entitlements associated with the new subscription.

API

1. SourceCode for EZPay event from MG2Control

The SourceCode value for EZPay event (event type Id:16) will now be derived from the MG2control key: DTI.SwitchToEzPay.SourceCode. The logic to support this has been implemented. If the key is not configured for the client, or is unavailable, then the SourceCode for EZPay event will default to the hardcoded value: “Internet”.

Configuration Notes:

MG2Control Setting - DTI.SwitchToEzPay.SourceCode

Value - Text

2. Total Price of Products in Offer API

A new parameter, TotalProductPrice (of decimal type), has been added to the Offer API. When an offer includes multiple products, this parameter returns the total price by summing the prices of all products associated with that offer. This was required for internal purposes and does not affect any existing functionality.

3. Implementing Cybersource Flex API v2

Subscribe has now implemented Cybersource Flex API v2 for payment transactions. This upgrade accommodates recent breaking changes introduced in the latest Cybersource API version. Necessary updates have also been made in the consumer applications to ensure seamless integration and compliance.

Following this update, there are no changes to the existing payment functionalities.

---

🛠️ Bug Fixes

Self Service

1. Error message while canceling the subscription

Users were encountering an error message — “Invalid Input Model” — when attempting to cancel a subscription which had an associated Smart Offer (Stop Saver). This issue has now been resolved.

After the fix, users can cancel subscriptions without any error messages, even if the subscription is linked to a Smart Offer.

2. User not directed to Home page

Previously when a logged-out user tried to hit a publication’s base URL (main myaccount URL), they were incorrectly shown the Auth0 login modal instead of being directed to the Self-Service home page. This issue has been resolved now.

After the fix, when a logged-out user visits the Publication’s base URL, they are correctly directed to Self Service home page. The Auth0 login modal now appears only when the user explicitly clicks the Login or Sign in button.

3. Error message in the StopSaver flow

An error message — “Object reference not set to an instance of an object” — was displayed during the StopSaver flow of a digital subscription (not on EZPay) that had an associated print smart offer. Despite the error message, the flow completed successfully and all events and transactions were generated as expected.

This issue has now been fixed.

---

Future Enhancements

Upcoming NavigaPay Integrations

Few additional properties/components are added in CMS that correspond to ApplePay, GooglePay & PayPal integrations via NavigaPay Payway.

The API development for these integration has been added to this release. However, these will be useful in upcoming releases when the end to end integration is completed.