---
title: v2.40.0 (Autumn '26)
slug: payments/v2400-autumn-26
docTags: 
createdAt: 2026-10-12T18:57:13.663Z
---

This release focuses on partnership options, specifically with Stripe and Elavon. This includes new supported payment options, phase 1 of the Stripe Optimized Checkout Suite (OCS), alongside card webhooks for dispute handling and necessary Salesforce package updates.

:::CtaButton{label="Install v2.40.0 (Autumn '26) LinkPending" openInNewTab="true"}

:::

## New feature: Stripe OCS (Phase 1)

The Stripe Optimized Checkout Suite (OCS) provides a new look and feel to paypages, as well as support for payments, authorisations and associated refunds, Apple/Google Pay, OneLink, and support for Stripe-only clients.

### Setup

OCS has to be enabled manually and uses standard Stripe Connect credentials.

### What is included

- New paypage look and feel 
- Support for Payments, Payments + Authorisations, Authorisations (& associated Refund processing against those transactions) 
- Apple/Google Pay 
- Stripe Only Clients (no mixed PSP clients yet) 
- OneLink 

:::hint{type="info"}
OneLink will enable automatically as long as it is enabled in your account and does not require additional setup.
:::

###  What is not included 

- Adaptive Pricing 
- Mixed PSP Clients 
- Canadian PAD/ACSS as that's not supported by Stripe yet in Elements (it will continue to use the existing flow outside of OCS until it is) 
- Dark Mode for paypage 
- Not available for Gross Settlement clients 
- MOTO card payments still use the existing Stripe Connect page, not the new paypage. Hence, MOTO clients will need both connections.
- MOTO bank payments 

### Upcoming: Stripe OCS (Phase 2)

A phase 2 release, with multi-PSP support, adaptive pricing, dark mode, PayPal, and MOTO improvements, is currently under development and will feature in following releases.

## Stripe Cards webhooks

Stripe card webhooks provide real-time updates for late card failures and dispute handling, addressing situations where a customer successfully makes a payment and later disputes it. Unlike standard card notifications that only confirm immediate success or failure, these webhooks automatically update Salesforce with new statuses: *Disputed* and* Dispute Lost*.

When a dispute status changes, it is tracked in the Unaric Payment History through updates to both the **Payment Stage** and **Payment Stage Description** fields.

- **Payment Stage:** Updates to reflect the current status, such as *Disputed* when a dispute is opened or *Collected from customer* when resolved.
- **Payment Stage Description:** Provides detailed updates on the dispute lifecycle, showing descriptions such as *Dispute created. Evidence submission due by \[date],* *Dispute fund locked*, *Dispute updated, Evidence submitted*, and *Dispute won*.

:::hint{type="warning"}
This feature depends on a package release. The new Payment Stage picklist values (*Disputed* and *Dispute Lost*) come with Unaric Payments v2.40.

If you're on a version earlier than v2.40, you'll still get detailed dispute updates in the Payment Stage Description. However, the Payment Stage can't change to *Disputed* or *Dispute Lost* until you upgrade, so the description will show the dispute while the stage stays the same.
:::

### Setup

You will need to add *Disputed *and *Dispute Lost *picklist values to the **Payment **object:

1. In Salesforce, navigate to **Setup > Objects and Fields > Object Manager**.
2. Find the **Unaric Payment** object (or **Asperato Payment**, API name `asp04__Payment__c`) and click **Edit**.
3. On the left menu, select **Fields & Relationships**.
4. Open **Payment Stage** (API name `asp04__Payment_Stage__c`).
5. Scroll down to the **Values** section and click **New**.
6. Enter `Disputed` and `Dispute Lost` on separate lines in the text box.
7. Click **Save**.

### Add path (optional)

You can add the new stages to the progress bar at the top of Payments records page:

1. In **Setup**, navigate to **User Interface > Path Settings.**
2. Click **New Path** (or **Edit** an existing one).
3. Set the Object to **Unaric Payment** (asp04\_\_Payment\_\_c), select your **Record Type**, and set the picklist field to **Payment Stage** (asp04\_\_Payment\_Stage\_\_c).
4. Select the* Disputed* or* Dispute Lost* stage in the preview bar, then add high-priority fields (e.g., **Amount**, **PSP Reference**) and brief instructions for your finance team.
5. Toggle the Path to **Active**.
6. Navigate to any Payment record, click the **Gear** icon** (⚙️) **and** Edit Page**.
7. Drag the **Path** component onto your page layout and save.

## Elavon EPG (Elavon payment gateway) integration

This new integration supports payments, authorisations, refunds, card webhooks, and digital wallets like Apple Pay and Google Pay. For this integration, it is required the Elavon Salesforce package, which is an Elavon-branded version of the Unaric Payments package that operates using a direct connection to Elavon EPG.