FinDock Payment Experiences

Combining FinDock’s native payments technology with Salesforce, FinDock Payment Experiences is an exciting new chapter in customer payment happiness. The solution enables you to build digital payer experiences directly in Salesforce with full control over the user experience.

FinDock Payment Experiences consists of several building blocks, enabling you to step in at any level of Salesforce technology:

• Payment API: a robust REST API for creating and updating data in Salesforce
• Lightning Web Component (LWC): managed LWCs for Flows and custom LWCs
• Flow: automation for user interactions and data manipulation
• Experience Cloud: websites and pages for public (unauthenticated) and private (authenticated) digital experience
• Templates: A variety of smart templates on FinDock Labs to jump start your development. We provide templates for Flows and Experience Cloud sites or pages for both nonprofit and commercial use cases.

Using any of these components (or a combination of them) enables you to tailor your payment experience to your exact needs.

The Payment API is a fundamental part of the FinDock offering. FinDock Payment Experiences leverages the API to offer maximum flexibility and performance while delivering a low-code development path through familiar configuration interfaces. For more information about the Payment API, see How the API works.

FinDock Payment Experiences includes Lightning Web Components that you can use within Flows. These components open the door to advanced payment experience configuration without requiring pro-code capabilities. We currently provide two managed components: FinDock Payment Method Selector and FinDock Pay Button.

While we advise you to use both when building your first Payment Experience in Flow, both components can be used individually or included directly in your own experience components!

As part of our starter templates, FinDock offers an unmanaged Amount & Frequency selector component for one-time and recurring donations. As it is unmanaged, you can use and extend this component in any environment.

If you have configured Giving Pages payment methods, you will find the FinDock Payment Method Selector familiar territory. The selector component includes a configuration editor you open through the component settings to set up payment methods for your payment experience.

The configuration editor automatically detects the details of your FinDock Setup and presents them in an easy-to-use Lightning Web Component where you define payment methods, set parameters, select target merchant accounts, and other aspects of the payment experience.

When you are finished, and the component is presented to the payer, it displays the enabled payment methods available for selection. If you configured a payment method to show parameters, these are also presented.

The FinDock Pay Button is a one-button step to initiate a payment through FinDock. It is a visual configuration interface to set up the payment which is initiated upon clicking on the button. It allows you to link your flow variables to your Payment Intent, extracting away the complexity developers face when building pro-code solutions.

Through the configuration editor, you build the Payment Intent request logic. The request can use dynamic logic, variables and static values.

If you are using the Payment Method Selector component, make sure to link the output of that component to the Payment Method variable in the Payment Intent mapping.

Once configured, the Pay Button component can be used in any Lightning-enabled solution from Salesforce. When the component is presented to the end user, it simply shows a button styled in your Salesforce theme. When the Pay button is clicked, a Payment Intent is created, and the online payment process is kicked off.

Salesforce Flows are the powerhouse of automation and logic control in your payment experiences. You can create anything from simple single-step payment forms to dynamic, multi-step payment journeys with conditional logic, validation, etc.

The toolbox you get through Flows is extensive and growing. Templates and out-of-the-box actions and components already get you far, but if you want more, you can just build it yourself as a custom component.

Alongside payment data, CRM data, components and actions, you can use anything from Data Cloud, add Agentforce agents and much more in Flows. Drop your Flow into an Experience Cloud page where it automatically adopts the look and feel of your Experience Cloud theme.

To help you get started, FinDock provides Flow templates for single-step and multi-step payment forms (screen flows). You can deploy these templates to your org directly from FinDock Labs. These include implementations of FinDock managed components as well as examples of how you can, for example, use Assignment elements to get Payer (contact) details or add extra data that is passed to the Payment Intent generated by the Pay Button component.

With Experience Cloud, Salesforce gives you a power set of tools for building digital experiences. You can create fully responsive, high performance pages and sites with anything from no-code to pro-code setups.

In the FinDock Payment Experiences context, think of Experience Cloud as the wrapping around your custom payment experience. It completes the user experience with your look and feel and your custom interactions. You can build anything from private pages to authenticated portals and public sites using the fine-grained access control provided by built-in enterprise security and compliance of Salesforce.

To help you get started, FinDock provides Experience Cloud templates for donation and checkout pages. You can deploy these templates to your org directly from FinDock Labs.

As we noted earlier, FinDock Payment Experiences operates entirely within the Salesforce enterprise security landscape. The solution uses all of FinDock’s existing framework with regards to permissions, compliance and other security-related matters.

The FinDock Payment Experiences solution comes with dedicated permissions sets that need to be assigned to user profiles for access to the managed LWCs. Simply follow standard Salesforce practices, for example, to grant access for a Guest User to use the FinDock Pay Button component. Personally Identifiable Information (PII) captured through FinDock Payment Experiences is not stored by FinDock components, templates or external systems.