The patterns, as the engine reads them
confidence 85 (high)
- Primary: Func_eu_debit_card: built-in matching logic that runs inside Purview. Browsable here, not yet testable.
- Any of these:
- Keyword_eu_debit_card: 5 keywords (word match), e.g. "account number", "card number", "card no."
- Keyword_card_terms_dict: 178 keywords (word match), e.g. "acct nbr", "acct num", "acct no"
- Keyword_card_security_terms_dict: 69 keywords (word match), e.g. "card identification number", "card verification", "cardi la verifica"
- Keyword_card_expiration_terms_dict: 41 keywords (word match), e.g. "ablauf", "data de expiracao", "data de expiração"
- Func_expiration_date: A date in a card expiration format such as MM/YY or MM/YYYY (approximated here with numeric forms).
confidence 65 (low)
- Primary: Func_eu_debit_card: built-in matching logic that runs inside Purview. Browsable here, not yet testable.
- Evidence: none required. The primary element alone decides the match.
Not available for live testing here. Part of this definition relies on a matching function this browser model does not implement, so a result would not be one we could stand behind. The anatomy above is still accurate, and the portal's own SIT test will evaluate it properly.
Related SITs
Others in the EU group.
Catalogue data reflects Microsoft's built-in SITs, which are the same in every tenant. This is a faithful simulation, not the live service, so confirm with the portal's SIT test before acting on a result.