Blnk Watch is currently in beta. Send us a message
meta_data and reference it in the rule.
Watch scripts
Rules are written as watch scripts: plain-text files with the.ws extension.
Watch loads these scripts from a designated folder (by default watch_scripts), compiles them, and turns them into the rules that run against each transaction.
When you add or change a .ws file in that folder, Watch picks up the change and updates the active rule set.
Rule anatomy
Every rule has two core parts: when (the pattern) and then (the outcome). The rest of this section walks through each piece and where to learn more. A simple, complete rule looks like this:HighValueUSD.ws
Keep in mind: When you need information that isn’t part of the transaction payload, include it in
meta_data first. A rule can use meta_data.kyc_tier or meta_data.promo_code only if your app sends those values with the transaction.Rule syntax
First, you declare the rule. The name afterrule must be a single identifier in camelCase or snake_case (e.g. HighValueUSD, burst_to_same_destination) and should describe the pattern or control so it’s clear in logs and audits.
ruleName.ws
ruleName.ws
ruleName.ws
ruleName.ws