The September ’26 release goes into production on 20 September and has been available in sandbox environments since 23 August.
You can watch the September ’26 release webinar for a walkthrough of the main updates, or head straight to the September ’26 release notes for the full technical detail.
September brings several important steps forward for payments in Salesforce, from more flexible payment experiences and bank-validated Direct Debit mandates to new ways to give and pay and simpler payment operations.
At a glance
- More flexible Payment Experiences, with new checkout and fundraising templates plus expanded localisation support.
- Bank-validated e-Mandates in the Netherlands, giving organisations stronger proof behind SEPA Direct Debit collections.
- More ways to give and pay, with Vipps MobilePay Donations and gift cards through Adyen.
- Simpler payment operations, with more incoming payment data available directly to Guided Matching.
Here are the four highlights worth knowing:
1. Build a payment experience to fit the moment
Different payment moments call for different experiences.
Someone making a donation has different needs from someone paying an invoice or joining a membership organisation. And organisations operating across markets need payment experiences that work across different languages and currencies.
For this release, we continued to build out the open-source templates and examples behind FinDock Payment Experiences, which remains in pilot.
We have added a new single-page checkout template for simpler payment journeys such as memberships, invoices, ticketing and products. We have also expanded localisation support, making it easier to create payment experiences that adapt to the languages, currencies and formatting your customers would be familiar with, using your Salesforce org’s own localisation capabilities.
For fundraising teams, there are also new UK donation templates with Gift Aid steps already configured and fee coverage included.
You can start with a ready-made experience, adapt one of our templates to your needs, or build something much more customised while keeping FinDock underneath it to handle the payment.
Why does this matter?
That means you can change the payment experience your customer sees without having to reinvent the payment engine behind it.
Because the front end of a payment journey should fit the customer and the use case, while keeping the payment data connected to the same customer record in Salesforce
Explore the Payment Experiences templates on FinDock Labs
2. Bank-validated e-Mandates for Direct Debit in the Netherlands
An e-Mandate is a digital Direct Debit mandate that a customer authorises through their bank.
Instead of simply entering an IBAN and giving consent online, the customer chooses their bank, authenticates in their banking environment and approves the mandate there. The bank validates the mandate, and FinDock brings the mandate and its proof back into Salesforce alongside the customer and the recurring payment it authorises.
This matters because collecting a SEPA Direct Debit online does not automatically mean you have a mandate you can prove.
If a customer later says they never authorised the Direct Debit, an organisation may need to show that a valid mandate was actually given. Without that proof, a collection can potentially be challenged as unauthorised for up to 13 months.
With e-Mandates via Incassomachtigen, the mandate is validated through the payer’s bank. The normal eight-week SEPA Direct Debit refund right still applies, but the organisation has bank-validated proof of the mandate behind the collection.
Why does this matter?
For organisations collecting recurring payments by Direct Debit, it creates greater certainty around the permission behind every collection.
And because FinDock connects the mandate, its proof and the recurring payment in Salesforce, the mandate does not sit in a separate system away from the customer and their payment history.
View the demo in our September Release webinar. e-Mandates via Incassomachtigen is currently available in pilot in the Netherlands as a FinDock add-on. Speak to our Customer Success team if you would like to strengthen your Direct Debit mandate process.
3. More ways to give and more ways to pay
This release also introduces two new payment options, each opening up a different way for people to give or pay.
Vipps MobilePay Donations
For organisations fundraising in Norway, FinDock now supports Vipps MobilePay Donations.
Donors can set up their donation through the Vipps MobilePay experience, while the resulting payment information flows back into Salesforce. FinDock can then use Guided Matching to connect that activity with the donor and the rest of their payment history.
The result is a familiar local giving experience for the donor without creating a separate source of payment data for the organisation.
Gift cards through Adyen
We have also added gift cards to our Adyen integration for one-time payments.
That gives organisations another way for people to contribute towards a payment. Depending on the journey, that could mean using the balance of a gift card towards a membership, ticket, product or even donations.
And the gift card does not need to cover the full amount. If someone wants to make a €40 payment but only has €36 remaining on their gift card, they can use the gift card first and pay the remaining €4 with another supported payment method without leaving checkout.
That turns unused gift card value into something people can actually put towards a purchase or contribution, while giving organisations another opportunity to capture revenue that might otherwise have been left unused.
Why does this matter?
More ways to pay can also mean more opportunities to convert.
By letting people use the value they already have available to them and top up the difference when needed, organisations can remove another barrier between someone wanting to pay and completing that payment.
4. Guided Matching: simplifying the other side of the coin
Accepting a payment is only one side of the story. The other is everything that needs to happen after the money starts moving.
Payment providers send a lot of useful information with their notifications, and that data often plays an important role in matching a payment to the right customer, account or transaction. Until now, using a specific piece of that information in Guided Matching could require additional steps or custom work first.
With the September release, Guided Matching can work directly with more of the data already arriving from your payment providers.
That means teams can use that information to find the right account, update the right record or identify a duplicate without first having to build another layer just to make the data usable.
Why does this matter?
Because payment operations get harder as payment volumes, methods and providers grow.
Making more of the incoming payment data directly usable in Salesforce means more of the reconciliation process can be automated, while teams spend their time on the exceptions that actually need attention.
And there’s more
These are the highlights, not the full release.
September also includes improvements across refunds, payment processing, Salesforce Fundraising, existing payment integrations and the day-to-day administration of FinDock.
For the complete list of changes, configuration details and technical documentation, read the September ’26 release notes.
And if you want to see the major changes in action, watch the September ’26 release webinar.