---
title: "September 2025 - Version 6.48"
slug: "payments-september-2025"
tags: ["Payments", "Release Notes"]
updated: 2025-12-03T22:56:17Z
published: 2025-12-03T22:56:17Z
canonical: "docs.blackthorn.io/payments-september-2025"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blackthorn.io/llms.txt
> Use this file to discover all available pages before exploring further.

# September 2025 - Version 6.48

Please review the updates below and follow the upgrade instructions to upgrade your Payments application.

## Table of Contents

*(Release Date: 10/14/2025)*

- [Bug Fix](/v1/docs/payments-september-2025#bug-fix)
- [Enhancements](/v1/docs/payments-september-2025#enhancements)
- [PayLink](/v1/docs/payments-september-2025#paylink)
- [Field/Layout Updates](/v1/docs/payments-september-2025#fieldlayout-updates)
- [Upgrade Instructions](/v1/docs/payments-september-2025#upgrade-instructions)
- [Important Definitions](/v1/docs/payments-september-2025#important-definitions)

## Bug Fix

- **Line Items:** If an Attendee registers for a waitlisted Session, the related Invoice’s Line Item for the waitlisted Session will have Total = “0.” Previously, the waitlisted Session’s Line Item listed the Total as the actual cost of the Session. (Known Issue: 000004779)

## Enhancements

- **Spreedly:** As part of Salesforce’s security requirements and to better protect your sensitive data, all Spreedly keys, including the Spreedly Payment Gateway access token and the Payment Intent **Client Secret** field must now be encrypted. Starting with version 6.48, customers with existing Spreedly gateways must manually reconnect those gateways in the Dashboard after upgrading.
  - **What does reconnecting mean?** Reconnecting requires you to open each existing Spreedly gateway and click **Create Spreedly Gateway**. This process encrypts your Spreedly key.
  - **What happens if you don’t reconnect after upgrading to a new version?** Until each Spreedly gateway is reconnected, all Transactions routed through that gateway will fail — meaning no payments will process for that gateway.
- **Payment Method:** The Payment Method **Stripe Token** (bt_stripe__Stripe_Token__c) field was deprecated.

### Virtual Terminal

The LWC Virtual Terminal was updated to support CVV and address validation on Authorize.net gateways when the Payment Gateway **Live Validation Mode (Authorize.net)** (bt_stripe__Live_Validation_Mode__c) field is enabled (checked). The validation only works with new and existing Payment Methods with the **Process Type** set to “Authorize Now” or “Capture Now.”

*Important Note: The “Auto-Process” picklist value in the* **Process Type** *field is not supported. Selecting the “Auto-Process” picklist option creates an open transaction that we cannot validate because Blackthorn does not store the tokenized card or the CVV. Please do not use the 'Auto-Process' processing type.*

To support the CVV and address validation, the **Authorize.net Transaction Key** (bt_stripe__Auth_Net_Transaction_Key__c) was added to the Payment Gateway. This field stores the Transaction Key, which is necessary to validate the CVV when charging a credit card.

- Object: Payment Gateway
- Field Label: **Authorize.net Transaction Key**
- API Name = bt_stripe__Auth_Net_Transaction_Key__c
- Data Type = Text
- Help Text = Transaction Key generated in AuthNet Account settings. It will be encrypted after saving for security.
- Description = It stores the AuthNet transaction key necessary for the card code validation.

Click here for more information about how the update works with the different Process Types.

## PayLink

### Enhancement

- Accessibility-related errors occurring on the PayLink landing page and after clicking the **PAY** button on the Payment Details page have been resolved.

## Field/Layout Updates

### New

- Object: Payment Gateway
- Field Label: **Authorize.net Transaction Key**
- API Name = bt_stripe__Auth_Net_Transaction_Key__c
- Data Type = Text
- Help Text = Transaction Key generated in AuthNet Account settings. It will be encrypted after saving for security.
- Description = It stores the AuthNet transaction key necessary for the card code validation.

### Old

- The Payment Method **Stripe Token** (bt_stripe__Stripe_Token__c) field was deprecated.

## Upgrade Instructions

To upgrade Payments to the newest version, go to the [Blackthorn Candy Shop](https://candyshop.blackthorn.io/products).

## Important Definitions

### Breaking Change

A breaking change is a significant change that requires a package upgrade to see the update.

### Off-Cycle or Hotfix Release

A hotfix is a release that corrects a problem that impacted extensive functionality.

**If you have any questions, please don't hesitate to contact [Blackthorn Support](https://community.blackthorn.io/s/support).**