---
title: "January 2026 - Version 6.52"
slug: "payments-january-2026"
tags: ["Payments", "Release Notes"]
updated: 2026-02-12T14:18:58Z
published: 2026-02-12T14:18:58Z
canonical: "docs.blackthorn.io/payments-january-2026"
---

> ## 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.

# January 2026 - Version 6.52

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

## Table of Contents

*(Release Date: January 27, 2026)*

- [Bug Fixes](/v1/docs/payments-december-2025#bug-fixes)
- [Enhancements](/v1/docs/payments-december-2025#enhancements)
- [Upgrade Instructions](/v1/docs/payments-december-2025#upgrade-instructions)
- [Important Definitions](/v1/docs/payments-december-2025#important-definitions)

## Bug Fixes

- **Refunds:** If a user initiates a refund for a payment Transaction from Stripe, the resulting refund Transaction in Salesforce will include a value from Stripe in the **Transaction ID** field. Previously, the Transaction’s **Transaction ID** field was blank.
- **Line Items:** From an Invoice, a user can change the value in a Line Item’s **Discount Code** field without causing an error or deleting the Line Item record. (Known Issue: 000003287)
- **Permissions:** Users can complete a payment without Read access to the Transaction’s (custom) parent object and/or fields when accepting a payment by entering a valid card or bank account number on the Mobile Payments app, or accepting a payment by entering a valid Payment Method on the Transaction record and clicking **Charge**. A new validation was implemented to prevent permission errors related to Transaction parent fields when a user with insufficient field access tries to accept a payment via the Mobile Payments app. Previously, users received insufficient object and field access permission errors when trying to accept a payment via the Mobile Payments app. (Known Issue: 000005099)

### Virtual Terminal

- After a user configures the Virtual Terminal mapping to use the Source Parent Object and Source Parent Field, the Virtual Terminal will retrieve Parent field values and populate target fields as expected, regardless of which Virtual Terminal is used – the old version or the LWC Virtual Terminal. Previously, the LWC Virtual Terminal would not load, and the old Virtual Terminal would load but not apply mappings properly or load the Payment Method. (000005029)
- The **Show Address** field on the Blackthorn Payments | Virtual Terminal’s Custom Settings is enabled. If a user tries to create a new Payment Method to process a single-charge Transaction using the Aura Virtual Terminal component, they will see the **Add+** and **Reset** buttons on the new Payment Method screen. Previously, the buttons were no longer visible because Salesforce updated its rendering of iframed components.

## Enhancements

### LWC Virtual Terminal and Flows

The user experience of submitting a payment with the BT Payments LWC Virtual Terminal in a flow has been reconfigured to create a more straightforward experience. Previously, the placement of the **Process** button led users to miss clicking it or to click it multiple times, resulting in duplicate payments.

Now, when submitting a payment using the BT Payments LWC Virtual Terminal in a flow, the following will occur:

- If the **Hide Transaction Button** setting in the Virtual Terminal flow component is set to “True,” the **Process** button won’t be visible, and clicking the **Next/Finish** button will trigger the Transaction to be processed.
- If a payment attempt fails, the user will see an error message and a retry option.
- If a payment is successfully processed, the flow automatically advances the user to the next step.
- Duplicate Transactions will not be created.

## 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).**