• Datapoint conflict rule: You can now configure rules to trigger and create a ping when conflicts are identified on specific datapoints, such as name, date of birth, or beneficial ownership. 
   
• Multiple group assignment options: We’ve added several options for group assignment/removal in rule configuration: ‘None’, ‘On Ping’, ‘On Trigger’ and ‘On Execution’. 
   
• KYC approved field: Entities can now be marked as ‘KYC Approved’ either via the API or manually. This status includes a timestamp of when the approval occurred. This is separate from the ‘Created At’ field, which reflects when the entity was first registered in the system. 
   
• API endpoint for account status: A new API endpoint allows your systems to check whether a source account has been blocked. This supports pre-checks before initiating transactions or other operations. 
   
• New entity type - ‘Product’: We have introduced ‘Product’ as a new entity type, enabling monitoring of transactions related to specific products in isolation. Product entities can be linked to other entities, such as accounts, individuals, and businesses. 
   
• KYC Form setup for account and product entity types: KYC Forms can now be associated with specific accounts or products, allowing you to compare actual usage patterns against what users declared during onboarding. 
   
• Enhanced transaction monitoring mode: Transaction monitoring rules can now be configured to operate: 
  • On a global level (business or individual, including all connected accounts and products) 
  • On an account level 
  • On a product-only level 

This enables retrieval and analysis of transaction behavior per account or per product. 

• KYC Form status options: We’ve introduced optional status settings for KYC Forms, which can be used upon submission or during review. The available statuses are: 
  • Pending: Form answers submitted by the customer but not yet reviewed. 
  • Completed: Form answers reviewed and approved. 
  • Rejected: Form answers reviewed and declined. 
  • Withdrawn: Form answers submitted but later withdrawn by the customer. 
  • None: No specific status applied.