11.1 Release Notes

This release is currently in testing and some of the items might not make to the final release.

Payments2Us workflows have been migrated to Salesforce Flows in line with Salesforce’s latest platform guidelines.
Existing workflows will continue to work as they do today and no action is required immediately.
For each workflow, a corresponding Flow has been included in this release and is set to Inactive by default.
You may choose to thoroughly test the new Flow in your org, deactivate the existing workflow and Activate the corresponding Flow once testing is complete.
Similar to workflows, you can also clone Payments2Us Flows, make changes to suit your requirements, and then activate them.
Please review the workflow to flow migration help article for further details.

In this release, we’re introducing an exciting new feature, Service Agent.
This feature allows customers to interact with an autonomous AI agent that handles common inquiries about donations and receipts, and escalates complex issues when needed.

Manual Payment LWC version is another feature we are introducing in this release.
This is a modern, Lightning Experience-native interface for recording non-credit card payments in Salesforce. This component replaces the legacy Visualforce manual payment page with a fully integrated Lightning Experience, providing a faster, more intuitive user experience with real-time field validation, automatic calculations, and intelligent address auto-complete.

The Payments2Us Health Check has been enhanced to support the workflow-to-flow migration.
It identifies workflows that have migrated Flows available and recommends Deactivating the legacy workflow and Activating the new Flow.
It also detects scenarios where both a workflow and its corresponding Flow are active at the same time, and flags these so you can safely deactivate the workflow (or flow).

Payments2Us now also supports automatic reconciliation for Stripe, payFURL and BlackBaud Payment Gateways.
Stripe: Credit Card and Direct Debit Payments.
PayFURL: Credit Card Payments.

For the users who request new BPAY License:

The BPAY developers portal has moved from bpaygroup-portal.apigee.io to developers.auspayplus.com.au/bpay/.
BPAY now supports Sandbox APIs for testing, alongside its existing Pre-Production APIs.
As part of this release, a new Remote Site Setting sandbox.api.bpaygroup.com.au has been added.
This must be manually activated in your Salesforce org before using Sandbox API Keys for BPAY testing.
The BPAY Sandbox environment has limited test data and functionality. For more accurate testing, it is recommended to use BPAY Non-Production API keys, as they better reflect real-world behaviour.
For more details, review: How to test with BPAY Sandbox APIs?

The “Available for Lightning Experience, Experience Builder sites, and the mobile app” option has been enabled for the StripeVerify Visualforce page, allowing it to be used within Experience Cloud sites as well.
Support for $0 memberships has been added to the checkout form. Previously, this was only possible through the use of a voucher code.
Manual Direct Debit is now supported for the PayFURL payment gateway.
A new field, “Exchange Rate” has been introduced on the Payment Txn object. This field is currently populated with the exchange rate returned by the Stripe payment gateway.
An issue where Manual Direct Debit was not functioning for the Westpac Quickstream payment gateway on the checkout form has been resolved in this release.
For Xero Contact syncing, the BSB Number and Account Number fields were previously being cleared in Xero if they were blank in Salesforce. This issue has now been resolved.
An issue where the address was not defaulting based on IP when the “IP Defaulting” option was enabled on the merchant facility has been resolved.
For Stripe payments, the Balance Transaction ID was incorrectly being stored in the Payment Gateway Response Code field instead of the success code. This issue has been fixed in this release.

Need Help? Let's Find the
Answer Together!