2026.1

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-3.0
Subscribe Extracts	Australian Clients - Extract Version 6 Other Clients - Extract Version 5
Sync Jobs	2026.1.0
CircPro	2025-1.1
CircPro Extracts	3.6 (Recommended)
Naviga Pay (if using)	2.2

Recommended Engage Version

2026.1.0

🔑Key Feature

💳Apple Pay & Google Pay Payway via NavigaPay in Self Service

Up until this release, Bank Account and Credit Card were the only payment methods available in Self Service for various payment transactions for both NCS and CircPro clients. Subscribe now supports Apple Pay and Google Pay payment methods via Payway NavigaPay in Self Service (SS) for the following payment flows:

1. One time payment

2. Update payment (Change Payment method)

3. EZPay Sign up

4. Restart payment (Only for NCS)

5. Downgrade/Upgrade payment (Only for NCS)

6. StopSaver payment (Only for NCS)

7. Add Tip payment (Only for NCS)

1. Apple Pay via Payway NavigaPay

1.1 'Apple Pay' Payment method option

'Apple Pay' is now available as a payment method option on the following Self Service payment pages.

• One time payment

• Update payment (Change Payment method)

• EZPay Sign up

• Restart payment (Only for NCS)

• Downgrade/Upgrade payment (Only for NCS)

• StopSaver payment (Only for NCS)

• Add Tip payment (Only for NCS)

Refer to some of the example screenshots given below:

Apple Pay payment option for One time payments

Apple Pay button to initiate payments

Apple Pay pop-up with payment details

Whenever the payment is related to AutoPay, the following additional information is displayed in the Apple Pay pop-up as applicable:

• Term

• Length

• Recurring amount

• Billing agreement

• Recurring payment information

Apple Pay pop-up with additional payment details

1.2 Labels for Apple Pay (Payway) Payments

The following CMS content keys have been added to display Apple Pay as a payment option in Self Service:

• PaymentMethod.ApplePayText

• Billing.Widget.WalletLabel

These labels have been added to the following pages: Payment, AutoPaySignUp, AutoPayManage, AddTip, SubscriptionRestart, SubscriptionUpdate, and StopSavers, so that the Apple Pay option is displayed correctly in the respective Self Service payment flows.

Content key to display the Apple Pay payment option on the Add Tip Page

Note:

• During Apple Pay payments, if the card used by the user supports MPAN (Merchant Primary Account Number), Subscribe submits the payment method as ‘ApplePayMPAN’ to NCS. In all other cases, Subscribe submits the payment method as ‘ApplePay’ to NCS.

• After a successful Apple Pay payment, the Credit Card Number field is displayed as “****” on the payment success pages of Self Service. Since Apple returns a DAN (Device Account Number) instead of the actual card number, the value is masked.

• Likewise, when a user selects the Apple Pay payment option in SP, the system displays “****” in the Credit Card Number field on the Congratulations page.

Implementation Notes:

• The application URL of Self Service must be verified by Apple via Payway. Naviga Implementation team will get this done, when requested.

• The following mandatory field must be configured in the NavigaPay properties file.

  • applemerchantId

• To configure NavigaPay, set the following MG2 Control api keys:

  • NavigaPay.Integration: 'Payway'

  • SubConSite.NavigaPay.SiteCode: <valid value>

  • SubConSite.NavigaPay.SiteKey: <valid value>

• To display the Apple Pay payment option on the payment pages, configure the corresponding CMS content keys on the Payment, AutoPaySignUp, AutoPayManage, AddTip, SubscriptionRestart, SubscriptionUpdate, and StopSavers pages. Update the text for the payment option in CMS as needed.

  • PaymentMethod.ApplePayText

  • Billing.Widget.WalletLabel

• Enable the Apple Pay option in Support Viewer > Api settings > SubCon.Configuration by updating each Payment page configuration wherever applicable:

"PaymentTypes": ["CreditCard", "BankAccount", "ApplePay"]

With this, a new ‘Apple Pay’ payment option is now available as a selectable option on the payment pages along with other payment methods.

• Add the following under BillingWidgetSection in Subcon.Configuration:

  "WalletPaymentSection": {
    "PaymentProvider": "NavigaPay"
  }

• Add the following under BillingWidgetSection in Subcon.Configuration:

  • The new object, ApplePayMpan must be configured with the fields, RecurringPaymentInfo, BillingAgreement, PaymentDescriptor for displaying custom messages to be displayed in the Apple Pay iframe (Apple Pay Billing screen). Payment Descriptor is available to subscribers in their account statement via Apple. (Note: The PaymentDescriptor field is not displayed in the iFrame. It is required only for configuration purposes.)

"BillingWidgetSection": {
  "BankAccountSection": {
    "PaymentProvider": "Default",
    "Types": ["CheckingsAccount", "SavingsAccount"],
    "DisplayBankHolderName": true
  },
  "CreditCardSection": {
    "PaymentProvider": "NavigaPay"
  },
  "WalletPaymentSection": {
    "PaymentProvider": "NavigaPay"
  },
  "ApplePayMpan": {
    "RecurringPaymentInfo": "This is the recurring payment information",
    "BillingAgreement": "This is the billing agreement information",
    "PaymentDescriptor": "This is the payment descriptor"
  }
}

2. 💳Google Pay Payway via NavigaPay

1.1 'Google Pay' Payment method option

'Google Pay' is now available as a payment method option in the following Self Service payment pages.

• One time payment

• Update payment (Change Payment method)

• EZPay Sign up

• Restart payment (Only for NCS)

• Downgrade/Upgrade payment (Only for NCS)

• StopSaver payment (Only for NCS)

• Add Tip payment (Only for NCS)

Refer to some of the example screenshots given below:

Google Pay payment option in One time payment flow

Google Pay payment option in EZPay Sign up flow

Google Pay button to initiate payment

Google Pay pop-up with payment details

2.2 Labels for Google Pay Payments

The following CMS content keys have been added to display Google Pay as a payment option in Self Service:

• PaymentMethod.GooglePayText

• Billing.Widget.WalletLabel

These labels have been added to the following pages: Payment, AutoPaySignUp, AutoPayManage, AddTip, SubscriptionRestart, SubscriptionUpdate, and StopSavers, so that the Google Pay option is displayed correctly in the respective Self Service payment flows.

Content key to display the Google Pay payment option on the Add Tip Page

Implementation Notes:

• The following mandatory fields must be configured in the NavigaPay properties file.

  • googlePayGateway

  • googlePayGatewayMerchantId

  • googlePayMerchantId

  • googlePayMerchantName

• To configure NavigaPay, set the following MG2 Control api keys:

  • NavigaPay.Integration: 'Payway'

  • SubConSite.NavigaPay.SiteCode: <valid value>

  • SubConSite.NavigaPay.SiteKey: <valid value>

• To display the Google Pay payment option on the payment pages, configure the corresponding CMS content keys on the Payment, AutoPaySignUp, AutoPayManage, AddTip, SubscriptionRestart, SubscriptionUpdate, and StopSavers pages. Update the text for the payment option in CMS as needed.

  • PaymentMethod.GooglePayText

  • Billing.Widget.WalletLabel

• Enable the Google Pay option in Support Viewer > Management > Api Settings > Subcon.Configuration by updating each Payment page configuration wherever applicable:

  "PaymentTypes": ["CreditCard", "BankAccount", "GooglePay"]

  With this, a new ‘Google Pay’ payment option will be available as a selectable option on the payment pages along with other payment methods.

• Add the following under BillingWidgetSection in Subcon.configuration:

  "WalletPaymentSection": {
    "PaymentProvider": "NavigaPay"
  }

🌐General Enhancement

API

1.Removing Dependency on EFT and Credit Card Description for CircPro Payments

The dependency on the Description parameter (for example, EFT_payment_type) has been removed from CircPro payments. The system now determines the payment type based on the payment category instead of the description.

• Bank and Credit Card payments for CircPro are supported regardless of the description configured for the payment method, as long as the EFT category is available.

• The same behavior applies to Credit Card payments using their respective category.

• The system passes the correct PaymentTypeId back to CircPro based on the category, not the description.

This change makes the integration more flexible and avoids issues caused by client-specific or custom descriptions configured in CircPro.

Note:

• The Bank and Credit Card payment category must be configured in CircPro for Bank and Credit Card payments to work.

• This change does not apply to Queue Newstart.

🛠️ Bug Fixes

API

1. Restart & Newstart failures with Google Pay/Apple Pay via Braintree

Restart/Newstart subscription flows with payments using GooglePay/ApplePay via Braintree were failing for CircPro clients. This issue has now been resolved. After the fix, users can complete Restart and Newstart flows using GooglePay/ApplePay through Braintree without any errors.

2. New Subscribers Showing Status “Future” When the status in NCS is Active

Some new subscribers were unable to access content in client apps because their subscription status was not getting synched in realtime from NCS when it was 'Future' in Subscribe. This issue has now been fixed.

3. 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 2025.4.1 & 2025.5.1.

Database

1. Error when Starting a Call from SubCon Admin for CircPro

For CircPro clients, the SubscriptionKindId value for certain subscriptions was being set to 'null' in Subscribe. As a result, users encountered an error when trying to start a call for those accounts in SubCon Admin. This issue has now been resolved. After fixing the business logic in the CircPro extracts, starting a call from SubCon Admin for CircPro clients no longer shows this error.

Note: This fix requires CircPro Extract Version 3.6.

Future Enhancement

PayPal via NavigaPay Payway

As part of integrating PayPal payment method via NavigaPay Payway, it has been implemented in the Payments API to support wallet payments in Self Service (SS) for both NCS & CircPro clients.