A fundraising campaign works hard to get someone to give online. But a supporter fired up by a specific appeal clicks donate and lands on a generic form: no mention of the campaign, no sense of the goal, the same amounts as everything else. That drop in momentum is where some of them leave before they finish. A page built for the campaign keeps more of them going through to a completed gift. A year-end appeal, an emergency response, a major-donor ask: each one deserves its own donation page, with its own amounts, wording and look. Your general donation page is critical, but it can’t do justice to every campaign at once. 

So the practical question is how to give each campaign its own donation page in a way that’s manageable for your team.

This use case covers building donation pages on Salesforce, using Experience Cloud, Salesforce Flow and FinDock’s payment components, starting from FinDock Labs’ donation templates. Your team builds and adjusts the page in Salesforce’s Experience Cloud  drag-and-drop tools, and FinDock’s components handle the payment itself.

FinDock Payment Experiences for fundraising

FinDock Payment Experiences lets your team build the donation page itself, using Experience Cloud, already included in your Salesforce edition. Instead of a generic donation form, the donation page can be built for the specific campaign: the right message, the right goal, the right amounts. And because the page and your donor data sit on the same platform, a gift lands on the donor record the moment it’s made, with nothing to sync afterwards.

It brings together three things: Experience Cloud to build and brand the page, Salesforce Flow to build the form and its logic, and FinDock’s payment components to take the payment. FinDock Labs provides ready-made templates, so you start from a working donation page rather than a blank screen.

What you can do with FinDock’s donation templates

• Collect a one-time or recurring gift, with amounts and frequencies your team sets.
• Let a donor give in honour or memory of someone, using Gift Tributes.
• Let a donor cover the transaction fee, so the full gift reaches the cause.
• Reuse the same template for the next campaign, with its own amounts, frequencies and branding.

You set all of this up in Salesforce Flow and the Experience Cloud page builder. If you’ve ever built a page in a website builder like WordPress, or a drag-and-drop one like Squarespace, the builder will feel familiar. You lay out a page by adding or dragging components onto a web page, and it handles desktop and mobile layouts for you. Typography, brand colours and header images are set once from a single menu and apply across the whole site. And you control the page structure yourself: navigation, custom URLs, and how pages show up in search with metadata. The result is a donation page that looks like the rest of your organisation’s site, on your own brand, not a generic hosted page you can’t change.

Launch a new campaign page faster

The donation site and flow are templates from FinDock Labs, so a new page doesn’t mean you have to start from a scratch. You deploy the template into your Salesforce org and you have a working donation page and flow, already connected to FinDock’s payment components. From there, setting the amounts, frequencies and branding for a specific campaign can be a no-code job in Flow and the Experience Cloud builder.

Because you start from a working template, getting a page live for a new campaign is quicker, and the amounts, wording and branding are things your team can change themselves in the builder. You’d only bring in a developer for something more custom, like a custom-designed component, or logic beyond what Flow can handle on its own.

The gift lands straight in Salesforce

Webpages and sites built with Experience Cloud and FinDock run natively in Salesforce, so a gift is written directly to the same place your campaigns, funds and donor records already live. There’s no separate donation platform to sync from, and no second copy of the data to keep up to date.

Extending beyond the template

The templates are only the starting point. Adding elements like a progress bar toward a goal, changing the site layout, or adding a screen to the flow is done in the Experience Cloud builder and Flow. If you need something the standard components don’t cover, developers can build their own Lightning Web Components using FinDock’s payment components, or add custom CSS, so the custom part stays manageable rather than a rebuild of the payment logic. And if you want to go further still and build a fully custom payment journey from the ground up, FinDock’s Payment API is there underneath it all, the same engine the templates are built on.

Available templates

FinDock Labs is FinDock’s open-source GitHub repository. The templates are free and public, with nothing to subscribe to, and you deploy them straight into your own Salesforce org. They’re community starting points built on FinDock’s supported payment components, so you’re customising a working example rather than relying on it as-is. For donations, it has templates for both the site and the flow underneath it:

• Donation site, which uses either the Donation flows for Fundraising or Donation flows for NPSP template, for one-time and recurring gifts.
• An LWC template, for teams that want to build their own Lightning Web Components using FinDock’s payment components, without Flow.

All templates are accessible and WCAG-compliant, and support multiple currencies, languages and payment methods.

What this means for fundraising teams

Your team can build donation pages in Salesforce, deploy them quickly for each campaign, and handle the everyday changes themselves, the amounts, the wording, the look, keeping technical help for the genuinely custom work. Gifts land directly on the donor record, and the pages sit on the same platform as the rest of your fundraising data. so there’s one less system for your team to manage.

Next step

The donation templates are available on FinDock Labs, where each one includes a preview of what it looks like and how it works:

• Donation site: github.com/FinDockLabs/experience-cloud-donation-site
• Donation flows for Fundraising: github.com/FinDockLabs/experience-cloud-donation-flows-fundraising
• Donation flows for NPSP: github.com/FinDockLabs/experience-cloud-donation-flows-npsp
• Full template library: github.com/FinDockLabs/payment-experiences-templates

For a walkthrough, or to talk through what your fundraising organisation needs, contact your FinDock representative.

FinDock’s July ’26 release went live in your Salesforce org the night of Sunday, July 19, after first appearing in your sandbox. You can watch the July release webinar for a detailed walkthrough and to see the detailed demos, or review the release notes for the complete list of the changes for this release.

With summer this good across Europe, we’ll keep it quick. Here are the release highlights so you can get back to enjoying it:

• FinDock Payment Experiences, our Experience Cloud payment solution, now ships with ready-to-use templates on FinDock Labs (pilot)
• Outbound payments now live in the UK, sending Faster Payments via GoCardless 
• e-Mandates for the Netherlands, a bank-validated SEPA mandate captured and stored natively in Salesforce (pilot)

And to help you close out the month before you head off on holiday, we also shipped:

• Guided Matching improvements, letting you settle multiple installments in one action and match against Data 360

FinDock Payment Experiences

Since opening pilot sign-ups in May, we’ve been building out FinDock Payment Experiences, our online payment solution combining Salesforce Experience Cloud for the site, Flow for building out the payment journey, and FinDock payment components for accepting the payment itself. With the July release, this pilot moves forward with working templates you can deploy directly from FinDock Labs.

More templates are available than we covered at the webinar. For fundraising, donation flow templates now cover standard Fundraising, Fundraising UK with Gift Aid, and NPSP, letting payers choose a one-time or recurring amount and frequency.

For membership, subscriptions, or any other pay-now use case, a checkout flow template can pay against an existing installment or recurring record rather than only creating new ones. Both come with a matching Experience Cloud site template, so you’re not building the site yourself. And if you’d rather skip Flow entirely, a pro-code LWC template gives you full control over layout, validation, and navigation.

Every Flow and site template is built on the same three components: Experience Cloud as your website and page builder, Flow as your payment form builder, and FinDock payment components for payment method selection and payment initiation.

The FinDock payment method component shows every processor and payment method enabled in your org, lets you search and reorder them, and exposes the underlying API parameters so you can further personalize things like bank statement descriptions using Flow variables.

Why does this matter?

Until now, FinDock offered two ways to build online payment experiences: out-of-the-box Giving Pages and PayLinks, or a fully custom build on the Payment API. FinDock Payment Experiences sits between the two, giving you more flexibility than Giving Pages without the development cost of a custom build, all while staying inside Salesforce so it can connect to Data 360, Marketing Cloud, and Agentforce.

The templates available on FinDock Labs today are only the start, with more being released as the pilot progresses. Everything is built with native Experience Cloud and Flow tooling, so you can change the layout, add fields, or extend the logic without needing to touch code.

If you want to join the pilot or contribute a template of your own, sign up at forms.gle/vwcnuyrtyXNkY9mZ6 , email laurens@findock.com , or reach out to FinDock Support.

Templates are hosted on GitHub under FinDockLabs, and community contributions are welcome.

Outbound payments go live in the UK with GoCardless

Outbound payments already work inside FinDock today, through SEPA Credit Transfer to bank accounts in the SEPA region. This release, we’re extending the capability to the UK, adding Faster Payments via GoCardless, so outbound disbursements, claims, and supplier payments can go out from the same Salesforce record where you manage collections.

With FinDock, every inbound and outbound transaction is recorded in Salesforce, so finance teams can build their reconciliation and reporting views from one set of data instead of stitching two together.

Why does this matter?

Sending money out has typically meant logging into a separate banking portal, re-entering details by hand, and reconciling two systems afterward. Bringing UK payouts into that same outbound payments capability removes that manual step and the audit risk that comes with it. Payouts also trigger directly from Salesforce, with Confirmation of Payee run against every new beneficiary and verified bank details reused from existing collections where available, so additional security is built into the payout itself rather than handled separately in a banking portal.

We’re seeing this used for member loan disbursements at credit unions, claim payouts at insurers, grant and bursary payments for nonprofits, and loan disbursements for lenders. 

Outbound payments with GoCardless is a paid add-on and live now for UK and European customers; talk to your Customer Success Manager to get started.

e-Mandates for the Netherlands: bank-validated SEPA mandates

Without a properly signed mandate, payers have up to 13 months to reverse a SEPA Direct Debit payment, leaving your organization with little to defend a disputed transaction with. This release adds e-Mandates for the Netherlands to FinDock, a signature route built on incassomachtigen.nl, the established Dutch payment industry standard for bank-validated mandates.

This pilot covers FinDock’s native SEPA Direct Debit processing for select banks in the Netherlands, connecting directly to the payer’s bank to set up compliant mandates. When a payer signs an e-Mandate, they’re redirected to their own bank to authenticate, the bank confirms the mandate, and FinDock stores the result as a Mandate record in Salesforce along with the proof.

You control how payers sign per PayLink or Page: the existing IBAN-and-name flow for a fast sign-up, or the new e-Mandate flow for a bank-validated mandate and a stronger legal position. The two signing options can be offered side by side, so you can keep the fast flow where speed matters and add e-Mandate wherever that stronger legal position is worth having.

Why does this matter?

An e-Mandate is bank-validated by design, so it reliably secures the standard eight-week reversal window rather than risking the 13-month window that applies when a mandate’s validity can be disputed. That matters most for organizations where the customer gets the benefit before the payment is fully settled, membership organizations that grant access from day one, insurers where cover starts as soon as a policy is signed, or subscription services that deliver the product immediately. For those cases, that certainty means less time a completed transaction stays reversible, and a bank-validated mandate to point to if a dispute does come in.

This is the same approach FinDock already runs in Sweden with Autogiro and Bankgirot, now extended to the Netherlands, with more countries and signature types planned. e-Mandates is a paid add-on and currently in pilot; talk to your Customer Success Manager to get it switched on for your org.

Guided Matching: settle multiple installments and query Data 360

Two updates cut down manual work in reconciling payments this release. You can now select multiple installments in Guided Review and settle them together in a single action, useful when one incoming payment needs to clear several scheduled amounts, such as an invoice covering multiple installments.

Guided Matching also gains a new rule type that queries Data 360 directly, so campaign, source, fund, and attribution data can be used to recognize a payment, not just data already synced into your org.

Why does this matter?

Fewer exceptions per transaction means your Guided Review backlog clears faster. The detail that identifies a payment often lives in Data 360 rather than in Salesforce itself, so being able to query it directly should mean higher auto-match rates and less time in manual review.

What else shipped this release?

This release also includes Paya for FinDock moving to beta and opening to all customers, security improvements behind the scenes, and a long list of smaller fixes across the platform. We’ll be covering Reconciliation Optimisations, e-Mandates for the Netherlands, and this release’s security improvements in more detail in upcoming posts. In the meantime, for the full technical detail, review the complete release notes or watch the release webinar.

How Vierstroom is building a membership platform for every generation with Salesforce and FinDock

Vierstroom is a Dutch healthcare and membership organization dedicated to helping people live independently and comfortably for as long as possible. Through its membership services division, the organization supports more than 60,000 members with services, advice, and benefits that contribute to their wellbeing and quality of life.

For more than 26 years, Vierstroom’s membership organization relied on the same system. It had served the organization well, but over time it became harder to support the ambitions Vierstroom had for the future. Processes that worked years ago were becoming increasingly difficult to scale, automate and improve.

As member expectations evolved and the organization looked for ways to engage both existing and future generations of members, Vierstroom decided it was time for a new foundation.

Together with Salesforce, FinDock and implementation partner, the organization moved its membership administration and payment operations to Salesforce.

Creating a foundation for growth

While Vierstroom is a much larger organization, its membership services division is run by a relatively small team supporting more than 60,000 paying members.

As Vierstroom’s ambitions around automation, member engagement and scalability grew, the organization increasingly found itself working around the limitations of its existing system.

“We increasingly ran into the limits of what the system could support.”

The organization wanted to:

• Automate repetitive administrative work
• Create stronger connections between membership data, communications and payments
• Support future growth without increasing manual workload
• Modernize member experiences while continuing to serve less digitally active members

After evaluating different CRM solutions, Vierstroom selected Salesforce Nonprofit Cloud and FinDock as the foundation for its future member platform.

Supporting every member’s preferred payment journey

One of Vierstroom’s key requirements was flexibility.

While many members prefer digital payment methods, a significant part of the membership base still relies on letters and manual bank transfers. Moving everyone to a fully digital process simply wasn’t realistic.

Imagine being 80 years old and suddenly being expected to manage everything digitally. The local bank branch has almost fully disappeared. Services that once involved a phone call or paper form now require online portals, passwords and apps. What feels convenient to one generation can feel overwhelming to another.

Vierstroom sees that reality every day. While the organization wants to encourage efficient payment methods such as direct debit, it also recognizes that many members still prefer receiving a letter and manually transferring their contribution. Supporting those members is not seen as an exception. It is part of providing good service.

“We want to stimulate direct debit as much as possible because it is the most efficient process. At the same time, we have members who still want to pay manually. We need to support both.”

Turning flexibility into everyday payment processes

That need for flexibility now comes together in the way Vierstroom manages its membership payments in Salesforce and FinDock. The platform supports the core payment processes around membership, while still allowing different journeys for different members. This includes:

• Supporting both direct debit and manual payment methods
• Managing annual membership contributions from a single platform
• Offering digital payment links while continuing to support letter-based payment journeys
• Automating payment reminders and follow-up communications
• Collecting payments for member events through PayLinks
• Processing refunds through SEPA Credit Transfer
• Bringing member, payment and financial data together in Salesforce

Members who prefer digital communication can receive payment links by email. Members who prefer traditional communication can continue receiving letters and paying manually.

For Vierstroom, that means payment operations can become more efficient while the member experience remains flexible, personal and accessible.

A platform with more potential still to unlock

Vierstroom sees the implementation as the beginning of a longer journey.

The organization is continuing to explore additional automation opportunities, including e-mandates and further optimization of payment processes.

For a relatively small team supporting tens of thousands of members, those improvements can make a significant difference.

“We invest in systems and automation because we have a lot of work with a relatively small team.”

The biggest benefit so far is having a platform that can continue to evolve alongside the organization, something that had become increasingly difficult with the previous system.

Advice for other membership organizations

Looking back, Vierstroom encourages organizations to be realistic about the role of analogue processes.

Even in a digital-first world, some members will continue to prefer letters, manual payments or telephone registrations.

“You should not assume everything will become completely digital. If you serve a certain target group, there will always be an analogue component and the technology you choose should support that.”

For Vierstroom, the goal is not to force every member into the same journey.

It is to create a platform that supports both digital convenience and personal service, while giving the organization the flexibility to keep improving in the years ahead.

How Konzernverantwortung scaled supporter engagement and donation operations with Salesforce and FinDock

Konzernverantwortung, the Swiss Coalition for Corporate Justice, mobilizes supporters across Switzerland to campaign for stronger corporate accountability laws.

As the organization grew, so did the complexity behind supporter management and donation processing. What started as a small coalition quickly evolved into a large-scale movement with growing fundraising operations, thousands of supporter interactions, and national campaigns requiring speed, flexibility, and reliable data.

To support that growth, the organization implemented Agentforce Nonprofit (formerly known as Nonprofit Cloud) and FinDock together with Salesforce partner ANT Informatik.

The result: faster donation processing, less manual work, and a more responsive supporter experience.

“Thanks to Salesforce and FinDock, we can process donations much quicker and communicate with supporters much faster than before.”
— Dario Schai, Fundraising and Campaign Manager at Konzernverantwortung

Growing beyond manual processes

In the early years, Konzernverantwortung operated with a lightweight setup managed largely through external systems and spreadsheets.

As donation volumes increased, the limitations became clear:

• Supporter data was managed externally
• Payments without reference numbers required manual matching
• Payment processing relied on scripts and spreadsheets
• Teams lacked direct visibility into supporter and donation data
• Thank-you communications were delayed because processing took too long

The organization also had to support typical Swiss donation behavior, where many supporters still donate through payment slips and QR bills via e-banking or post offices. Konzernverantwortung needed a solution that could handle both traditional donation methods and future automation ambitions.

Why Salesforce and FinDock

Konzernverantwortung selected Agentforce Nonprofit as the foundation for supporter engagement and fundraising operations.

Implementation partner ANT Informatik, introduced FinDock to manage payment processing and reconciliation directly inside Salesforce.

Key requirements included:

• Reducing manual reconciliation work
• Supporting Swiss QR bill and reference number payments
• Improving visibility into supporter and payment data
• Automating donation matching and supporter communications
• Creating a scalable foundation for future campaigns

FinDock’s Guided Matching capabilities became especially valuable for handling payments without reference numbers, such as donations connected to campaign material orders.

“With FinDock integrated in Salesforce, it’s much easier to process payments without reference numbers and see whether someone is already in our database.”
— Dario Schai, Fundraising and Campaign Manager at Konzernverantwortung

Reducing manual work while improving supporter experiences

One of the biggest operational improvements came from reducing manual payment processing work. Before Salesforce and FinDock, payment imports and reconciliation were handled through a combination of scripts, spreadsheets, and manual database updates.

Today, much of that process is automated directly within Salesforce. The organization estimates it has already reduced the time spent on payment processing by more than half, with further efficiency gains expected over time as more supporter payment history becomes available in Salesforce.

For a small fundraising operation, even modest efficiency improvements make a major difference.

“We probably saved around two-thirds of the time compared to our previous process.”
— Dario Schai, Fundraising and Campaign Manager at Konzernverantwortung

The impact extends beyond internal operations. Because donations are processed faster, the organization can now thank supporters much sooner after a donation is made.

Previously, donations and thank-you communications were processed only once or twice per month. Today, the organization typically processes and responds to donations weekly.

Salesforce Flows help automate the thank-you process based on supporter preferences and donation amounts. Supporters can receive either an email or a personalized letter depending on the donation value and communication preferences.

The organization also sees future opportunities for deeper personalization using payment data directly inside Salesforce.

Building a scalable foundation for future campaigns

For Konzernverantwortung, Salesforce and FinDock are helping create a more scalable and supporter-centric organization. The team now spends less time on manual payment operations and more time engaging supporters and running campaigns, improving the payment experience.

Dario also advises other nonprofits to invest time upfront in designing their payment matching strategy carefully.

“The Guided Matching rules are very powerful, but it helps a lot if you already know what kinds of payments and exceptions you need to handle.”
— Dario Schai, Fundraising and Campaign Manager at Konzernverantwortung

As the organization prepares for future campaigns and large-scale signature collection initiatives, Salesforce and FinDock provide the flexibility and operational foundation needed to support continued growth.

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:

1. Refunds from Salesforce, expanded to Stripe and Authorize.net, with a new out-of-the-box component (beta)
2. Salesforce Bulk API 2.0 moves to General Availability
3. Reconciliation improvements, more control over matching and payment references

Also announced:

1. 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:

1. Experience Cloud as a website and page builder – responsive, brandable, with a free Salesforce CMS included
2. Flow as a form builder – flexible multi-step journeys with conditional logic, validation, and no-code configuration
3. 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