Limio Release Notes – Release 109

Key Features & Improvements

Empower customer with self-service

Finance Self-Service: Brand-new, more powerful, financial self-service with new Saved Payment Methods, new Self-Service Form, improved Invoice Table and new Payment History components.

Seamless integrations

Stripe Payments: Vault cards directly in Stripe and leverage Stripe Elements (iFrame).

Zuora Hot Sync: Sync Zuora customers seamlessly into Limio on log-in.

Zuora Payment Profiles: Capture payment information at the Zuora subscription level.

Actions required:

Please note that there are changes in this release which may require action to be taken:

• Invoices table: If you are using the Invoices Table component, you'll need to check your prop configurations before rebuilding and publishing your pages.

• basketItems: If you are using basketItems via the SDK, you need to replace references to it with orderItems.

• Legacy Salesforce integration: If you are using the legacy Salesforce integration at Settings > Salesforce and you do not have anything populated in the new integration settings at Integrations > Salesforce, please add your credentials to Integrations > Salesforce.

Please remember to perform a hard refresh in your browser after upgrading your environment.

New Features and Improvements

Hot sync customer data from Zuora on customer login

We’ve introduced the Hot Sync, a new capability to automatically bring customer data from Zuora into Limio when customers log in.

Instead of requiring a time-intensive migration, the Hot Sync ensures that Zuora customer account information, subscriptions, and payment methods are pulled into Limio on login. This makes Limio usable as a Finance Portal from day one, even if customer acquisition is not yet managed through Limio.

The Hot Sync is controlled by a new setting in General Settings > Zuora > Zuora Sync Settings > "Do you want to hot sync Zuora data into Limio when customers log in?". When enabled, Zuora data will be synced seamlessly during login. If no Zuora account ID is provided, no sync will occur.

Learn more at Note that enabling commerce actions like Upgrades and Downgrades after a Hot Sync will come in future releases.

We recommend using the new Hot Sync Loader component if you are using the hot sync. This will display a loading message to your customers when the hot sync is in progress. Learn more at .

New Saved Payment Methods Component

Our new Saved Payment Methods component allows customers to view and manage the payment methods associated with their account directly from self-service pages.

Customers can see all saved payment methods, including cards, ACH, BACS, SEPA, PayPal, Apple Pay, and Google Pay. Expiry dates are shown where relevant, with clear labels for cards that are expiring soon or already expired.

The component supports adding new payment methods, setting a default payment method, and deleting existing ones. The default payment method is always synced with Zuora and displayed first in the list.

Learn more at .

New Payment History Component

Our new Payment History component displays all prior payments associated with a customer’s account, showing the date, status, amount, and payment method.

Learn more at

Pay invoices from the Invoices Table component

Customers can now pay open invoices directly from the Invoices table. This is a configurable feature, which means you can allow users to pay their invoice in full, pay a partial amount, or not allow them to pay an invoice at all. When the user wants to pay an invoice, their current default payment method will be used. They can update their default payment method using the Saved Payment Method component (see above).

Along with this new functionality, the component has also been redesigned to improve usability and clarity. Updates include improved layout, styling, table filtering, and handling of empty and error states.

These updates support use cases such as Finance Portal, where B2B customers need the ability to review and pay invoices alongside managing subscriptions and payment methods. Learn more at

⚠️ Note: This enhancement has a breaking change for all customers using the Invoices Table prior to Release 109.

Please follow these steps to avoid any issues with the Invoices Table.

1. Adopt Release 109.

2. On all pages using the Invoices Table component, you will need to check the props for these changes:

   • Heading: The Heading prop has been removed. Please use the Text component instead if you still want your table to have a heading.

   • Invoice date header: The new default value of "Invoice date" will overwrite whatever value you have set in this prop. If you do not want the column name to be "Invoice date", please change this and save the page.

   • Download invoice header: The new default value of "Export" will overwrite whatever value you set in this prop. If you do not want the column name to be "Export", please change this and save the page.

   • Show price: The new default value of "true" will overwrite any false value set in this prop. If you do not want this column to show, please change the value to false and save the page.

3. Rebuild your pages.

4. Republish your pages.

If you do not follow these steps, the new component changes will not appear live until your next build and publish.

New Self-Service Form component

The Self-service Form component allows customers to manage their payment methods directly. It is intended for post purchase account management, for example adding a new payment method, updating contact details, or paying an invoice. It is distinct from the Checkout Form, which is used for acquisition.

Customers can add a new payment method, choose whether it becomes the default, and see new methods stored in a consistent format so they display correctly in the new Saved Payment Methods component. The form accepts extended address fields including phone and email.

The component works with Zuora Hosted Payment Methods and with Stripe Elements for tokenised payments in Zuora.

Learn more at .

Stripe Payments Integration

You can now directly vault your card payment in Stripe and use Stripe's Elements. Card tokens will be passed to the billing system, such as Zuora. You can use Stripe with both the Checkout Form and Self-service Form components.

Learn more at

Support for Zuora Payment Profiles

Limio now supports Zuora Payment Profiles, the replacement for Advanced Payment Methods. With Payment Profiles enabled in Limio, you can assign payment methods at the subscription level instead of the account level, meaning that different subscriptions can have different payment methods. This allows new subscriptions, renewals, and payment method updates to be managed more flexibly—without affecting existing subscriptions on the same account.

The new setting, Enable Zuora Payment Profiles, is now available under General Settings > Zuora in Limio Commerce. Customers can enable this option to prepare for the transition away from APM. Limio will support both APM (until its retirement) and Payment Profiles during the transition period, with full migration to Payment Profiles completed in a future release.

Read more about .

Offers and add-ons with usage-based external pricing

Limio now supports purchasing offers and add-ons which use usage-based, per unit external pricing. This means customers can purchase subscriptions that bill based on actual usage.

In the near future, we’ll be supporting initial pricing with usage, along with other advanced pricing models like volume and tiered pricing.

Read about all the pricing Limio supports here:

New self-service APIs available in the Limio SDK

We have new APIs available in our Limio SDK to complete a variety of self-service use cases:

• Set a default payment method as the default

• Delete a payment method

Read about these APIs here:

Filtering on promo codes

The new search function makes it easy to filter and find your promo codes quickly. Using the search bar at the top of the page, you can select the attribute you want to search by (e.g., discount amount, creation date, etc.) and enter the value to filter the results. This update streamlines the process of locating and managing existing promo codes.

New Header with Floating Cart component

We've released a new header component, with a floating cart that is aligned to our newest Cart components. Use this component if you want a floating basket on your page.

Read more about the component here:

Generate Limio Developer Experience (LDX) credentials in Limio Commerce

We’ve streamlined the onboarding process for custom component repositories. Instead of emailing Limio Support, users can now generate their own Git credentials directly in the Profile > Credentials section of Limio Commerce. From there, you can create or delete repository credentials, view your environment-specific clone link, and follow simple instructions to clone the repository locally. This reduces setup time, removes back-and-forth with Support, and makes it easier to get started with Proofs of Concept and custom development.

Read more about .

Sync billing addresses to Salesforce with Salesforce v3 plugin

The Salesforce v3 plugin now supports syncing billing addresses to Salesforce accounts. This makes it easier to keep customer account records complete and aligned with your billing data.

If you are interested in using this feature, please reach out to so a Limio engineer can configure this for you.

Read more about our , or the .

Customer Acceptance Date set to today

Limio now automatically sets the Customer Acceptance Date to today when processing new orders. This ensures subscriptions activate as expected for customers using Zuora’s Require Customer Acceptance Date setting. This should have no effect if you are not using the Customer Acceptance Date.

Renew without re-entering customer details

Renewals through Modular Checkout are now simpler — customers can renew without re-entering their name and email. Limio will automatically use the details from the original subscription to complete the order.

Read more about .

New “Box” support in Address Fields subcomponent

When using Loqate to autofill an address in the checkout, the Box field will now populate Address Line 2. This is a common element in European addresses (such as Belgium) and this change will help reduce address and delivery errors.

Read more about the .

New fields on Limio address object

The mobile phone, work phone, other phone, and work email fields are now stored on the Limio address object. These fields will be included in all relevant API calls, and in the Zuora sync.

See the Zuora mapping here:

Filter Zuora Hosted Payment Pages (HPMs) by domain when available

Limio has improved the logic for selecting a Zuora Hosted Payment Page (HPM).

Previously, Limio selected the first matching HPM based on country, currency, and auto-renew. This caused issues if multiple HPMs were configured for the same country/currency but on different hosted domains.

With this update, Limio now also considers the hosted domain when selecting the HPM.

• If the hosted domain matches the checkout domain, Limio will select the corresponding HPM.

• If no hosted domain is configured, Limio will fall back to the existing logic (country + currency + auto-renew).

This change is backward compatible. No action is required unless you want to enforce host-domain matching.

Read more about configuring

New setting to control whether default payment method pays off existing open invoices

You can now choose whether newly added default payment methods automatically pay outstanding invoices in Zuora. If Limio Settings > Zuora > Zuora Orders Settings > Disable auto pay for payment method updates is true, then outstanding invoices will not be paid automatically when a new default payment method is added. By default, the value is false, which means outstanding invoices will still be paid automatically.

German Localisation Introduced additional German translations across Limio components to improve localisation support.

Refactors and cleanup

Removed basketItems

⚠️ Note: This refactor has a breaking change for all customers using basketItems in the SDK

Please follow these steps to avoid any issues:

• References to basketItems should be replaced with orderItems. The underlying data is the same.

Read our updated SDK documentation here:

Removed legacy Salesforce Integration settings

We have removed the legacy Salesforce Integration settings by removing the General Settings > Salesforce tab entirely. The Integrations > Salesforce settings should be used instead.

⚠️ Note: This refactor has a breaking change for all customers using Salesforce who do not have the Integrations > Salesforce settings set

Please follow these steps to avoid any issues:

• Go to Limio Settings > Integrations

• Add a new integration of type Salesforce

Full instructions here:

Payment Methods object refactor

The way payment method objects are stored in Limio has been refactored for consistency. There should be no immediate impact to customers using payment methods in the old format, however some of the new components like the Saved Payment Method component may not work properly without a migration of data.

Please reach out to if you'd like to migrate your customers' saved payment methods to the new format.

Styling update

We’ve updated the way Limio styles are applied to prevent conflicts with third-party components (e.g., iFrames or scripts). Popovers and core checkout components will continue to look the same, but styling is now more safely scoped to avoid unintended side effects.

We recommend that you check your custom components are appearing as expected after this change.

Bug Fixes

Journeys v2 issues

Several inconsistencies in the Journeys v2 API have been corrected so that responses now align with expected behaviour and documentation.

See our Journeys v2 documentation here:

We've also fixed a bug where the journey page would error if there were no journeys configured.

Improved Order Complete Details component

We've improved the Order Complete Details component to display the order number, to work in a renewal order, and to have more consistent layouts.

Incorrect currency formatting

Some components displayed currency in the wrong format. Formatting has been corrected to display consistent values. Now, all components will display price according to the currency of the offer or subscription, and the limio_country cookie, according to .

Incorrect country capture

During checkout, the country was not being captured correctly from the viewer country. This issue has been fixed to ensure the correct viewer country is stored.

Evergreen-to-termed switch error

Customers were unable to switch from an evergreen subscription to a termed subscription, receiving an error message that should not have applied. This has been fixed so that evergreen subscriptions can now be switched to termed offers without error, and switch behaviour is consistent across subscription types.

Form feedback not displayed (#110716)

Checkbox and radio button feedback in SPC forms was not displayed. This regression has been fixed and form feedback now appears correctly.

Gift Codes search (#110236)

Searching for gift codes previously failed, showing continuous loading or no results. The gift codes index has now been added so searches return results as expected.

Remove ability to edit code (#110922)

We’ve simplified how code is managed in Limio by removing the ability to edit code directly in the preview asset section. Instead, code changes should now be made through supported features such as custom components or by uploading code assets.

This affects areas such as:

• Settings > Shop > Robots.txt – you can still upload a robots.txt file, but it can no longer be edited in-line.

• Code Assets – you can upload or re-upload assets, but not edit them directly.

This update ensures a more consistent and maintainable approach to managing code, while encouraging best practices through custom components and asset uploads.

Currency resets to N/A when changing from initial to external pricing

Previously, the currency would would reset to N/A if the user toggled on the "Use external pricing?" toggle in the Offer price editor, but the currency wouldn't be updated to N/A in the UI which made the missing currency hard to debug. Now, if you turn on "Use external pricing?", the currency persists.

Limio Commerce MFA blocking LFS authenticating

Previously, there was an issue where if MFA was enabled in a Limio Commerce environment, LFS wouldn't be able to connect to the Limio APIs properly using Named Credentials. This bug has been resolved so that MFA does not block this connection.

LFS not loading all subscriptions when there are many on one account

We've improved the getIdentitySubscriptions API so that LFS accounts with many subscriptions load all subscriptions. If you would like to adopt this bug fix, you'll need to be on LFS Release 13.32 or higher.

Issues with calculation in Cart Summary component

We've fixed 2 issues with the Cart Summary component:

1. If a specific-offer promo code is applied in the cart, the subtotal was displaying the amount without the discount. This has been corrected to show the amount with the discount (since the discounts are displayed in-line in the Cart Items component).

2. The percentage in the tax line item was displaying the incorrect value. This has been corrected so it pulls straight from Zuora.