August 2026 - Version 6.68
(Release Date: August 11th, 2026)
Table of Contents
📋 At a glance
This month brings the LWC Virtual Terminal to parity with the Aura Virtual Terminal — ACH V2 mandate support, Lite Mode guest checkout, clickable record links, and Experience Cloud community access — and fixes a range of charging, ACH, webhook, and gateway-connection issues, including a new opt-in setting to hold ACH transactions in Pending.
| Update | What it does | For whom | Setup |
|---|---|---|---|
| 💳 LWC Virtual Terminal ACH & parity | ACH V2 mandate disclosure, clickable record links, and Name (Type) gateway display, matching the Aura VT | Admins · Finance | 📦 Payments 6.68 |
| 🌐 Virtual Terminal in Experience Cloud | Authenticated community users can see, create, and pay with payment methods in the LWC VT | Community users | 📦 Payments 6.68 |
| ⚙️ Lite Mode guest checkout | Guest checkout via the LWC VT Screen Flow no longer freezes | Admins · Finance | 📦 Payments 6.68 |
| 🐛 Charging, gateway & webhook fixes | Restricted-profile charge/validation errors, Stripe webhook processing, Spreedly picker, gateway-connection, Flow-toast, and discount-on-donation fixes | Admins · Finance | 📦 Payments 6.68 |
The changes ship in the Payments 6.68 Salesforce package and need to be installed by an admin. Also upgrading Events to 5.59 in the same window? If you use the Blackthorn Candy Shop, Payments upgrades automatically as part of the Events install; if you install manually, upgrade Payments first.
⚠️ Action required
Installing packages manually? Install Payments 6.68 before Events 5.59.
Events 5.59 references the updated Payments dependency, so Payments needs to come first. If you upgrade through the Candy Shop, this is handled for you automatically.
✨ What's new
All items below are part of the Payments 6.68 package and need to be installed by an admin.
💳 Virtual Terminal
ACH V2 mandate support and ACH charging (Salesforce upgrade required)
The LWC Virtual Terminal now shows the required Stripe ACH V2 mandate disclosure and successfully charges ACH payment methods. Switching gateways refreshes the ACH field values so the disclosure always matches the selected gateway.
Clickable record links and gateway display (Salesforce upgrade required)
After a charge, the LWC Virtual Terminal now shows a clickable link to the created Transaction and Payment Method records, and displays gateways in Name (Type) format — bringing it in line with the Aura Virtual Terminal.
Guest checkout in Lite Mode (Salesforce upgrade required)
Guest checkout run through the LWC Virtual Terminal Screen Flow in Lite Mode no longer freezes; the flow now advances after payment as expected.
Virtual Terminal for Experience Cloud community users (Salesforce upgrade required)
Authenticated Experience Cloud community users can now see, create, and pay with payment methods in the LWC Virtual Terminal, matching the Aura Virtual Terminal experience. This is off by default — an admin turns on Allow Community Mode on the Virtual Terminal component in Experience Builder to enable it.
🐛 What's fixed
All items below are part of the Payments 6.68 package and need to be installed by an admin.
💳 Virtual Terminal & payment methods
- Charging on restricted profiles (Salesforce upgrade required): Previously, users on restricted profiles (for example iOS/Android mobile agents) could hit an "Insufficient permissions: inaccessible field" error when charging a transaction. Now they can charge without the error.
- Validating payment methods on restricted profiles (Salesforce upgrade required): Previously, restricted-profile users could hit silent failures when validating or using a payment method, leaving the payment method permanently invalid. Now validation completes correctly.
- Stale ACH mandate text and toasts (Salesforce upgrade required): Previously, the Virtual Terminal could show stale ACH mandate text after changing the related record, payment method, or gateway; mandate dates showed in a non-local format; and creating a payment method showed the transaction header instead of a confirmation. Now the mandate text refreshes, dates show in local format, and creating a payment method shows a "Payment Method Created" toast.
- Error adding a duplicate payment method (Salesforce upgrade required): Previously, adding a payment method that matched an existing one in the Virtual Terminal could fail with a query error when the dedupe path reused the existing record. Now the payment method is added without error.
💳 Charging, gateways & webhooks
- Stripe webhook processing error on customer records (Salesforce upgrade required): Previously, some Stripe customer webhooks failed with a "must not have two identically equal elements" error when the payload carried the same payment method in more than one place. Now the webhook processes cleanly.
- ACH transactions skipping the Pending review window (Salesforce upgrade required · optional per-gateway setting): Previously (since March 1, 2026), an Authorize.Net webhook could flip ACH transactions from Pending to Completed almost immediately instead of holding until settlement, breaking workflows that monitor Pending. You can now keep ACH transactions in Pending until a settlement webhook confirms them by turning on Hold ACH eCheck Pending on Webhook on the Payment Gateway record. This is off by default, so existing behavior is unchanged unless you enable it, and it affects only webhook processing — not direct charges or card transactions.
- Spreedly picker offering gateways that can't authorize (Salesforce upgrade required): Previously, the Create Spreedly Gateway picker allowed sub-gateways that don't support authorization (for example iATS), which then failed at transaction time. Now only capable gateways are selectable.
- New Payment Gateway overwriting an existing Stripe connection (Salesforce upgrade required): Previously, connecting a new Payment Gateway could rebind an existing gateway's Stripe connection to a different account — routing payments to the wrong place. Now each gateway's Stripe connection is preserved.
- Blank success message after a Flow card charge (Salesforce upgrade required): Previously, the Payment Charge Flow success toast could show an empty message body in Summer '26 orgs (it worked in Spring '26). Now the confirmation message displays correctly.
🏷️ Discounts
- Flat-amount discounts reducing donations (Salesforce upgrade required): Previously, a flat-amount discount code could incorrectly reduce a donation contribution. Now the discount lands on the ticket line as intended and donations are untouched.
📄 DocumentLink
- UK date format when the template language is English: Previously, UK DocumentLink recipients could see US-style (mm/dd/yyyy) dates even when the template's Display Language was English. Now recipients see dd/mm/yyyy, matching their regional format. (Released off-cycle ahead of this version; also appears in the Events release notes.)
🛠️ Technical reference
This section is intended for Salesforce admins. Field API names, custom metadata, and implementation notes are grouped by the feature they relate to.
Package fields & layout changes
One new field ships in the Payments 6.68 Salesforce package this release:
Hold_ACH_Pending__c— label "Hold ACH eCheck Pending on Webhook" (Checkbox) on the Payment Gateway (bt_stripe__Payment_Gateway__c) object. Default unchecked. When checked on an Authorize.Net gateway, an incomingnet.authorize.payment.authcapture.createdwebhook for an eCheck (ACH) transaction will not overwrite an existing Pending status — the transaction stays Pending until a settlement webhook confirms the outcome. Affects webhook processing only; no impact on direct charges, card transactions, or other gateway flows. Add the field to your Payment Gateway page layout to expose the toggle; leaving it unchecked preserves current behavior. (AGC-123)
The remaining Virtual Terminal enhancements and fixes are component and processing changes and require no field or permission updates. Community Virtual Terminal access (AGC-199) is controlled by the Allow Community Mode design property on the Virtual Terminal Lightning component, set in Experience Builder — not a package field.
⬆️ How to upgrade
Go to the Blackthorn Candy Shop to upgrade Payments to 6.68. Also upgrading Events to 5.59? If you use the Candy Shop, this is sequenced automatically; if you install packages manually, upgrade Payments first.
For step-by-step instructions, click here.