Changelog
We are constantly improving our platform by releasing new features, fixing bugs, and updating documentation. You can read about these improvements in our changelog.
2026
Updated
AnalyticsPaymentsMore Accurate Payment Success Rate in Payments Dashboard
We’ve improved the default calculation of the Payment Success reports in the Payments Dashboard to more accurately reflect actual payment outcomes.
- Previously, orders that were blocked before any payment attempt due to fraud checks or export compliance were still counted as submitted orders. Because these orders never had a chance to be paid, they could artificially lower the Payment Success Rate.
- With this update, the default calculation now excludes orders that were blocked before a payment attempt from the denominator. For transparency, you can also switch to an optional view that includes all submitted orders, matching the previous calculation method.
- As part of this update, the Product List filter is now also available in the Filters section of the Payments Dashboard.
For more details about Payment Analytics available in SCM check our business user documentation
Why this is important: This update gives you a more accurate view of payment performance by ensuring the default Payment Success Rate reflects only orders that actually reached the payment stage. At the same time, the optional toggle preserves transparency by allowing comparison with the previous method. The added Product List filter ensure consistency across SCM report management tools.
Added
AnalyticsHistorical Test View Now Available in MVT Campaign Analysis You can now view historical MVT test results in Analyze > MVT Campaigns. This view helps you manually reconstruct comparisons for past periods when a test no longer appears in the standard test view because the control candidate was removed/changed or routing was edited after the test ran.
For more details, see the View historical test data section of the MVT Campaigns analytics document.
Why this is important: The Historical view gives you the flexibility to rebuild past comparisons even when the original test setup has changed. You can select which candidates to compare and assign any of them as the control baseline, making it easy to analyze performance for a specific period and answer “what performed better vs. what“ without being limited by the current routing or control configuration.
ApplicationsClient-Level Redirects for Rejected Refund Requests
We’ve enhanced the self-service refund flow to support client-specific redirects when a refund request is rejected because it falls outside the allowed refund criteria. Customers are now first shown the refund rejection page and can then use the Customer Service Team link to reach either the client-defined support page or, when no client URL is configured, Cleverbridge Help & Support.
We’ve also added tracking when a customer is redirected to a client support page after a rejected refund request. A history entry is added to the purchase so teams can measure the impact of these redirects.
For more details, see Request refunds article in the Self-service options section.
Why this is important: This update gives clients more control over the customer support experience for rejected refund requests, helping route customers to the right support channel and reduce Cleverbridge support requests.
Updated
CheckoutPaymentsCheckout 2.0 Now Supports Wire Transfers and ACH Credit
We’ve added wire transfer and ACH Credit as a supported payment methods in Checkout 2.0 for B2B checkouts. To get started with these payment methods, please reach out to our Client Experience department.
To see all supported payment methods, see Offer global payments
Why this is important: Wire transfer and ACH Credit are widely used by B2B customers. By supporting it in Checkout 2.0, B2B clients can now make use of our new checkout without losing critical payment options. This strengthens global payment coverage and supports continued checkout modernization.
Added
PaymentsCheckoutUPI is Now Supported for India
Cleverbridge now support UPI payments. UPI is a real-time payment system developed by the National Payments Corporation of India (NPCI) that allows sending and receiving funds instantly using UPI applications. The method is supported for both one-time payments and recurring payments. Recurring payments are performed through e-mandates (also known as UPI AutoPay)
To learn more, see UPI (India)
Why this is important: UPI is a leading digital payment method in India, and adding it can improve conversion by letting customers pay using a familiar, trusted flow. Supporting for both one-time payments and subscriptions, it helps expand subscription reach while keeping the checkout experience simple.
APIsProcessCart API Now Supports Internal PO Numbers
We’ve enhanced the ProcessCart API to support passing an internal Purchase Order (PO) number using the <CustomerReferenceNo> parameter. The value is stored on the purchase and appears in invoice records, invoice PDFs, and invoice emails.
For more details, see Process Cart API.
Why this is important: This update makes it easier for businesses to include their internal reference numbers during order creation, improving invoice reconciliation, accounting workflows, and purchase tracking for B2B transactions.
CheckoutDynamic Products Now Supported in Checkout 2.0
Checkout 2.0 now supports dynamic products, allowing you to define products dynamically during the checkout process using checkout parameters.
To learn more, see Dynamic products.
Why this is important: This gives you more flexibility to tailor checkout behavior at runtime, supporting use cases like dynamic catalogs, personalized offers, and automated product selection without requiring a fixed checkout setup for every product combination.
Updated
AnalyticsCore Metrics Widgets Now Expandable with Trends and Split Views
We’ve enhanced the core metrics area so that all four top widgets can now be expanded to review deeper details, including a trend line and the ability to split the view by a specific metric display: Value only or Value with comparisons (YoY, MoM).
The documents related to the Overview Business Review dashboard and Acquisition Business Review dashboard were extended correspondingly.
Why this is important: This makes it easier to move from a high-level snapshot to actionable insights—quickly spotting trends and validating changes over time (YoY/MoM) without needing to switch contexts.
Updated
AnalyticsReport Builder: New Dimensions, Comma-Separated Filters, and Compatibility Guidance
We’ve enhanced Report Builder with additional reporting options and clearer guidance when selected metrics and dimensions aren’t compatible:
- Renewal Type, Churn Type, and Client Group values can now be used to build and filter reports.
- Open Text Search filters have been enabled, allowing users to enter multiple values in a single filter field.
- A universal compatibility message now appears when the selected metric/dimension combination isn’t applicable. The message includes a direct link to the compliance search and matrix table (Available metrics and dimensions) to make sure users are aware of the limitation.
To learn more, see Create reports with Report Builder.
Why this is important: These improvements make Report Builder both more powerful and easier to use. Teams can build more relevant reports using new business-focused dimensions, apply multi-value filters faster with comma-separated input, and avoid confusion when certain metric/dimension combinations aren’t supported. The universal compatibility message, along with direct links to the compatibility resources, helps users quickly understand limitations and adjust reports without trial and error.
Added
CheckoutCheckout 2.0 Now Supports Session URLs (SURL) and Protected URLs (UURL)
Checkout 2.0 can now be launched using Session URLs (SURL) and Protected URLs (UURL) making it easier to start checkout sessions using masked links.
You can see all supported URL generation functions in the URL Generator API Guide.
Why this is important: This gives you more flexibility for link-based purchase flows (for example, from emails, in-app prompts, or support-assisted checkouts) while maintaining stronger control over how checkout sessions are initiated and protected.