Logo

How can we help you?

Search our knowledge base to get answers to your questions, access video training & more!

Spring '26 Release

Release Notes

Spring '26 Release

Last updated on 18 Sept, 2026

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

  • Braintree Invoice Details – enhanced the Braintree payment integration to include invoice details with each transaction, including the Invoice Number and Invoice PO Number.

  • CardConnect: Void and Refund Now Restricted for Pending Settlement Transactions – prevents users from voiding or refunding CardConnect transactions while they are in Pending Settlement status, helping prevent processing errors and ensuring transactions can only be acted upon when supported by the processor.

  • Dual Price Fees for ACH – added support for applying Dual Price fees to ACH payment transactions, providing consistent fee calculations across card and ACH payment methods when Dual Price is configured.

  • CyberSource 3D Secure (3DS) Authentication Flow – updated the CyberSource integration to support the latest 3D Secure authentication flow, improving compatibility with payer authentication services and secure transaction processing.

  • Improved CardConnect Deposit and Payment Status Processing – enhanced batch processing to retrieve deposits from a rolling date range, helping ensure delayed or late-posted deposits are captured and payment statuses are updated correctly.

  • Enhanced Payment Authorization Requirements – added support for photo ID verification, electronic signature capture, and Terms & Conditions acceptance across payment transactions. These enhancements help ensure the required authorization information is captured before completing a payment.

  • Payment Intent Enhancement: Verify Transactions Before Taking Action – added a Verify Transaction feature that allows users to search for and review processor transactions directly from the payment workflow before creating a new payment, helping prevent duplicate payments when a previous transaction may have timed out.

Fixes and Improvements

  1. eCheck Payment Status Does Not Change for Failed Transactions
    Affected Orgs: Organizations using Authorize.net with eCheck enabled
    Fix: Updated eCheck status processing so isSuccessful is evaluated correctly before the transaction status, ensuring failed eCheck transactions are properly reflected.

  2. Clover Authorization Error in Canada
    Affected Orgs: Organizations using Clover devices in Canada
    Fix: Updated the payment request to use the final transaction parameter instead of the capture parameter, preventing the regional authorization error.

  3. Future Auto Pay Dates Not Being Processed
    Affected Orgs: Organizations with invoices configured for a future auto pay date
    Fix: Updated the processing logic to set the Pending Auto Bill Pay flag to True, allowing scheduled invoices to be identified and processed when the auto pay date is reached.

  4. Incorrect Invoice Status for Mixed Installment Payments
    Affected Orgs: Organizations processing installment payments using mixed payment methods where an eCheck remains pending
    Fix: Updated invoice status processing to keep the invoice in Payment Pending status when a previous eCheck transaction is still pending.

  5. CyberSource Unified Checkout Improvements

    • CyberSource Payment Profile Creation Error
      Affected Orgs: Organizations using CyberSource Unified Checkout to create payment profiles with transient tokens through the REST API
      Fix: Updated the profile creation process to correctly handle transient tokens and include the payment processor ID, preventing the null reference error.

    • CyberSource Card Type Displayed as Unknown
      Affected Orgs: Organizations creating CyberSource payment profiles using transient tokens
      Fix: Updated payment profile processing to correctly identify and store the card type.

    • Incorrect State/Province Display in CyberSource Checkout
      Affected Orgs: Organizations using CyberSource Unified Checkout where state or province values are provided as full names or non-standard formats
      Fix: Updated the checkout component to correctly handle and display state and province values regardless of whether they are provided as full names or two-letter abbreviations.

    • CyberSource Unified Checkout Locale Support
      Affected Orgs: Organizations using CyberSource Unified Checkout for invoice payments in multiple languages or regions
      Fix: Updated the checkout experience to use the locale configured on the invoice, ensuring the payment page displays the appropriate language and regional format.

  6. CyberSource Credential Validation Error
    Affected Orgs: Organizations configuring or validating CyberSource processor credentials
    Fix: Removed the dependency on the CyberSource BIN Lookup Service API during credential validation, allowing credentials to be validated without errors caused by an unavailable or unreachable service.

  7. Incorrect Payment Processing When Using Multiple Browser Tabs
    Affected Orgs: Organizations processing multiple payments simultaneously in separate browser tabs
    Fix: Updated the payment processing flow so each browser tab maintains its own payment session and uses the correct customer and payment method information.

  8. Incorrect Payment Amount When Resending an Invoice
    Affected Orgs: Organizations processing payments and resending invoices using separate console tabs
    Fix: Updated the invoice resend process to preserve the correct payment amount and prevent previously processed payment information from being overwritten.

  9. Inactive Recurring Invoice Schedule Values Displayed
    Affected Orgs: Organizations managing Recurring Invoice Schedule picklist values
    Fix: Updated picklist handling so only active Recurring Invoice Schedule values are displayed when creating new records.

  10. Duplicate Stripe Payment Profiles
    Affected Orgs: Organizations using Stripe where a declined payment attempt is followed by a successful payment attempt in the same payment session
    Fix: Updated payment profile creation to prevent duplicate Salesforce payment profiles and ensure payment profiles remain correctly synchronized with Stripe.

  11. CyberSource Payment Submission Error with Special Characters
    Affected Orgs: Organizations using CyberSource payments where billing addresses contain special characters or line breaks
    Fix: Updated the CyberSource payment submission process to properly handle special characters and multi-line billing addresses, allowing transactions to be submitted successfully.

Did you find this article helpful?
Previous

Winter '26 Release

Next