We’re excited to introduce new features, enhancements, and fixes designed to improve your payment processing experience, increase flexibility, and reduce operational issues.
New Features & Enhancements
Commerce Hub – enables integration with Fiserv Hosted Checkout, allowing merchants to deliver secure, branded payment experiences with support for credit card while simplifying PCI-compliant payment processing and reducing implementation effort.
CyberSource Unified Checkout – enables merchants to utilize a secure, hosted payment component that embeds directly into the checkout page, supporting credit card, ACH, Google Pay, and Apple Pay, while reducing PCI DSS scope by ensuring sensitive payment data is handled by Cybersource.
Auto Decline Soft Decline Payments – introduces an option to automatically decline transactions marked as “Authorized – Pending Review,” allowing the system to void the transaction, prevent payment record creation, and log the attempt as a failed transaction, reducing manual intervention for supported processors such as Cybersource and Authorize.net.
Refund Without Processor Visibility Setting – introduces a configurable option to show or hide the “Refund Without Processor” functionality, allowing administrators to control its availability through a checkbox in Payment Center Settings.
QuickBooks Connection Enhancement – enables customers to configure and use their own Intuit developer application by providing Client ID and Client Secret, securely managing credentials through encryption and supporting seamless OAuth connection with QuickBooks.
Credit Memo Class Reference Mapping – enhances Credit Memo synchronization by supporting Class Reference mapping at the line level, ensuring values from Salesforce are accurately passed to QuickBooks and reflected per line item for improved financial tracking and reporting.
Schedulable Exchange Rate Sync – introduces an automated batch process to regularly retrieve exchange rates from QuickBooks and update Salesforce records, with support for scheduled execution and the ability to run per specific QuickBooks connection for improved accuracy and efficiency.
Fixes and Improvements:
1. Invalid Payment Amount When Amount Due is Zero
Affected Orgs: Stripe processors
Fix: The system now validates payment amounts when the amount due is zero, preventing users from entering arbitrary values.
2. Multiple HTTP 500 Errors on Square Webhooks
Affected Orgs: Square processors
Fix: Duplicate webhook events are now ignored if the transaction has already been processed, preventing unnecessary errors.
3. Invoice PDF Error (STRING_TOO_LONG)
Affected Orgs: Orgs with long contact names
Fix: The Recipient Name field length has been increased from 50 to 200 characters to prevent PDF generation errors.
4. NMI ACH SEC Code Always Set to “WEB”
Affected Orgs: NMI processors using ACH
Fix: The SEC code is now dynamically set based on the account type entered during payment or stored in the payment profile.
5. ACH Payment Link Showing Credit Card Option
Affected Orgs: Orgs using payment links with specific processor settings
Fix: Payment links now correctly honor configuration settings such as disabling credit card payments and enabling eCheck only.
6. ‘Payment Processor is not defined’ Error
Affected Orgs: Orgs charging payment profiles without a defined processor
Fix: The system now defaults to the configured processor at the entity or system level when the profile is missing this value.
7. Error with eCheck Profile Missing Name on Account
Affected Orgs: Authorize.net processors
Fix: Transactions will proceed without including the Name on Account if it is blank, preventing processing errors.
8. Cybersource ACH Refund Error
Affected Orgs: Cybersource processors using ACH
Fix: The correct payment type is now passed during refund transactions to ensure proper processing.
9. Cybersource Auto Pay Error (Invalid merchantInitiatedTransaction.reason)
Affected Orgs: Cybersource processors with recurring payments
Fix: The unsupported field has been removed from the payload to align with API requirements.
10. Future Installments Being Paid Incorrectly
Affected Orgs: Orgs using PayPal installments
Fix: Removed duplicate processing calls to ensure only the correct installment is paid.