2025.4.x

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.

.1

Restart Subscription from Subscribe considered as a New Start for NCS clients

It was observed that, in some cases, Restart subscriptions were treated as New Start subscriptions and vice versa on the NCS side for NCS clients. This issue has now been resolved.

After the fix, if there is any discrepancy between Subscribe and NCS regarding the subscription status, Subscribe will always follow the subscription status of NCS.

• For example, if a New Start created in Subscribe is treated as a Restart by NCS, a new event CHANGETORESTART will be triggered, and no new subscription record will be created in Subscribe.

• Similarly, if a Restart from Subscribe is treated as a New Start by NCS, the CHANGETONEWSTART event will be triggered, and Subscribe will create the appropriate subscription entry in the system.

Most importantly, subscribers will now receive real-time entitlements for the subscriptions regardless of whether NCS classifies the purchase as a Restart or a New Start.

This fix is also merged into the releases 2025.5.1 & 2026.1.

Error message on creating Realtime New start for CircPro

CircPro users encountered an Object reference error while creating a Realtime New Start using the Bank Account payment method. This issue was specifically observed when No EZPay was selected for the new start offer in SolCon.

This issue has now been resolved. After the fix, CircPro users can successfully create Realtime New Starts using Bank Account payments.

This fix is also merged into the releases 3.17.1.4, 2025.3.1, 2025.4.1 & 2025.5.

Incorrect pacTerm sent in the Restart flow

While restarting a subscription via SP, the PAC term (Periodic Automatic Charge) sent to CircPro was incorrectly taken from the stopped subscription instead of the PAC term associated with the selected restart offer. This issue has now been resolved. After the fix, the PAC term of the new subscription is correctly sent to CircPro for further processing.

This fix is also merged into the release 2025.5.1.

Application Covered:

API