2025.5
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.
This release is currently in beta.
Release Prerequisites
ENGAGE
2025.2.0
NCS Circ
2025-3.0
Subscribe Extracts
Australian Clients - Extract Version 6 Other Clients - Extract Version 5
Sync Jobs
2025.5.0
Circ Pro
2025-1.1
Naviga Pay (if using)
2.2
Recommended Engage Version
2025.5.0
🔑Key Features
💳🚀Moneris NavigaPay Integration - Phase 1
This enhancement enables seamless integration of Moneris as a payment processor within the existing NavigaPay framework.
SS & SP - Moneris Payment Vendor via NavigaPay
Credit card payment transactions via Moneris NavigaPay have now been implemented in the Self Service portal and Subscription Panel. When an end user selects Credit Card as the payment method for a client configured with the Moneris NavigaPay payment vendor, the corresponding payment iFrame is loaded on the payment page/tab. The user can then enter their card details, and the transaction will complete successfully.
This enhancement establishes a seamless, end-to-end payment flow through Moneris NavigaPay, from payment initiation to successful completion in Circ.
Note: A common CSS will be used across all Subscribe applications for Moneris NavigaPay payment integration.
API Enhancements for Moneris Integration
The Subscribe API now supports Moneris as a payment processor option through NavigaPay for credit card transactions.
New request and response parameters have been introduced as required for the Moneris integration.
Consumer applications integrating Moneris via NavigaPay for credit card payments now receive all necessary parameters in the API response.
The TransactionCode parameter from the NavigaPay response for Moneris transactions is passed to NCS as the TranCode parameter.
Implementation Note:
To enable Moneris via NavigaPay, configure the following:
NavigaPay.SiteCode
NavigaPay.SiteKey
SubConSite.NavigaPay.SiteKey
SubConSite.NavigaPay.SiteCode
🆕💳New NavigaPay Credit Card CMS Component
A new CMS component, “Credit Card NavigaPay,” has been introduced to consolidate all the configuration properties required for various NavigaPay payment vendors — including Payway, Paytrace, Eigen, ImpressPay, and Moneris.
This component can be added as a child element under the Payment Methods V3 component in any CMS presentation. The desired payment vendor for a specific client can be selected from the drop-down list provided at the top of the component. A note is provided under each property to specify whether it applies to all vendors or only to specific ones.
Note:
All clients using NavigaPay must switch to this new Credit Card NavigaPay component.
When configuring the Credit Card NavigaPay component, ensure that all properties applicable to the selected payment vendor are properly configured for seamless integration.
💱NavigaPay FluidPay Payments Refactor
The FluidPay Split Payment process which was introduced in 3.17.2 has been deprecated in this release. When the Cash Discounting feature is enabled and the payment vendor is FluidPay, the following key changes have been introduced in the New Start flow:
Subscribe now sends the total amount (including base amount, tip, donation, tax, and processing fee) as a single parameter.
Additionally, the processing fee and tax are sent as separate parameters for reference.
Split Amount will no longer be sent.
There will be a single AuthCC and FundCapture request from Subscribe.
For Subscription Restart and Payment flows in Self Service, a new parameter ‘taxAmount’ will now be included in the Circ API calls when Cash Discounting is enabled for FluidPay. All other values are already sent from Self Service.
Implementation Note:
Configure the following:
Vendor = ImpressPay
DTI.CashDiscounting for NCS
CircPro.VariablePricing key for CircPro
🌐General Enhancements
Self Service
1. Hiding the Tip page and Tip field for Digital Subscriptions for NCS clients
The Tip field on the payment pages of One-time Payment, Restart, and Autopay Signup flows will now be hidden for digital subscriptions. If the DeliveryMethod of a subscription is returned as “Mail” or “Online” by the API, the Tip field will no longer be displayed on the payment pages of any of the above-mentioned flows.
Additionally, two new Link Restrictions — Mail Subscription and Digital Subscription — have been introduced in CMS. When configured on the Add Tip link, these restrictions ensure that the corresponding page link is not displayed on the Dashboard page for subscriptions with delivery methods Mail or Online.
Implementation Note:
The restrictions are to be configured in: CMS > Navigation > Links > Add Tip > Hide Link For > Mail Subscription and Digital Subscription
CMS
1. New property "EEditionUrl" in the Confirmation component
A new CMS property “EEditionUrl” has been introduced in the Confirmation V3 component. The value of this property can be any valid URL. When the end user clicks the ‘Continue’ button on the Confirmation page, they will be redirected to the URL configured in this property.
With this enhancement, clients can now flexibly route their end users to any desired page — such as an E-Paper, Self-Service Portal, news site, or any other valid destination — directly from the Confirmation page.
Implementation Note:
To configure, navigate to Page V3 > Confirmation V3 component > EEdition EEditionUrl property.
API
1. Surcharge for PayPal transactions when Cash Discount is enabled
When the Cash Discount feature is enabled and the payment method is PayPal, the cash discount will not be applied to the end user. Instead, a surcharge amount will be added to the transaction.
Implementation Note:
Enable the MG2 Api setting DTI.CashDiscounting key.
🛠️ Bug Fixes
API
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.
Subscription Panel
1. Card fields disappearing on the Payment page
The card fields that should appear on the payment page when using the NavigaPay ImpressPay payment option went blank when new start flows were initiated via the Subscription Panel.
This issue has now been resolved. After the fix, when a user selects NavigaPay ImpressPay as the payment option, the payment iFrame loads correctly with all required card fields displayed as expected.
CreditCardTypeID updated as Null for Master/Amex cards after Sync process of NCS clients
During the new start flow of NCS clients, when a payment was made using MasterCard or American Express via ApplePay Payway, the CreditCardTypeID in the database was being updated to NULL after the nightly data sync process. This issue has now been resolved.
After the fix, the CreditCardTypeID value is correctly retained as '3'—the expected value after the nightly sync—when payments are made using MasterCard or American Express via ApplePay Payway during the new start flow.
2. Issues in NavigaPay integration
The issues identified during integration with Naviga Pay have been resolved.
When the Submit Button text was left blank in CMS, the ImpressPay flow was not working. This issue has been resolved. After the fix, if any CMS property is left blank, the corresponding default value configured in the codebase will be applied, ensuring that the flow remains unaffected. Note: The use of default values from the codebase when a CMS property is left blank applies only to the Credit Card NavigaPay component.
The Submit button in the ImpressPay iFrame was getting cut off when using the Seamless theme, in cases where the First Name and Last Name fields were displayed on separate lines or rows. This issue has been fixed by increasing the iFrame height.
Last updated
Was this helpful?