FinDock’s May ’25 release went live in production on Sunday, 25 May. Some of the key highlights include support for ACH Direct Debit via Authorize.Net, Direct Debit in our MOTO Virtual Terminal, and WCAG-compliant PayLinks – all right inside Salesforce.
Watch the release webinar or read the release notes for the full rundown.
1. Support for ACH Direct Debit via Authorize.Net
Back in March we introduced our new Authorize.Net integration for card payments – a huge leap for organizations using Salesforce in the U.S. and Canada. In our May release, we’re expanding that integration with full support for ACH Direct Debit.
Why it matters
ACH Direct Debit through Authorize.Net keeps transaction costs to just a few cents, far lower than card fees, while giving you a payment method that’s built for monthly memberships, donations and other recurring revenue.
Because everything happens inside Salesforce, teams can create, update, reconcile, and report on ACH payments using the same FinDock solutions they already rely on for cards – FinDock PayLinks, Giving Pages, and the MOTO Terminal.
2. Set up Direct Debit payments via FinDock’s Virtual Terminal (MOTO)
Our Virtual Terminal component turns Salesforce into a secure virtual terminal, allowing agents to collect payments when the payer isn’t present. In the May ’25 release we added an option to set up ACH Direct Debit payments alongside existing card capabilities.
Why it matters
Agents can now capture one‑time or recurring ACH Direct Debit payments right inside Salesforce by keying in the payer’s routing and account numbers during a service call. They can also turn mailed response slips or other paper forms into live mandates on the spot, instantly scheduling new collections or installments.
All bank details are tokenized as soon as they’re entered, so agents can safely reuse or update a customer’s saved payment method without ever exposing sensitive data, keeping you PCI‑compliant and ready for the next interaction.
To learn more about how it works visit our Agent Payments page.
3. Accessibility: WCAG 2.1 AA Compliance for PayLinks
Our out‑of‑the‑box PayLinks have been fully audited and updated to meet the WCAG 2.1 AA accessibility guidelines. In our next release, this same level of accessibility will roll out to Payment Pages.
Why it matters
Ensuring every customer can complete a payment journey with confidence isn’t just good practice, it’s an important step toward a more inclusive experience.
By bringing PayLinks up to WCAG 2.1 AA, we’ve designed an experience that screen-reader users, keyboard navigators, and anyone relying on assistive tech can perceive, operate, and understand from the first click to the confirmation screen.
Meeting this standard also keeps you aligned with major regulations such as the ADA in the U.S. and EN 301 549 in the EU, reducing legal exposure while signaling that your organization welcomes every customer or donor.