FinDock’s May ’26 release is now live in production orgs as of Sunday, May 17. You can watch the May release webinar for a walkthrough and demos, or review the release notes for the complete list of changes.
If you’re short on time, here are the release highlights:
- Refunds from Salesforce, expanded to Stripe and Authorize.net, with a new out-of-the-box component (beta)
- Salesforce Bulk API 2.0 moves to General Availability
- Reconciliation improvements, more control over matching and payment references
Also announced:
- Experience Cloud payments, allowing you to build more flexible online payment experiences inside Salesforce. Pilot sign-ups are now open.
Refunds from Salesforce: now in beta, now on Stripe and Authorize.net
Refunds from Salesforce started as a pilot in January with Paya. With the May release, the feature moves to beta and expands to two of the most widely used payment processors: Stripe and Authorize.net.
This release also introduces a new out-of-the-box web component for refunds. Service agents can initiate full or partial refunds directly from an Installment, Opportunity, or Gift Transaction record. The component shows relevant payment history, flags any prior refunds, and surfaces customizable refund reasons, so agents have the context they need without the need to switch between tools.
For teams that want more flexibility, refunds can still be triggered from a Flow or built into a custom component. Documentation with code examples is available in the FinDock Knowledge Base under Integrating Refunds.
Why does this matter?
Issuing a refund should not require having to leave Salesforce, logging into a processor dashboard, and manually updating records on the way back. When a refund is processed through FinDock, the refund record is created and linked to the original payment automatically. Status updates from the processor flow back in through Guided Matching, this means that finance teams see the full and accurate picture without having to chase down more information.
For teams using Fundraising (NPC), FinDock also creates a Gift Refund record linked to the original gift transaction, keeping fundraising data and payment data in sync.
If you want to test Refunds from Salesforce, contact FinDock Support to get started.
Salesforce Bulk API 2.0 moves to General Availability
Bulk API 2.0 has been in pilot since the March release. It moves to General Availability with the May release, improving how ProcessingHub exchanges data with Salesforce for large volumes of records.
All sandbox orgs receive Bulk API 2.0 now. For production orgs, FinDock is using a phased rollout over the coming weeks. This rollout is not tied to the standard release cycle, so your production org will be switched over separately. Customers will receive advance notice via email, please ensure that the Support & Product Contact email address in FinDock Setup is up to date.
Why does this matter?
For teams processing large volumes of payment data, this reduces the time ProcessingHub spends pushing data to Salesforce. Internal testing showed up to 60% faster data loads for bank statement files and a 28% improvement for Gift Aid processing.
For most teams this change is invisible, as it happens in the background. But if you run high-volume operations, you should experience faster processing windows.
Experience Cloud for online payments: now accepting pilot customers
FinDock is opening sign-ups for online payments built on Salesforce Experience Cloud, Flow, and FinDock web components, all combined into a single, configurable solution that runs inside Salesforce.
The approach is built around three parts that can be mixed and matched:
- Experience Cloud as a website and page builder – responsive, brandable, with a free Salesforce CMS included
- Flow as a form builder – flexible multi-step journeys with conditional logic, validation, and no-code configuration
- FinDock web components for payment method selection, payment initiation, and response handling
Templates are available via FinDock Labs so you can start from a working example and adjust from there.
Why does this matter?
Until now, online payment experiences in FinDock were either out-of-the-box Giving Pages and PayLinks, quick to set up but limited in flexibility, or fully custom builds on top of the Payment API, which require more development-intensive resources. This pilot is designed to fill the gap, giving you more flexibility than Giving Pages, but without the cost and complexity of building from scratch.
It also means payment pages live inside Salesforce, so they can connect directly to Agentforce, Marketing Cloud, Data Cloud, and the rest of the Salesforce ecosystem. Localization, accessibility, and branding can now be handled through Experience Cloud’s native tooling.
The pilot is open for sign-up. If you want to participate, contact laurens@findock.com or support@findock.com, or fill in the form at https://forms.gle/vwcnuyrtyXNkY9mZ6.
Reconciliation improvements: serial processing and custom payment references
Two updates in this release give teams more control over how transactions are matched and how payment references are generated.
More control over how transactions are matched. When Guided Matching processes incoming transactions, it has always run multiple matches at the same time, processing in parallel to get through large volumes quickly. That works well, but in some cases it can cause conflicts, where two transactions compete to match against the same record simultaneously.
You can now choose to process transactions one at a time instead. For most organisations, this is just as fast, and it removes the risk of those conflicts, particularly useful when matching rules are complex or when the order in which transactions are processed matters.
New installs default to one-at-a-time processing. Existing installs stay as they are, with the option to change it in the Guided Matching setup.
Why does this matter?
The processing mode change improves matching reliability for organisations with complex transaction flows, particularly relevant for teams reconciling large bank statement files or working with bank transfer payments that require exact reference matching.
The custom base reference makes it easier to link incoming payments to internal records like invoices, without having to build your own reference logic from scratch.
For a complete overview of all changes in the May 2026 release, review the full release notes at docs.findock.com/release-notes/release-notes-may-26 or watch the release webinar