Role permissions

We've introduced configurable role permissions so you can tailor access to your organisation’s needs directly in the interface under Access management.

You can now:

• Edit permissions for system default roles. 
• Create new custom roles with bespoke permissions.

Default roles & access:

• Manager: Full administrative access across all modules and settings. 
• Auditor: Read-only access to all modules for compliance review. 
• Analyst: Broad read/write access across configuration modules (Risk Setup, processes, groups, transaction types, rules), with restricted access to sensitive areas (API Keys, Member Management) and no write access in Risk Monitoring or Case Management. 
• Developer: Full access to manage technical integrations (API Keys) without visibility in other modules.
• Operations support: Full operational access to Risk Monitoring, Entities, Reports, but no Risk Setup access and no ability to generate Police Reports.

Under each role configuration you can now view and manage assigned members and API keys, in addition to traditional management via the Members and API Keys sections.

MCC rule

A new Merchant Category Code (MCC) rule has been added to monitor transactions by MCC.

With this rule you can:

• Define a list of MCCs to block. 
• Automatically generate pings when a transaction contains an MCC from your blocklist.

Case deadline

We've introduced Case Deadline, a new feature that helps teams manage time-sensitive work more efficiently by having the system automated setting the deadlines of cases based on what rules have been triggered.

Rule-based deadline offsets 

Assign a deadline offset to a rule. When triggered, a ping will automatically receive a deadline derived from the offset and its creation time.

Example: Rule with a 7-day offset triggered at 12:31 on 3rd of March, will have a deadline of 12:31 on the 10th of March.

Automatic deadline inheritance 

When multiple pings are grouped into a case, the case inherits the earliest ping deadline.

Example: Ping 1=3-day deadline, Ping 2=7-day deadline, Ping 3=30-day deadline
→ Case deadline will automatically be set to 3 days.

Manual adjustments 

You can always manually update the case deadline directly in a case, or in the pop-up when changing a case’s status, allowing you to change the deadline based on your actions and internal procedures. 

Case list enhancements 

A new deadline column has been added to the case list, which can be sort by deadline to prioritise work. And visual deadline indicators have been added to the list:

• Orange: Case deadline is within 2 days 
• Red: Case deadline is within 24 hours 
• Red (Overdue): Case deadline has passed 
• Plus, a live countdown (time remaining) is shown beside the deadline

Standard reports in interface

We’ve updated our library of standard reports, to better meet our clients needs of insights into system activity over time. Standard reports are available for the interface to generate on demand, with pre-configured input filters. 

Standard reports available:

• Number of unique initiators - Provide the total number of unique initiators for a selected time interval. This report can, for example be used to analyse the total number of unique individuals making a payment for a given timeframe.
• Case overview - This report provides an overview of all cases created in the system for a selected timeframe, including case status and lifecycle. It offers a quick overview of cases and insight into the case flow.
• Entity overview - Shows all entities created during a selected time interval, and the report can be generated based on optional user-added filter (entity type, groups and/or risk classes)
• Entity transactions - This report provides a detailed overview of each entity's transaction activity within the selected time period, including total volumes, frequency, and active days for incoming, outgoing, and processing transactions in the specified currency.
• Entity report - Provides a detailed, entity-specific overview for a selected entity. The report consolidates all activity related to that entity, including associated requests, triggered pings, created cases, custom connections, screening reports. and group assignment history. It offers a complete activity summary to support investigation, analysis, or audit purposes.
• Group duration - This report calculates the number of days between two specified group assignment events, assigned or unassigned, on each entity within the selected time range.
• PEP & Sanction hit (threshold variation) - This report lists all individuals created after a selected date and shows the individuals PEP and Sanction match probability.
• Ping overview - Provides and overview of all Pings triggered by all, or user selected rules, during a selected timeframe. Additionally, the report can be filtered to only shows simulated Pings triggered by test rules, which is useful when validate rule logic or checking sample triggers.
• Request overview - This report provides an overview of all request sent to the system for a selected timeframe, and the report can be generated based on optional user-added filter (input parameters). One row per request matching the filter criteria.
• Risk distribution - This report provides an overview of entities per assigned risk class.
• Rule overview - This report provides a summary of rule versions and configurations within the selected range.
• SFSA regulatory report - Provides summary data related to Swedish Financial Supervisory Authority (SFSA) reporting, e.g., entity counts by region or risk.

Webhooks

We have introduced Webhooks, enabling real-time event notifications from Pingwire to external systems.

Webhooks allow you to automatically send data to a specified endpoint when certain events occur, such as when a group assignment is done on an entity in Pingwire. This makes it easier to integrate Pingwire with your internal systems, workflows, or third-party tools, without manual exports or polling.

Webhooks help streamline automation, and ensure your systems stay in sync.

Update Ongoing due diligence rule

The Ongoing Due Diligence (ODD) rule has been enhanced to include group assignment date as a time anchor.

The Ongoing due diligence (ODD) rule has been enhanced to include group assignment date as a time anchor. A time anchor in this context refers to an event that is considered the start of the period of which the rule is counting/monitoring. The available time anchors in the ODD rule is:

• Entity creation date
• KYC approval date
• Last form submitted date
• Group assignment date

This lets you define time-based triggers from any of these events to create pings at the right intervals.

Form configuration directly in the interface

We have introduced the ability for users to view and configure basic form settings directly within the Pingwire interface. The functionality is available under Administration → Forms in the sidebar.

Users can now access form details, including:

• Form ID 
• Language 
• Creation date

In addition, the following configuration options are available directly in the interface:

Light integration settings

• Edit form titel
• Configure URLs to whitelist 
• Define allowed iframe parent origins 
• Choose whether the form should be submitted as a request 
• Select which process the submission should trigger

Welcome page configuration

• Set/edit the welcome page title 
• Set/edit the welcome message

Thank you page configuration

• Set/edit the thank you page title 
• Set/edit the thank you message

This enhancement provides greater transparency and flexibility, allowing users to manage basic form setup and presentation without external configuration or support involvement.