New beneficiary rule

A new beneficiary rule detects a payment to a payee the account has never paid before, usually in combination with a condition on the amount or the timing. A first payment to a new destination is a normal event for a customer and a necessary step for a fraudster, so the rule is rarely useful on its own.

The fraud scenario this rule addresses

To move money out of a compromised account, an attacker must send it somewhere. Unless they have found an existing payee they can reuse, they must add a new one, and then pay it, often within minutes of adding it. The addition of a beneficiary followed quickly by a payment to it is a recognised takeover signature.

The rule also matters for authorised push payment scams, where the customer themselves adds the new payee after being deceived. There the device and login are genuine, and the new beneficiary may be the only visible signal.

Data the rule requires

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 new_beneficiary_payment
  FOR EACH payment P from account A to beneficiary B:
    first_time = NOT EXISTS(prior payment from A to B)
    age        = P.timestamp - beneficiary_created_at(A, B)
    IF first_time
       AND P.amount >= :min_amount
       AND age <= :max_age:
      RAISE alert(rule = "new_beneficiary_payment",
                  account = A, evidence = P)

Choosing a threshold

Three parameters interact here: the minimum amount, the maximum beneficiary age, and whether the rule also considers beneficiary addition events. With no amount floor, every first payment to a new payee alerts, which on an active account is a large share of all payments. A high floor lets an attacker stay beneath it by sending small test payments first.

The age condition narrows the rule to the dangerous window: paying someone seconds or minutes after adding them. Make the age limit too short and an attacker waits it out, make it too long and the rule regains the noise it was meant to avoid.

Cooling-off conditions that depend on how the beneficiary was added, for instance through a trusted channel as opposed to a new session, change the balance considerably. They are a design choice in their own right, not just a threshold.

False positives to expect

New payees are a normal part of banking. Someone paying a new landlord, a tradesperson, a friend after a night out, a new employer's expenses contact, or a charity after a disaster appeal creates a new beneficiary as a matter of routine. Newly onboarded customers have no payee history at all, so every payment they make is to a new beneficiary.

Useful mitigations are a looser condition for new accounts than for established ones, weighing the new beneficiary together with the amount and the device, and recognising payees that other unrelated customers have paid for a long time without incident.

Investigating an alert from this rule

  1. Establish when and how the beneficiary was added, and from which device and session.
  2. Compare that session with the account's usual device and location.
  3. Check whether anything about the account changed shortly before, such as a password, contact detail or limit.
  4. Check the beneficiary: its account age, whether it has received payments from other customers, and whether it has been reported.
  5. Compare the amount with the account's history and with what is typical for a first payment to a new payee.
  6. If the payment looks customer-initiated, consider the scam possibility: contact the customer through a known channel and ask what the payment is for before drawing conclusions.

Related rules

Where this rule fits

The use case this rule supports is covered in account takeover, and the fraud rules engine page describes how conditions like these are expressed and versioned.

Common questions

What is a new beneficiary rule?

A new beneficiary rule is a fraud rule that flags a payment to a payee the account has not paid before, normally combined with a condition on the amount or on how recently the payee was added. A first payment to a new destination is a necessary step in most account takeover and scam cases, but it is also an everyday event.

Because new payees are routine, the rule is rarely used alone. It is usually combined with the amount, the age of the beneficiary record, or a change in device, so that it fires on the dangerous combination rather than on every first payment.

It is also one of the few signals available in authorised push payment scams, where the customer is genuinely logged in on their own device and the new payee may be the only visible anomaly.

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