High-value transaction rule
A high-value transaction rule detects a single transaction whose amount exceeds a configured limit, so that unusually large movements of money are reviewed. It is the simplest amount-based rule, and it is deliberately blunt: it knows nothing about the account's history, only the size of this payment.
The fraud scenario this rule addresses
A fraudster who has gained access to an account or a card wants to extract as much value as possible before the victim notices. A large single transfer or purchase, particularly to a new destination or a high-risk merchant category, is the fastest way to do it.
The same rule also supports compliance work, since large payments are often the ones a regulator expects to see reviewed, even when nothing about them is fraudulent.
Data the rule requires
- Transaction amount
- Currency, with an exchange rate to a reporting currency where limits are set in one currency
- Account identifier and account type
- Transaction type or channel
- Beneficiary or merchant identifier
Example logic
Illustrative pseudocode: it compares each event with the rule's parameters and flags the ones that match. Parameters are symbolic: every value is institution-specific and has to be derived from your own transaction distribution.
RULE high_value_transaction
FOR EACH event E:
limit = lookup(:limits, segment = E.account.segment,
channel = E.channel)
amount = convert(E.amount, E.currency, :reporting_currency)
IF amount >= limit:
RAISE alert(rule = "high_value_transaction",
account = E.account, evidence = E)
Choosing a threshold
The single parameter is the limit, but the real decisions are what the limit is applied to. A limit applied across every account type will either miss fraud on small retail accounts or bury analysts in alerts from business accounts, where large payments are routine. Setting limits per segment and per channel is nearly always needed.
Set too low, the rule fires on ordinary rent, tuition and supplier payments and stops being informative. Set too high, it sits well above anything a typical retail victim holds, so it never protects the accounts most often targeted. A fixed limit is also trivially learned: an attacker who finds it can split the transfer below it, which is why this rule is paired with velocity and unusual-amount rules rather than relied on alone.
Currency matters. A limit stated in one currency drifts in meaning as exchange rates move, so decide whether limits are fixed in the transaction currency or converted to a reporting currency.
False positives to expect
Legitimate large payments are frequent: a property deposit, a tuition fee, a business paying a supplier invoice, a customer moving savings between their own accounts, an annual insurance premium, or a one-off purchase such as a vehicle.
Most of these are known in advance by the customer. A review step that contacts the customer, and an exemption for beneficiaries with a clean payment history, reduces repeat alerts for the same legitimate payee.
Investigating an alert from this rule
- Check the amount against the account's history. A payment the account has made before at this size is a different case from a first.
- Check the beneficiary: is it an established payee, a new one, or one that has been reported before?
- Check how the payment was initiated: the device, channel and location, and whether they match the account's normal pattern.
- Look for a stated purpose or reference, and whether it is consistent with the beneficiary.
- Contact the customer through a channel you already hold for them, never one supplied in the payment instruction, and confirm they made it.
- Record the decision and, if the payment was legitimate, note the beneficiary as expected so it does not alert again.
Related rules
Where this rule fits
The use case this rule supports is covered in payment fraud, and the fraud rules engine page describes how conditions like these are expressed and versioned.
Common questions
What is a high-value transaction rule?
A high-value transaction rule is a fraud rule that raises an alert when a single transaction is larger than a configured amount. It is the simplest amount-based control, applied to one payment at a time. Because it ignores the account's history, the limit is normally set separately for each customer segment and channel.
A single global limit performs badly. It either misses fraud on small retail accounts or generates constant alerts on business accounts where large payments are routine, so the limit is normally tied to the segment.
The rule is easy to evade by splitting a payment into smaller ones, so it is usually used together with velocity rules and with rules that compare a payment against the account's own typical amounts.
Discuss your transaction monitoring requirements
Tell us which transaction flows you need to monitor, which systems Akoben would integrate with, and how your fraud team works today.
Request a demo