We’re excited to share the latest updates included in this release! These fixes and improvements are designed to enhance stability, accuracy, and the overall payment experience.

• Performance improvement of Recurring Invoice batch job - This enhancement allows users to specify the number of invoice records processed in each batch, giving them greater control over system load and overall performance.

• Deposit Schedule offset - A new Deposit Schedule Date Offset field was added so the batch job pulls deposit data based on processor timelines instead of today’s date.

• Enable Google Pay payment for CardConnect - The article explains how to enable Google Pay in Payment Center, outlining the customer experience and how payments are recorded in Salesforce.

• Enable Apple Pay payment for CardConnect - The article explains how to enable Apple Pay in Payment Center, outlining the customer experience and how payments are recorded in Salesforce.

• CardConnect - Level 2/Level 3 support - CardConnect supports Level 1–3 data, enabling lower interchange fees, greater transparency, and stronger reporting.

• Cybersource REST API - The CyberSource integration was upgraded to the REST API, providing enhanced security, broader payment support, and improved maintainability.

• Clover Setup - This article guides you through setting up Clover as a payment processor in Payment Center.

• Default SEC code - This update introduces the ability to configure the SEC code dynamically based on the account type used for the transaction.

• reCaptcha support - The guide outlines how to integrate Google reCAPTCHA v3 on key Payment Center pages to protect forms from bots and automated abuse.

Fixes and Improvements:

1. Customer Name Missing in eCheck Transactions
Affected Orgs: Authorize.net processors
Fix: First name and last name are now passed in the API request for eCheck transactions.

2. Bank Account Type Always Defaulted to “Checking”
Affected Orgs: Authorize.net processors
Fix: The bank account type selected by the user during the payment process is now correctly passed in the API request.

3. Customers Charged After Sandbox Refresh
Affected Orgs: Orgs that refresh sandbox and run recurring invoice batch process
Fix: Live processors in sandbox orgs now require a separate encryption key, preventing charges from being sent to live accounts.

4. Rounding Error on Invoice Total (Discount Percentage)
Affected Orgs: Orgs applying discount percentages on invoice lines
Fix: Invoice totals are now rounded correctly when discounts are applied in formula fields.

5. Error on Card Present Transactions
Affected Orgs: Authorize.net processors using card-present (swipe device) payments
Fix: Request parameters have been rearranged according to the XSD, resolving card-present transaction errors.

6. Credit Memo Not Displayed at Payment Terminal
Affected Orgs: Orgs where “Other” payment method is set to Credit Memo only
Fix:When selecting “Other,” the system now defaults to the first available valid option.
If no Credit Memo is available, the “Other” tab will not be displayed.

7. Email address not visible when Stripe 3DS2 is enabled
Affected Orgs: Orgs with Stripe 3DS2 enabled
Fix:The payment page has been updated to allow users to enter an email address when processing payments with Stripe 3DS2.

Post-Upgrade Note:

In some cases, due to the rounding error fix, paid invoices may temporarily revert to an “Overdue” status with a small balance variance (for example, 0.01 or -0.01).
This behavior can occur across all orgs upgrading to this version and is a result of recalculated rounding adjustments introduced in the fix.

Resolution: Run the provided utility in the Execute Anonymous window of the Developer Console to correct the data.

<strong>fw1.RoundingUtil.balanceInvoicePaidAmount();</strong>