broker_velocity enricher. See the Fraud Detection overview for how it fits with the fraud network.
Thresholds
Each band is a minimum count of distinct sending domains, set per account. The defaults are 5 forhigh, 4 for medium and 3 for low. Contact your Heron rep to change them, for example after a backtest on your own deals.
Integrating
Broker velocity runs inside your Heron workflow on every submission you send, so there is nothing extra to call.Prerequisites
- Submissions flowing into Heron, by email or over the API. See the Quickstart to send them over the API.
- Broker velocity enabled for your account and added to your workflow. Contact your Heron rep.
- Owner details on the submission, usually from its ISO application. Without them it is not run. Sole proprietors are not measured, and neither are submissions to broker accounts.
Act on it in your policy
A high band can route the deal to review or decline it. Policies read the Broker velocity variable (broker_velocity), which is High, Medium, Low or None. Sole proprietors read as None. It is missing when the deal has no owner information, your account is a broker, or the measurement did not run. Ask your Heron rep to add the check.
Read the result
Theenricher.succeeded webhook fires when it finishes, with enricher_name broker_velocity. Then fetch the result:
app.py
404 until it has run for the submission.
Understanding the result
The response is the band only. The brokers and the number of submissions are never shared.
Testing your integration
You can get ahigh result without real data. Create a submission with business legal name HERON SANDBOX FRAUD RING LLC and owner HERON SANDBOX / FRAUD RING, following the fraud network testing steps. Broker velocity returns high at your account’s high threshold and records no measurement.
Any other made-up identity runs the live count, so it usually returns no signal or is not run.