HomeDocumentationRecipesAPI ReferenceChangelog
Platform OverviewDemoContactImprintLog In
Changelog
Platform OverviewDemoContactImprint
Back to All

Release 2026-11-05

November 9th, 2026

  1. New Payment Intent API

    We introduced a new Payment Intent API with payment variants, in preparation for pay-by-link and capture-only. Pay-by-link is a payment through a link. Capture-only means the payment was authorized before it reaches instellix, and instellix only captures that authorization.
    We deprecated the previous Payment Intent API because it cannot represent these variants. It remains available until 27 October 2027 at the latest.
    The new API is documented here: https://docs.instellix.io/reference/querypaymentintents

  2. Final payment retry at month end

    Payment provider retry schedules for Adyen and Stripe now support the type DAY_OF_MONTH_UNTIL_MONTH_END. With this type, a failed retry on the last configured day of the month is the final attempt, even when Max Retry Attempts has not been reached.

  3. Dunning level on OPOS Case updates notification

    The oposCase.updated notification now includes the current dunning level of the OPOS Case in the field dunningLevel. The value is null when no dunning level is active, and it uses the same format as oposCaseDunning.issued. This applies to OPOS Case dunning only. Existing notification payloads stay valid.

  4. Adyen settlement booking date

    Adyen settlement items now use the Booking Date from the Settlement Details Report when that column is included in the report. Previously, the creation date was also stored as the booking date. If the report has no booking date, the creation date is still used.

  5. Dashboard Widgets from a Metric

    Dashboard Widgets can now be created based on Metrics, allowing greater flexibility in displaying key business data. Existing Metrics can be added to the Dashboard as Widgets and configured with different visualization types, time spans, and comparison periods. This makes it possible to customize the Dashboard according to individual reporting needs.
    The new Metric-based Widgets will gradually replace the existing Dashboard Widgets, providing a more flexible and consistent way to visualize business data.
    For more information, see Dashboard & Widgets and Metrics.

  6. Deprecation of Legacy Dashboard Widgets

    Existing Dashboard Widgets will gradually be deprecated and replaced by the new Metric-based Widgets, which offer more flexibility in displaying and configuring business data. Widgets that will no longer be supported will be marked as Deprecated on the Dashboard, including information about their planned deactivation date.
    During the transition period, affected Widgets will continue to display their existing data. However, they can no longer be edited, and new Widgets of these types cannot be created.
    Instructions for creating new Metric-based Widgets are available in the documentation under Dashboard & Widgets.

  7. Usage Records for Metered Usage Credit Notes

    Usage Records are now also available for Credit Notes containing canceled Metered Usages. When a Credit Note is created, a Usage Record can be generated automatically based on the configured Document Provisioning settings. Both Metered and Combined Usage Record configurations are supported.
    This provides a detailed record of canceled usages, making it easier to trace which usages were credited and may subsequently be included in a new invoice. All values, including quantities, are displayed as positive numbers, as the Credit Note itself indicates the cancellation.
    For more information, see Usage Records.