---
title: "September 2026 - Version 6.69"
slug: "payments-september-2026"
updated: 2026-09-01T13:36:09Z
published: 2026-09-01T13:36:09Z
canonical: "docs.blackthorn.io/payments-september-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.

# September 2026 - Version 6.69

# September 2026 - Version 6.69

## September 2026 - Version 6.69

*(Release Date: September 1st)*

## Table of Contents

- [At a glance](/v1/docs/payments-september-2026#at-a-glance)
- [Action required](/v1/docs/payments-september-2026#action-required)
- [What's new](/v1/docs/payments-september-2026#whats-new)
- [What's fixed](/v1/docs/payments-september-2026#whats-fixed)
- [Technical reference](/v1/docs/payments-september-2026#technical-reference)
- [How to upgrade](/v1/docs/payments-september-2026#how-to-upgrade)

## 📋 At a glance

A focused release on the Stripe path. Saved payment methods now become reusable when a payment succeeds and the method was set up for future use, instead of being locked to One-Time forever, and Stripe Link is now a recognized payment method type rather than an unlabeled one. Both arrive with the package, with nothing to switch on.

| Update | What it does | For whom | Setup |
| --- | --- | --- | --- |
| 💳 Stripe Link recognized as reusable | Link payment methods are treated as reusable rather than one-time use, and **Link** is now a value on Payment Method Type | Anyone taking Stripe payments | 📦 Payments 6.69 |
| 🔁 Saved methods promoted to Valid | A saved payment method of any type moves from One-Time to Valid when a payment succeeds and the method was set up for future use | Anyone taking Stripe payments | 📦 Payments 6.69 |
| 📄 Full invoice text in DocumentLink PDFs | Long text in Document fields 1 and 2 is no longer cut off in the downloaded invoice PDF | DocumentLink users | Automatic |

---

## ⚠️ Action required

**Do you have reports, list views, or automation that treat One-Time payment methods as permanently one-time? Check them before you upgrade.** Previously, a payment method that was not a card was locked to **One-Time** status and stayed there, so it was safe to treat One-Time as a terminal state. That is no longer true. When a payment succeeds and Stripe was told to save the method for future use, the matching Payment Method record is promoted from One-Time to **Valid**.

This is wider than Stripe Link, which is what the change was raised for. It applies to a saved payment method of any type. If you count One-Time records, filter on them, or branch automation on them, those numbers and branches will change without anyone editing a record.

**A new `link` value appears on the Payment Method Type field.** It is additive, so Salesforce delivers it on upgrade with no Update Picklists step and nothing is removed or renamed. But if you have automation that enumerates the values of Payment Method Type, or a validation rule or report filter written as a closed list, it will now encounter a value it has never seen. Check anything that treats that field as a fixed set.

There is a second, quieter part to the same fix: the Type field is no longer overwritten unconditionally. It is now written only when the incoming value is non-blank, so a Type that was previously being blanked out on update stays set.

---

## ✨ What's new

### 💳 Payment methods

#### Stripe Link is recognized and treated as reusable

Stripe Link payment methods were previously treated as one-time use, so a registrant who paid with Link could not have that method reused, and the method carried no recognizable type. Link is now a value on **Payment Method Type**, and Link methods are treated as reusable.

#### Saved payment methods are promoted when a payment succeeds

More broadly, a saved payment method of any type is now promoted from **One-Time** to **Valid** when a payment succeeds and the method was set up for future use. See **Action required** if you have reporting or automation keyed on One-Time status.

---

## 🐛 What's fixed

### 📄 DocumentLink

- **Invoice PDF content was cut off**: Previously, a large amount of text in Document fields 1 and 2 was truncated in the downloaded invoice PDF, so recipients received an invoice missing content that was present in Salesforce. Now the full content renders. *(Arrives automatically; no package upgrade needed for this one.)*

> Known Issue reference numbers for this release are being finalized with Support and will be added on publish.

---

## 🛠️ Technical reference

*This section is intended for Salesforce admins.*

****Payment Method Type: one new picklist value****

- **Payment Method · Type** (`bt_stripe__Payment_Method__c.bt_stripe__Type__c`), Picklist. New value `link`, label **Link**. Additive, delivered on upgrade with no Update Picklists step.

****Where the promotion happens****

The One-Time to Valid promotion is in `PaymentMethodStripe.upsertRecordSpecific()`, which now writes `Type__c` only when the incoming value is non-blank rather than overwriting it unconditionally.

****No other metadata changed****

No field was added or removed, and no permission set, page layout, validation rule, or Flow changed in the Payments package this release. Verified against the net `release/v2026-08` to `release/v2026-09` diff.

---

## ⬆️ How to upgrade

Go to the [Blackthorn Candy Shop](https://candyshop.blackthorn.io/products) to upgrade Payments to 6.69.

If you also run Blackthorn Events, note that Events 5.61 requires Payments 6.59 or later, so upgrading Payments to 6.69 satisfies that on its own. See the Events release notes for what is in 5.61.

For step-by-step instructions, click [here](https://docs.blackthorn.io/docs/blackthorn-payments-installation).

The DocumentLink fix arrives automatically and needs nothing from you to install.