---
title: v2.38.0 (Spring '26)
slug: payments/v2380-spring-26
createdAt: 2025-12-01T18:38:52.875Z
---

This release focuses on improving our core features.

:::CtaButton{label="Install v2.38.0 (Spring '26) Package" externalHref="https://login.salesforce.com/packagingSetupUI/ipLanding.app?apvId=04tJ70000004oC0IAI" openInNewTab="true"}

:::

::::hint{type="danger"}
:::ExpandableHeading
**Important notice on guest user access to Unaric Payments**

We’re aware that some clients have been using Guest Users with our package. Guest Users have never been an officially supported use case and whilst certain functionality may have worked previously, this is not guaranteed going forward.

With the Summer 25 release and onwards, our security controls in line with Salesforce best practices may affect existing Guest User configurations. We advise clients to carefully check before upgrading any integration with us which uses Guest Users. Our recommended approach is to use Experience Cloud (community) user licences, which are fully supported, secure, and compatible with protected package components.

Contact support at [support@unaric.com](mailto\:payment-support@unaric.com) if you have any questions or concerns.
:::
::::

## New feature: Level 2 & level 3 data processing for recurring payments (Stripe Connect)

Introduced in the Winter 26 release, level 2 and level 3 (L2/L3) data processing via **Stripe Connect **now includes recurring payments, enabling sending enriched transaction data to Stripe and potentially qualify for reduced interchange fees. This feature is particularly beneficial for US-based organisations, where L2/L3 data directly impacts processing costs.

With this change, you can now include line-level information such as:

- **Product name**
- **Product code**
- **Tax amounts**
- **Unit cost**
- **Quantity**
- **Unit of measure**

### How it works

- *If **Payment Line Items** exist*, level 2 / level 3 data is sent to** Stripe**.
- *If no line items exist*, payment is processed as level 1 only.

:::hint{type="info"}
No system error is generated when line items are missing.
:::

### What’s included

:::hint{type="success"}
- New object: **Payment Line Item** (child of **Payment**).
- Support for L2/L3 data on single and recurring payments.
- New packaged permission set for line-level data.

::Image[]{src="https://api.archbee.com/api/optimize/10Nod6Ww95R3dPr0k0TCJ/TX5wgs2YZXRqwYVESZfoh_image.png" size="66" width="983" height="768" position="center" caption=""Payment Line Item" is a child object of "Payment". Existing customers are unaffected by this new object." darkWidth="983" darkHeight="768" showCaption="true"}
:::

### What’s not included

:::hint{type="warning"}
No Certinia connector changes are included. The Certinia connector does **not** create Payment Line Items automatically. As such, clients must populate** Payment Line Items** via Flow or custom automation.
:::

### Important notes

- This is a **premium feature** and requires enabling with your CSM before use.
- Only available via **Stripe Connect** for **card payments.**
- Clients should work directly with Stripe to confirm:
  - Which data is being received.
  - How their transactions are classified.
  - What discounts may apply.
- Stripe does not clearly display the value of L2/L3 data inside the dashboard, so coordination with Stripe is essential.

### Prerequisites

- Speak to your CSM about enabling L2/L3 data access. 

## New feature: Payout references for Stripe Connect card payments

This feature allows ease of reconciliation between Stripe payments and Unaric payments within Salesforce. Each time a Payout is sent from Stripe to your bank account, a reference will be populated on the Payment record within Salesforce.

To use this feature, ensure that the Payout Reference field is added to your page layout and this will be populated automatically if you are using Stripe Connect for either Card or Bank payments.

## New feature: Expanded Stripe bank payments

Winter 26 expands bank payment support via **Stripe**, using **Stripe Hosted Checkout Elements**.

### Now supported

:::hint{type="success"}
- ACH – United States
- PAD – Canada
- Payout processing for bank payments
:::

### Important differences

- Requires **customer email address** for Stripe session creation.
- Styling is partially controlled by Stripe (not fully customisable).
- The experience is functionally the same but **visually different** from the existing pay page.
- All outcomes, errors, and statuses flow back to Salesforce as normal.

Customers must configure some options within their **Stripe Dashboard**.