2025.3
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
ENGAGE
2025.2.0
NCS Circ
2025-2.0
Subscribe Extracts
Australian Clients - Extract Version 6 Other Clients - Extract Version 5
Sync Jobs
2025.3.0
Circ Pro
2025-1.0
DSI (Saxo Circ)
Supported
Naviga Pay (if using)
2.2
Recommended Engage Version
2025.3.0
🔑Key Features
1. Subscribe-CircPro Real Time Integration
New subscriptions for CircPro clients can now be created and processed in real time when purchased through the Subscription Panel (SP).
Previously, new subscriptions created via SP were sent to a Subscription Queue in CircPro, which returned a temporary subscription ID to Subscribe. Payment events were not triggered at this stage, and Subscribe received the actual subscription ID only after the subscription was processed in CircPro—typically after the next publishing date.
With the current enhancement, Subscribe now captures the payment along with authorization & subscriptions are created in CircPro in real-time. The end-to-end flow for subscriber, subscription, and payment processing has been streamlined, significantly reducing delays and improving operational efficiency.
Real Time New Start flow for CircPro
The Purchase API new start request has been completely integrated with CircPro API. Subscribe's CircProMicroAPI handles all the logic for a successful end-to-end real time flow by sending requests and receiving responses from the CircPro API.
Existing subscriber check - Whenever a purchase request comes, at first API checks whether the same subscriber already exists in the Circ system.
Subscriber creation - If the subscriber does not exist, a request is sent to CircPro to create a new subscriber. Once a subscriber is created successfully, nameId is returned.
Subscription creation - For creating a subscription, a new endpoint /RealtimeCreateSubscription is introduced in CircProMicroAPI. The request will be sent to CircPro createSubscription endpoint, which returns the subscriptionId upon successful subscription creation.
Payment submission - The payment is captured in Subscribe, and a new endpoint (POST .../CircPro/RealtimePayment) has been created in CircProMicroAPI, which makes the payment in real time to CircPro.
Events Generated
In the end-to-end new start purchase flow in real time for CircPro clients all necessary events are logged in the system. The events generated against subscriptions would be available in SubCon Admin Event reports.
The Events created as per the real time flow is as follows:
140
FINDADDRESSOCCUPANT
Find the existing occupant or subscriber
141
ADDADDRESSOCCUPANT
Add a new occupant or subscriber
1111
ADDSUBSCRIPTION
Add new subscription
35
AUTHCC
Payment authorization
56
CCFUNDCAPTURE
Authorized payment capture
57
PAYMENTNEWSTART
Send payment info to respective Circ system
Implementation Note:
The EventProcessor must be mapped pointing to CircPro in NewspaperEventProcessorAssignments DB table for FINDADDRESSOCCUPANT, ADDADDRESSOCCUPANT, and PAYMENTNEWSTART events.
Following MG2 Control Api setting keys must be configured:
Flow.CircProIntegration - Set this as "RealTime" to run the new start in real time. For existing queue flow, set any value, for example, "Queue".
CircPro.Tenant - Details of CircPro tenant added by Naviga specific to each client.
CircPro.RestSubscribeWebService.EndpointAddress - Set the webservice URL to consume the newly created web Service of CircPro, SpringSubscribeWebService. The URL set in this key will be used to call subscriptions in real time.
2. FTC Compliance: User Consent and Subscription Transparency
To support FTC compliance and promote transparency, Subscribe has introduced user consent checkboxes before submitting payment details on key transaction pages of Self Service, such as One-Time Payments, Restart, E-Bill Sign out—ensuring users are informed and are aware of the terms and conditions of the transaction they are performing.
Additionally, on the final Congratulations page of the new start flow, users are now shown key date details—Start Date, Expiration Date, and Cancel Before Date—alongside other important subscription information. The Cancel Before Date indicates the last day the user can cancel the subscription to avoid auto-renewal.
2.1 New Terms and Conditions Checkboxes on Self-Service Pages
Newly introduced checkboxes allow end users to explicitly provide consent for corresponding transactions. A transaction will not proceed unless the checkbox is checked - the Next button remains grayed out by default. Once the checkbox is checked, the Next button is enabled, allowing the user to continue the transaction. The checkbox label and associated condition text are sourced from the corresponding CMS content elements for each page.
One-time Payment Page
One-time payment Page CMS Content Elements
Restart Page
Restart payment Page CMS Content Elements
eBill Sign Out Page
eBill Sign out CMS Content Elements
Implementation Note:
New CMS content elements have been introduced to display the consent checkbox label and condition text on the Self-Service pages. One-time payment page: (CMS > Content > Payment).
Payment.TermsAndConditionsLabelText - Label of the checkbox
Payment.TermsAndConditions - The terms and conditions text content
Restart page: (CMS > Content > SubscriptionRestart)
SubscriptionRestart.TermsAndConditionsLabelText - Label of the checkbox
SubscriptionRestart.TermsAndConditions - The terms and conditions text content
E-Bill Sign out page: (CMS > Content > EbillManage)
EbillManage.TermsAndConditionsLabelText - Label of the checkbox
EbillManage.TermsAndConditions - The terms and conditions text content
2.2 New Date Fields on Final Congratulations Page
The Start Date, Expiration Date, and Cancel Before Date of the purchased subscription will be displayed on the final Congratulations page during new starts.
These dates will only be displayed when:
The corresponding CMS properties are enabled. (Refer to the image below) (Subscription StartDate, Subscription Expiration Date, Subscription CancelBeforeDate)
The date values are available from the Purchase API.
Note: These properties can be toggled on/off in the CMS Presentation to control their display on the Congratulations page. The label texts of the date properties are customizable. However, even if the properties are enabled, they will not be displayed unless the corresponding values are available in the Purchase API.
Configuring Date attributes in Subscriber Email
The following date attributes can be configured in the subscriber email template in SubCon Admin, if required.
Subscription.StartDate
Subscription.ExpirationDate
Subscritption.CancelBeforeDate
Additional Enhancements
To facilitate the display of these three date fields on the Congratulations page, the following enhancements have been implemented.
Three new optional fields — Promotional term unit, Promotional term length, and Renewal offset (in Days) —have been added to the Coding section under Billing system codes in SolCon.
Promotional term unit: Dropdown with values Day, Week, Month, Year
Promotional term length: Integer value greater than or equal to 1 (text field)
Renewal offset (in Days): Integer value greater than or equal to 1 (text field)
While creating an offer group, the values entered in these fields will be saved in the database.
Three new parameters have been added to the /Offer API response. These parameters will be included in all endpoints of the Offer API that return regular term and length details.
RenewalOffset
PromotionalTermLength
PromotionalTermUnit
During the New Start flow, if both Promotion Term Unit & Term Length are available in the Offer API, the Purchase API will calculate and return the parameters CancelBeforeDate and ExpirationDate in the response. These details will be:
Saved in the database against the corresponding subscription.
Made available as attributes for use in email templates, enabling the information to be shared with subscribers via email.
This enhancement applies to both NCS and CircPro clients.
StartDate logic:
For NCS: StartDate = Current Date
For CircPro: StartDate = Next Publishing Date (Existing Logic)
The following Component properties have been introduced in the Confirmation V3 component that can be configured to be displayed in the Congratulations Page of the Subscription Panel:
Subscription Start Date: A toggle button to show or hide the subscription start date from being displayed on the Congratulations page, a Start Date label text (Subscription.StartDate & Subscription.StartDateText).
Subscription Expiration Date: A toggle button to show or hide the subscription end (expiration) date, and an Expiration Date label text (Subscription.ExpirationDate & Subscription.ExpirationDateText).
Subscription Cancel Before Date: A toggle button to show or hide the cancel date (the date before which the user can cancel the subscription to avoid renewal), along with a field for the Cancel Before Date label text (Subscription.CancelBeforeDate & Subscription.CancelBeforeDateText).
3. Data Support Tickets - SubCon Admin
This feature is currently in its Beta version.
Subscribe has implemented a solution to reduce the turnaround time (TAT) for data removal support tickets related to CCPA and GDPR. A new menu option -Support > Manage Requests - and a corresponding page have been introduced in SubCon Admin, allowing clients to raise data removal support requests in the context of CCPA/GDPR. This screen will be accessible to users with the 'Client Admin' role.
With this feature, an SA user will be able to:
Raise a new data support request through SA Click the Create New button, enter the Title and the Description of the request. This will create a corresponding data support ticket.
View a Requests grid with requests logged by all users of the respective client. The grid details include Request ID, Summary (title of the ticket), and Requested Date. Each request has a Details button along with it, which displays the Title and the Description of the ticket.
Cancel a request (drop) Click the Drop button along with each request to delete the selected request. The Drop button of already dropped tickets will be displayed as disabled.
Refresh the status of tickets Click the Refresh button on the top right of the page, it refreshes the page and provides the latest status of requests.
🌐General Enhancement
Mapping the Subscription Kind of the Complimentary Subscriptions - CircPro
Starting from this release, when Complimentary subscriptions are created in CircPro, the SubscriptionKind of these subscriptions will be displayed as ‘Comp’ when these subscriptions are synchronized to Subscribe. This is determined by identifying the Billing Method "Free" for CircPro subscriptions.
🛠Bug Fixes
1. Adding owners to a Subscription
An issue that allowed users to add more owners to a subscription than the defined maximum—provided it was within the overall registration count—has been resolved. With this fix, users can now add owners only up to the configured max owners limit, not more than that.
2. Issue with Canadian Zip codes
The display of Canada Zip code values in SubCon Admin was not in the intended format. This issue has now been resolved. After the fix, Canada zip codes are displayed in SubCon Admin in the expected format.
Last updated
Was this helpful?