> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/naviga-subscribe/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/naviga-subscribe/welcome-to-subscribe/subscribe-release-notes/2026.2.md). # 2026.2 {% 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 | Integrations | Minimum Version | | ----------------------------------------- | ----------------------------------------- | | ENGAGE | 2025.2.0 | | NCS Circ | 2025-3.1 (with ETP for PayPal) | | Subscribe Extracts |

Australian Clients - Extract Version 6 | |
Other Clients - Extract Version 5

| | | Sync Jobs | 2026.2.0 | | CircPro | 2025-1.1 | | CircPro Extracts | 3.6 (Recommended) | | Naviga Pay (if using) | 2.2 | #### Recommended Engage Version 2026.2.0 ## 🔑Key Feature ### 🏦Bank Account Payments via NavigaPay Payway for NCS Subscribe now supports tokenized Bank Account payments via NavigaPay Payway for payments from Subscription Panel, Self Service and LTE for NCS clients. This feature is configurable. Previously Subscribe did not authorize/capture bank account payments. With this new integration, bank account payments are now tokenized and processed via NavigaPay Payway. #### 🔄Functional Workflow: Bank Account payments via NavigaPay Payway happens in two steps: **Tokenization and Transaction**. **Tokenization (Profile Creation)** * User enters bank details (Account Number, Routing Number, Account Type, Account Holder Name) on the payment page and clicks the Submit button. * Subscribe triggers the **CreateUserProfile** event and passes all bank details to NavigaPay. * NavigaPay validates details from Payway and returns a Profile ID. * This Profile ID is sent to NCS as `BDTokenID`. (No payment is captured at this stage.) **Transaction (ACH Sale)** * Subscribe triggers the new **ACHSALE** event. Subscribe passes Profile ID, Transaction Amount, PaymentType, and other details to NavigaPay. * NavigaPay inturns passes the details to Payway to process the transaction and returns a Transaction ID. * Subscribe sends this Transaction ID to NCS as `BDTranID` along with `BDTokenID`, `BDAuthNumber`, and BDUniqueCustomerID. {% hint style="info" %} **Note**: A default value, **“**Settlement Pending**”** is sent as `BDAuthNumber`. With this value, NCS treats the payment as captured and does not reprocess it. However, although the payment is tokenized, capture does not occur in real time. Instead, NCS validates the settlement status via NavigaPay. The transaction is typically settled within a couple of days. {% endhint %} {% hint style="info" %} * Two new events support this integration: * `CREATEUSERPROFILE` → For tokenization * `ACHSALE` → For payment processing * Four new parameters introduced: * `BDTokenID` → Token/Profile ID * `BDTranID` → Transaction ID * `BDAuthNumber` → Sent as “Settlement Pending” * `BDUniqueCustomerID` → Reserved for future use {% endhint %} #### 🔐**Tokenized Bank Payments in SP, SS, and LTE** The functional workflows in SP and SS remain the same. The only difference is in the calls that are made to NCS and the details that are passed to NCS. * Payments in **Subscription Panel** - the Profile ID returned by NavigaPay is sent to NCS as `BDTokenID` in the AddSubscription call. * Payments in **Self Service** - the `BDTokenID` (Profile ID) is sent to NCS in different events in different workflows. * Onetime Payments - `BDTokenID` and `BDTranID` are passed in PaymentACH * Restart Subscription - `BDTokenID` and `BDTranID` are passed in RestartPaymentACH * Sign up for EZPay - `BDTokenID` is passed in the EZPAY event * Recurring payments (EZPay) * Tip flow - `BDTokenID` will not be passed in CHGACH event * Update payment method - `BDTokenID` will be passed in CHGACH event * Upgrade/Downgrade/StopSaver * If user switches from Non-EZPay offer to EZPay offer - `BDTokenID` will be passed in EZPAY * If user switches from Non-EZPay offer to Non-EZPay offer or from EZPay offer to EZPay offer - EZPay event is created, `BDTokenID` will not be passed {% hint style="info" %} **Note**: In some SS payment flows, the `BDTokenID` is not sent to NCS because it already exists for the corresponding user. For example, during a downgrade flow, when a user switches from one EZPay offer to another, NCS already has the user’s `BDTokenID` , so no additional token is required or sent. {% endhint %} * Payments in **LTE -** A new field, Account Type, has been added to LTE screen, with options *Savings* and *Checking*. This allows users to select the appropriate account type when submitting a new start via bank payment. The selected value is included in the NavigaPay request.

New Payment method - Bank draft & new field Account Type in LTE

{% hint style="info" %} **Note:** There is no change to the overall payment flow in LTE. The API determines whether to process the payment via NavigaPay or to submit the payment information directly to the circulation system (the latter follows the existing flow). {% endhint %} **Configuration Note**: The tokenized Bank Account payment in the consumer applications (SP, SS & LTE) are applicable only when payment is via **NavigaPay Payway for NCS clients**. 1. Set the below mandatory MG2 Control Api setting keys: 1. NavigaPay.Integration = payway 2. ProcessACHSale = 1 (mandatory setting to enable tokenized bank account payments via NavigaPay Payway) 3. Flow\.BillingProvider= NavigaPay 2. Event Processor Assignment:\ Insert the following records into NewspaperEventProcessorAssignments:\ Event: CREATEUSERPROFILE → EventProcessor: NavigaPay\ Event: ACHSALE → EventProcessor: NavigaPay #### 🧩New CMS ‘Account Type’ property in Bank Account Components (Subscription Panel) To support Bank account payments (ACH) for new starts and restarts via NavigaPay Payway, new Account Type properties have been introduced in the CMS Bank Account components of SP Presentations. Once configured and enabled, the Account Type property is displayed on the Place order and Confirmation pages of bank payments, where applicable. 1. BankAccountV3 Component 1. AccountType → Show (Toggle) 2. AccountType →Title (String) When Account Type is toggled ON in the BankAccountV3 component: * A dropdown is displayed with the options: Checking, Savings, and None. * The selected account type is submitted to the Subscribe micro API. When toggled OFF: * The Account Type dropdown is not displayed in the Presentation.

Account Types displayed in SP Presentation for Bank Account Payments

2. PlaceOrderV3 Component: 1. PaymentInformation -> BankAccount → AccountType (String) 3. ConfirmationV3 Component: 1. PaymentInformation → BankAccount → AccountType (String) **Note**: No changes are required in the Presentation components for SP. The existing components can be used as is. **Note**: Account Type is sent to NCS as “savings”, “checking”, or "none" based on the user input. If the input is invalid, “checking” is sent by default to avoid breaking the flow (consistent with existing behavior). Although the display names of these payment options can be customized in the config file, they are internally treated as “savings”, “checking”, and "none" respectively. {% hint style="info" %} **Note**: * There is no impact on the CircPro flow—existing behavior remains unchanged regardless of user input. (Capturing user input for Account Type is not recommended at this time). * The Account Number, Account Holder Name, Routing Number, and Account Type for bank payments are not displayed/fetched in SubconAdmin. {% endhint %} ## 🌐General Enhancements ### SubCon Admin #### 1. Support Ticket Feature - API Upgrade The integration API for **Support Ticket** feature that used to submit data deletion requests was recently deprecated by the service provider. This has now been updated to use the new API without affecting any UI functionality. Users can continue to create new tickets and view the status of their client’s tickets as before. It may happen that a newly created ticket does not appear immediately in the grid and may require a manual refresh. **Note**: A fix has also been sent to SubCon Admin to allow users to enter support ticket title up to 150 characters. ### Self Service #### 1. TnC enhancements on Update Payment page The position of the TnC text has been moved next to the checkbox, above the **Next** button, on the Update Payment page to ensure consistency across all payment screens. **Note**: * The Next button is enabled only after the end user selects the TnC checkbox. The iframe loads only after the user clicks the Next button. * Once the Next button is enabled, the TnC checkbox will remain disabled in the checked state further in the flow. * Additionally, if the user clicks on the Back button, the SUBMIT button will be disabled.

TnC checkbox unselected and Next button disabled

TnC checkbox selected and Next button enabled

TnC Checkbox disabled in the Checked state

#### 2. Accessibility Enhancements in Self Service Pages * Fixed and standardized alternative texts have been added to images on the My Account page. Alt text describes an image and is particularly useful for users who rely on screen readers to access content. * Scaling and Zooming have been enabled in the My Account page. The end user is now able to resize text to at least 200 percent without loss of content or functionality. ### LTE #### 1. New Payment Vendors in LTE (NavigaPay Payway & NavigaPay ImpressPay) LTE now supports newstart payments using Credit Cards via NavigaPay Payway and NavigaPay ImpressPay, enabling clients to seamlessly transition to NavigaPay without disruption. **Note**: Support has been added for Credit Card payments via NavigaPay Payway and NavigaPay ImpressPay, while Billed and Check payment methods continue to function without any changes. **Configuration Note**: To enable NavigaPay Payway/ImpressPay for LTE- 1\. Set the following MG2 Control API keys: * `Billing.CreditCardProcessingProvider = navigapay` * `LTE.NavigaPay.SiteCode =`` ``` #### 2. Variable Pricing in LTE via NavigaPay for NCS The Variable Pricing Feature has been implemented in LTE starting from this release. When Variable Pricing is enabled: * The Offer Details page displays the rate amount including surcharge, along with the marketing text configured in SolCon for the selected offer. * On the Payment page: * For Credit Card payment method, the displayed rate includes the surcharge. * For other payment methods, the displayed rate excludes the surcharge (i.e., the discounted amount).

Pricing for Bank Account/Billed/Check Payment methods

Pricing for Credit Card Payment method

The system dynamically recalculates the subscription cost in real time when users switch between payment methods (Credit Card, Bank, Billed, Check). The final calculated amount, based on the selected payment method, is submitted to the API and the circulation system: * **Credit Card:** Amount includes surcharge * **Bank/Billed/Check:** No surcharge applied **Configuration Note**: Set the following MG2 control Api setting keys * DTI.CashDiscounting → 1 * Billing.CreditCard.ProcessingFee.Enable → 0 ### Subscription Panel #### 1. Integration with Google reCAPTCHA Enterprise for securing application Subscription Panel is now integrated with *Google reCAPTCHA Enterprise* to enhance protection against automated bot traffic, carding attacks, and fraudulent requests. This implementation includes server-side token verification and risk score evaluation to detect and prevent suspicious activity. **Key Enhancements** * Detects and restricts automated bot activity during critical user actions * Strengthens security for subscription and payment-related operations * Reduces risks such as carding attacks, credential stuffing, and fraudulent requests * Validates user actions using risk-based scoring before processing requests **How It Works** * A reCAPTCHA token is generated on the frontend during critical actions (e.g., login, subscription, payment). * The token is sent to the backend along with the request. * The backend validates the token using Google reCAPTCHA Enterprise and evaluates the risk score. * Based on validation and risk score: * Valid requests are processed normally * Suspicious or invalid requests are rejected or flagged **Impacted Areas** reCAPTCHA validation is applied to key flows, including: * Subscription actions (e.g., new subscriptions) * Address validation * Payment-related operations (including PayPal, Apple Pay, Google Pay, and other integrations) * User actions (e.g., login, email verification) * Gift redemption flows {% hint style="info" %} **Note**: * This security enhancement does not impact the UI or the functional flow in SP. * The new setup will be enabled by default with the 2026.2 upgrade. Clients can manage reCAPTCHA settings from Presentations. {% endhint %} **Configuration Notes**: 1. To enable this feature, set the CMS toggle **TurnOffCaptcha** to **OFF** and configure the desired risk score in the **reCAPTCHAScore** field. 2. Naviga implementation setup details are available in the internal documentation. ### API #### 1. Trial Subscriptions with PayPal Payment option Subscribe now supports Trial subscriptions with PayPal as a payment option. When an end user selects PayPal while subscribing to a trial: * No upfront payment is captured. * Payment details are collected and tokenized. * The tokenized information is passed to NCS. This functionality is supported in payment via PayPal with Braintree integration as well. {% hint style="info" %} **Note**: PayPal Express Checkout is not supported. {% endhint %} #### 2. Paypal Payway integration with NCS (Refactor) The PayPal Payway integration with NCS has been updated as follows: * When the payment method is PayPal Payway, *PayPal* will be sent as the Payment Type to NCS. Previously, it was sent as the Payment Source under Credit Card. * Hardcoded values will no longer be used for PayPal transactions. * The *email* value will be correctly passed in the appropriate parameter. * CC surcharge will be removed for PayPal payments (applicable for Variable Pricing), as it is not relevant. **Note**: This is applicable to both new starts and renewals. {% hint style="info" %} **Note**: The minimum supported NCS version for PayPal transactions through NavigaPay Payway is 2025-3.1. However, PayPal functionality is only available with a subsequent NCS ETP release beyond 2025-3.1. Customers must ensure the appropriate NCS ETP has been installed before configuring PayPal. {% endhint %} ## 🛠️ Bug Fixes ### Self Service #### 1. eBill Sign Up link visible to eBill Subscribers The eBill sign-up link was visible to existing eBill subscribers in the Self Service portal, even when the 'Hide Link' setting was configured in the CMS. This issue has now been resolved. After the fix, the eBill Sign up link is no longer visible to eBill subscribers. #### 2. Login Failure for Valid Credentials in Self Service An issue was identified where a limited set of users were unable to log in to Self Service using valid email and password combinations, resulting in an “Invalid LoginName” error. This issue has been resolved. The system now correctly identifies the exact email address and validates the corresponding password, ensuring successful login for valid credentials. ### SubCon Admin #### 1. Error message while registering an Email in User Accounts An issue was observed where users received an error message — “Invalid email Undefined” — when clicking the Registration button next to an email in the search results (User Accounts > Search > Registration). This issue has been resolved. After the fix, clicking the Registration button no longer shows any error, and users can successfully unlink subscriptions, add new subscriptions, or edit profile settings. ### Subscription Panel #### 1. Date details missing on the Confirmation Page Date details such as Start Date, Expiration Date, and Cancel Before Date were not displayed on the Confirmation page for a customer-specific custom presentation, despite correct configurations in SolCon and CMS. This issue has been resolved. After the fix, the date details are correctly displayed on the Confirmation page. #### 2. Error message disappearing from the UI The expected error message — *“There is an error placing your order. Please contact customer service to make your purchase.”* — was initially displayed correctly on the UI. However, it disappeared when the user clicked the **Continue** button again on the User Information page in SP. This issue has been resolved. After the fix, the error message remains visible on the screen, and the user is prevented from proceeding further. ### API #### 1. Double payment deduction for pre-authorized, externally captured payments (NCS customers) An issue was identified where pre-authorized and externally captured payments, when submitted to NCS via the Subscribe Purchase API, were being captured again at NCS, resulting in duplicate charges to customers. This issue has now been resolved. As part of the fix, the Authorization Code is now included in payment requests sent to NCS for pre-authorized and captured transactions. This allows NCS to correctly identify such payments and avoid duplicate processing. After the fix, externally captured payments are now properly identified and processed in NCS without any additional deduction from the customer. #### **2. Missing ‘pacCardType’ in updateDataWithPAC Request for CircPro** An issue was identified where pacCardType was not being sent in the updateDataWithPAC request for certain payment types of CircPro. This has now been resolved. After the fix, the system determines the correct pacCardType based on the CategoryId provided by CircPro, instead of relying on the payment type description. As a result, pacCardType is now correctly passed for applicable payment types. **Note:** EFT payments continue to work as expected. For EFT, pacCardType is optional and may be sent as blank. #### 3. Failure in Processing Downgrade Events via ProsperStack Customers attempting to accept downgrade offers through ProsperStack with pending past dated move experienced continuous failures. This issue has been resolved. After the fix, end users are able to accept downgrade offers through ProsperStack and complete subscription update successfully without any failures. #### 4. Entitlement details not displayed while fetching Entitlements While fetching entitlement details for all newspapers in SubCon Admin, the results were not displayed on the screen in some cases.\ This issue has been resolved. After the fix, entitlement details are correctly displayed in the search grid. #### 5. Tax Amount Not Updated for NCS & CircPro clients When Switching Payment Method for New Starts (Variable Pricing Enabled) An issue was identified where the tax amount was not updated when NCS or CircPro users switched between Credit Card (CC) and Bank payment methods during new subscription starts where Variable Pricing feature was enabled. This issue has been resolved. After the fix, the tax amount is recalculated correctly based on the selected payment method. ### ​💡Future Enhancement #### --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.navigaglobal.com/naviga-subscribe/welcome-to-subscribe/subscribe-release-notes/2026.2.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.