v2.5.6 27-8-2026

🔍 Transaction Monitoring

Rule configuration, now editable in-app
Each monitoring rule has its own detail page where you can adjust parameters and set thresholds across a matrix of values. Every change is recorded in an audit log showing who changed what and when.

Role-based access for Transaction Monitoring
Transaction Monitoring permissions are now part of the standard permission set, with sensible default role mappings applied to your organisation automatically. Administrators can grant or restrict access to alerts, cases, and rule configuration per role.

🪪 KYC Renewal

Automated expiry tracking and self-service renewal
KYC records are now monitored for upcoming expiry automatically. Customers can regenerate their KYC through the portal as the expiry date approaches or once it has passed, so renewals no longer require manual intervention from your team.

🔗 Customer Portal

Choose how verifications are accessed
You can now configure whether verifications are available through internal (local) access, a public link, or both — giving you control over who can initiate a verification and how.

Notes on locally created cases
Reviewers can add notes to cases created through local verification, keeping context and decisions alongside the case record.

🗄️ Data Source Connections

Support for MySQL and PostgreSQL
Transaction data can now be pulled from both MySQL and PostgreSQL databases. When saving a connection, the platform validates it immediately and tells you if the details are incorrect, rather than failing silently later. Connection credentials are encrypted at rest.

🛠️ Fixes

• Relationship graph — Entities with a single association no longer open an oversized default graph view.

• Webhooks — Webhook events are now delivered correctly following a qualified rejection.