2025.4

Release Prerequisites

Recommended Engage Version

2025.4.0

🔑Key Features

1. 🏦Bank Account Payments for Circpro

Subscribe now supports Bank Account payments for CircPro clients in the following payment flows:

• Newstart via Subscription Panel - Real-time

• Restart via Subscription Panel - Queue

• One-time payments, Autopay payment, and Update payment via Self Service - Queue

2. 🏷️Variable Pricing - CircPro

The Variable Pricing feature has been implemented in the following payment flows for CircPro clients:

• Newstart via Subscription Panel (SP)

• Restart via Subscription Panel

• One-time payment and Autopay signup via Self Service (SS)

With this feature, when the end user selects a payment method involving a credit card, a credit card processing fee (surcharge) will be applied. Unlike processing fees, this surcharge will not appear as a separate line item; instead, it will be included in the total amount displayed to the user. That means, the surcharge amount is added to the subscription rate (base amount), and the combined total is displayed as the subscription cost to the user. For payments made via Bank Account, users will see a lower total amount for the same offer, as this method excludes the surcharge.

Variable Pricing for CircPro is enabled through the MG2 Control setting: CircPro.VariablePricing.

1.1 Variable Pricing for Newstarts & Restarts via SP

For CircPro clients, Variable Pricing feature is now available only for Realtime Newstarts, not for Queue Newstarts. Variable Pricing is also available for Queue Restarts via SP. CircPro sends the surcharge amount (processing fee) along with rates, which Subscribe consumes to make Variable Pricing available for Realtime Newstarts and Queue Restarts via SP. In the Queue Restart flow, Subscribe performs only the authorization, while fund capture is handled by CircPro.

When Variable Pricing is enabled, the workflow is as follows:

1. The user selects the offer and enters the address details, including the ZIP code.

2. The user selects the payment method and provides the corresponding payment details. For CircPro, the currently available payment methods are:

   • Credit Card (Including Apple Pay/Google Pay)

   • Bank Account

   The subscription amount varies depending on the selected payment method and is displayed to the user as follows:

   • Credit Card/Google Pay/Apple Pay → Rate amount + Credit card processing fee + Tax (if enabled and applicable)

   • Bank Account → Rate amount + Tax (if enabled and applicable)

3. The user submits the payment. After authorization and fund capture, the Order Summary and the final Congratulatory pages are displayed.

1.3 Variable Pricing for One-time payment and EZPay Signup via SS

The Variable Pricing feature is available for One-time payments and EZPay Sign-ups (both are Queue processes) via the Self-Service portal for CircPro clients.

When Variable Pricing is enabled:

• Two different rates for the same offer are displayed on the Payment page:

  • A higher rate for Credit Card payments

  • A lower rate for ACH payments

• The user can choose their preferred payment method.

• Tip and/or Donation amounts can also be added along with these One-time or EZPay signup payments, as before.

The rate terms are fetched from CircPro, the subscription cost is calculated accordingly, and payment information is then submitted back to CircPro. The payment details include:

• Rates with surcharge → for Credit Card payments

• Rates without surcharge → for ACH payments (Bank Account)

Confihuration Notes:

1. A new MG2 Control setting CircPro.VariablePricing has been introduced.

   1. CircPro.VariablePricing set to 1 - The Variable Pricing feature is enabled.

   2. CircPro.VariablePricing set to 0/Null - The Variable Pricing feature is disabled.

2. Set the MG2 Control settings Flow.CircProIntegration = RealTime, Billing.CreditCard.ProcessingFee.Enable = 1

3. Enable the CMS property 'CashDiscounting.Enable' under the PaymentMethod V3 component

4. Disable the MG2 Control setting Billing.CreditCard.ProcessingFee.Enable

5. To setup taxes (if required):

   1. Set the MG2 Control Setting AllowTaxes to “1”

   2. Set the MG2 Control Setting Tax Engine as "FastTax"

   3. Validate the setup in NewspaperEventProcessorAssignments for GETTAX event pointing to the FastTax

6. Event GETRATECODEDETAIL should be enabled in NewspaperEventProcessorAssignments.

3. 💳GooglePay/ApplePay/PayPal Payway via NavigaPay

Subscribe supports the following payment methods in Newstart payment flows (SP) via Payway NavigaPay.

For NCS Clients:

• Apple Pay

• Google Pay

• PayPal

For CircPro clients:

• Apple Pay

• Google Pay

This enhancement enables clients to leverage the NavigaPay Dashboard to analyze and utilize the payment information captured for each transaction.

All existing configurations supported in the direct integration of Google Pay, Apple Pay, and PayPal Payway (without the NavigaPay middle layer) are also supported in the Payway integration. The above-mentioned payment methods are supported by the API when the selected payment vendor is NavigaPay Payway.

3.1 ApplePay Payway via NavigaPay

ApplePay Payway via NavigaPay supports the following flows in Newstarts:

• Full-page display with a Submit button at the end, where reauthorization is required

• Selecting a new offer through the Abandonment Popover with EZPay

• MPAN/DPAN (with or without EZPay) - supported for NCS

• ApplePay Billing Agreement for promotional offers (with/without Ezpay) There will be no dependency on Ezpay CMS component

Configuration Notes:

1. The CMS component “NavigaPay ApplePay Payway V3” must be configured with the required properties and should be included in the Presentation. Select an appropriate presentation -> Page V3 > Step V3 > Payment Methods V3 > NavigaPay ApplePay Payway V3 component.

2. Copy

   config.NavigaPayApplePayPayway = {
   	Constants: {
   		PaymentDescription: "Payment for news subscription",
   		BillingAgreement: "You are purchasing a news subscription"
   	},
   	CSS: {
   		defaultFileName: 'applePayDefault.css',
   		simpleFileName: 'applePaySimple.css',
   		seamlessFileName: 'applePaySeamless.css',
   		commonCSS: 'applePaySimple.css'
   	}
   }

   Note: CommonCSS is applied to all themes such as Minimal, Sleek, etc., except for Seamless, Simple, and Default.

3.2 GooglePay Payway via NavigaPay

A new component named “NavigaPay GooglePay Payway V3” has been introduced in CMS with the following properties:

1. Errors.ReAuthorize

2. Image

3. LearnMore.Show

4. LearnMore.Text

5. LearnMore.Url

6. Title

Configuration Notes:

1. The new CMS component “NavigaPay GooglePay Payway V3” must be configured with the required properties and should be included in the Presentation.

2. Select an appropriate presentation -> Page V3 > Step V3 > Payment Methods V3 > NavigaPay GooglePay Payway V3 component.

3.3 PayPal Payway via NavigaPay

A new component named “NavigaPay Paypal Payway V3” has been introduced in CMS with the following properties:

1. Alt

2. Description

3. Disclaimer

4. Image

5. LearnMore.Show

6. LearnMore.Text

7. LearnMore.Url

8. Messages.ReAuthorize

9. Style.Color

10. Style.Label

11. Style.Shape

12. Title

Configuration Notes:

1. The new CMS component “NavigaPay Paypal Payway V3” must be configured with the required properties and should be included in the Presentation.

2. Select an appropriate presentation -> Page V3 > Step V3 > Payment Methods V3 > NavigaPay PayPal Payway V3 component.

Minimum Circ Version: NCS 2025-2.2

🌐General Enhancements

API

1. Removing validation of Last4 Credit Card Digits

The validation of the last four digits of the credit card has been removed for already authenticated users logging into Self Service.

With this change:

• After entering the correct username and password, an authenticated user can log in to My Account regardless of the credit card format.

• The credit card value is displayed in the UI (where applicable) exactly as it is received in Self Service.

• If the value contains special characters or is not present, a NULL value will be displayed.

• Authenticated users are no longer restricted from logging in due to credit card format validation.

2. Restart Date in Alert Emails to Subscribers

Subscribe now captures the Restart Date returned by NCS for permanently stopped subscriptions and stores it in the Subscription table of the Subscribe database as LastStartDate against the restarting subscription.

The restart date parameter is also available as an email attribute {{subscription.LastStartDate}}, which can be added to email templates. For example, this attribute can be included in the info mail sent to subscribers who restart their previously permanently stopped subscriptions.

3. Account Holder Name in Bank Payments request & Passing it to NCS

A new parameter BankAccountHolderName has been added to APIs, allowing consumer applications to include the account holder name in their bank payment requests. The value of this parameter is stored in the Payment Method table along with other payment details in the database.

Currently, this parameter is used only in the Billing Change API, which passes billing change information to NCS. Other NCS APIs do not yet support this parameter.

CMS & Subscription Panel

1. New property "AccountHolder" in Components

A new property "AccountHolder" has been added to PlaceOrder and Confirmation V3 components in CMS. PaymentInformation.BankAccount.AccountHolder is the property name. The parameter is configurable through subcon config, and it will be non-mandatory on UI.

The account holder’s name can now be included in the Newstart Presentations for NCS if the payment method is Bank Account. The Order Summary page and the final Congratulatory page will display the Account holder name only if the corresponding label is set and the value is captured in the flow.

Configuration Notes:

• Page V3 > Bank Payment component > Account holder property --> On/Off (this behavior exists, not part of this development)

• Page V3 component > Confirmation V3 > Payment Information > Bank Account > "AccountHolder" string value for label in confirmation component

• Page V3 component > Place Order V3 > Payment Information > Bank Account >"AccountHolder" string value for label in Place Order component

Note: The AccountHolder property must first be enabled in Bank Account V3 for it to function effectively in the Place Order and Confirmation components.

Self Service (SubCon Site)

1. New 'Account Hoder Name' field in Bank payment pages

When the payment method is Bank account, a new mandatory field ‘Account Holder Name’ has been introduced on all Bank Payment screens, across all transactions, regardless of whether this information is sent to NCS or not.

• Autopay Signup

• Autopay Manage

• Subscription Update

• One-time Payment

• Add Tip

• Subscription Restart

Configuration Notes:

The new CMS content property "BankAccount.BankAccountHolderNameLabelText" is added for the BankAccountHolderName label text in all pages where the new field is added.

Database

1. Increasing the size of the Database Column

The size of the email ID column has been increased so that the users are now able to successfully link the accounts even when the email Id is as lengthy as 100 characters.

🛠️ Bug Fixes

1. Tip amount not captured in the EZPay signup flow

The tip amount was not being captured in CircPro during Autopay signup flow with both Tip and Donation. This issue has been resolved.

2. Update payment transactions zeroing out Recurring Tip amounts

While placing an update payment method via Self Service on an account that already has a recurring Tip setup, the recurring tip was getting removed for NCS clients. This issue has been resolved. After the fix, while updating the payment method, the already configured recurring tip is not being removed.

3. Issue while signing up to EZPay during upgrading/downgrading susbscription

While signing up to EZPay during upgrading/downgrading a subscription using a Visa card, an error message was received saying, “Credit card type does not match expected credit card type, Visa”. This issue has been resolved. After the fix, the user is able to sign up for EZPay while upgrading/downgrading a subscription using a Visa card without encountering any errors.

4. Issue in the Newstart and Restart flow for CircPro

During Real time Newstart or Restart flow of CircPro, when the subscription was created with EZPay, the EZPay was turned off after the nightly sync. This issue has been resolved. After the fix, Newstarts or Restarts on EZPay is not turned off after the sync process for CircPro clients.

5. Phone number not captured in Newstarts from SP for CircPro

The Phone number was not getting captured in Circpro after creating a Newstart from SP. This issue has been resolved. After the fix, when a Newstart is initiated and submitted from SP, the Phone number in the user details is correctly captured at the CircPro end.

6. Incorrect cardholder name getting captured in Newstarts for CircPro

During Newstarts from SP with ApplePay/GooglePay payment, it was observed that the incorrect cardholder's name (the name entered in the payment iFrame during the newstart purchase flow) was getting captured in the payment-related table. If the name of the user and the cardholder's name were different, instead of the cardholder's name, the user's name in the address details was getting captured. This issue has been resolved. After the fix, during newstarts via SP for CircPro clients, even when the user name and the cardholder name are different, the correct cardholder name is getting captured in the payment-related table.

7. Issues in the Restarts/Newstarts for CircPro clients

It was observed that when a Restart was initiated from SP for CircPro clients, the subscription was being restarted at a previous rate, which was not expected.

These issues have been resolved, and the Restart flow is now working as expected for CircPro clients.

Self Service

Alignment issues on the Benefits section

The Self-Service Benefits section was displayed misaligned to the logged-in users. This issue has been resolved. After the fix, Benefits section boxes and buttons are aligned on the page as expected.

SolCon

Error message while filtering the Offer

Previously, while filtering offers by OfferGroupId in SolCon, an “Index was out of range” error message was displayed. This issue has now been resolved, and users can now filter offers by OfferGroupId on the Offers page without encountering any errors.