Management API: Case group included in case webhooks
CASE_OPENED and CASE_CLOSED webhook payloads now include the case's group, so you can route or label cases by type (for example, onboarding vs. KYC) in downstream systems without a separate lookup.
Key updates include:
Case group is now part of the
CASE_OPENEDandCASE_CLOSEDwebhook payloads.
You can find it on our latest docs linked here
Compliance: STR Filing for FINTRAC now support all transactions on a case
We have now made it easier for you file STRs. When you start a draft to create an STR for a case, all transactions linked to the case are automatically pulled in.
In addition, we have made the following enhancements:
"Apply to all" option available for starting and completing action details (account information, direction, type of funds, account status, and disposition)
Screening: BIC/SWIFT code screening supported on KY6 and DOW jones
You can now screen BIC/SWIFT codes directly against KYC6, Dow Jones database. Previously, screening covered name, bank name, and reference fields only, so codes couldn't be matched.
Key updates include:
BIC/SWIFT screening available as a screening field, matched against the database
Existing screening rules can be migrated to include BIC/SWIFT matching.
Follow these steps below to try it out:
1. Open a template screening rule - R-169/R170
2. You can pick BIC as a screening field options under rule parameters
Screening: Exact stopword matching
You can now set stopwords to match exactly instead of fuzzily. Fuzzy stopword matching could unintentionally suppress legitimate names (for example, the stopword "Pte." affecting a name like "Pete"); exact matching avoids this.
Key updates include:
New option to apply stopwords as an exact match, with no fuzziness.
Screening: Separate "Exact match" and "Exact match with empty values" operators
Exact match and exact match including empty values were previously the same operator. They're now separate, so you can choose whether empty or null values should count as a match.
Key updates include:
Two distinct operators: "Exact match" and "Exact match (with empty values)."
Existing rules are unchanged; the previous behavior (exact match including empty values) remains the default.
Screening: Sort hits by fuzziness
Screening hits can now be sorted by their fuzziness score, so the strongest matches appear first and are quicker to review.
Key updates include:
Sort screening hits by match/fuzziness score.
