# July 15, 2026 — Dashboards, rule engine and issuer detection

This is the biggest update since the migration to the event platform. It brings customizable dashboards, a broad set of improvements to the rule engine, and improvements to issuing bank detection, in addition to new features in the API and the interface. Here are the details.

## Dashboards

You can now create custom **dashboards** to track what matters in one place. Each dashboard gathers **panels**, and each panel displays a metric with the dimensions and measures you choose.

- **Panel type** — choose between **Chart**, which displays the series over time, or **Value**, which displays the most recent number for each segment.
- **Dimensions** — choose a value for each of the metric's dimensions. Each value generates a series in the panel.
- **Aggregations** — select one or more of the metric's measures to display in the panel.
- **Granularity** — set the aggregation interval of the displayed data.
- **Default time window** — applied to the panels when opening the dashboard, and adjustable at any time through the period selector.

You can edit the panel layout, give each dashboard a name and a description (displayed as a subtitle), and organize as many dashboards as you need, within your plan's limit.

See the [dashboards documentation](/en/behavioral/dashboards/) for all the details.

## Rule engine

The **rules** engine received several improvements:

- **Version comparison** — compare two versions of the same rule side by side, highlighting what was added, removed, reordered, or changed.
- **Condition names** — give each condition a name to identify it clearly in the admin panel and in the analysis results.
- **Enhanced simulation** — when simulating a rule, the platform shows exactly which condition was met (or reports that none were met with the provided variables), along with the evaluated arguments.
- **`concat()` function** — combine variables and text into a single value, including in inclusion (`in`) and exclusion (`not in`) comparisons.
- **Syntax highlighting** — condition expressions are now displayed with syntax highlighting, and list references become direct links to the corresponding list.

See the [expression syntax](/en/transactional/expression-syntax/) for all the details of the rules language.

## Issuing bank detection

We made internal improvements to identifying the issuing bank of cards, and you can expect more matches. The platform still identifies the issuer from 6-digit BINs, but we recommend sending at least 8 digits to increase the match rate.

## Transactions and API

- **New `canceled` status** for transactions, available in the analysis and in the API. This new status represents transactions that were authorized but reversed before capture.
- **Rule details in the API response** — the [payments API](/en/api/methods/post_payments/) response now includes the details of the rule applied to the analysis.

## Interface and usability

- **Collapsible side menu**, with its state preserved across sessions.
- **Account switch warning** — if the current account is changed in another browser tab, the platform warns you before you continue, avoiding modifying data in the wrong account.
- **Filter by empty or filled fields** — filters gained two new operators that do not require a value: **Empty**, to find records where a field was not provided, and **Filled**, for those that have the field provided. Useful, for example, to isolate payments with no identified issuer. They are available in the filters of the analysis, reports, and exports screens.
- **Event export** — in addition to payments and transactions, you can now also export events.