Overview - Heron

Heron sees more than 60k funding submissions a day across the lenders and brokers on the platform. Fraud Detection checks each submission you send against two signals. Each is enabled separately.

Signal	What it detects	Enricher name	Availability
Fraud network	The applicant, its owners, or a business linked to them has an early default (< 10% RTR) reported by a consortium member, or is in a ring Heron found moving money between businesses.	`fraud_network_scan`	Heron Fraud Consortium members
Broker velocity	The same merchant has been submitted by an unusual number of brokers in the last 24 hours, and the highest that count reached for the same owner over the last 30 and 90 days.	`broker_velocity`	Enabled per account

Contact your Heron rep to enable either.

How they work with your submissions

Both run inside your Heron workflow, so you integrate by sending submissions as usual:

Send the submission by email or over the API (Quickstart), with its ISO application.
Heron reads the business and owner details from the application and the other documents you send.
The checks run when your workflow reaches them. Your Heron policy can route a flagged deal to review or decline it.
You are notified by the enricher.succeeded webhook, and read each result from the endpoint on its page.

Testing

Each page has a testing section with reserved identities that return a sample result, so you can build and test your integration without real data:

Outcome	Business legal name	Owner	Fraud network	Broker velocity
Fraud ring	`HERON SANDBOX FRAUD RING LLC`	`HERON SANDBOX` `FRAUD RING`	`status=match`, `classification=fraud_network`	`high`
Lone actor	`HERON SANDBOX LONE ACTOR LLC`	`HERON SANDBOX` `LONE ACTOR`	`status=match`, `classification=lone_actor`	not run
No fraud	Any other made-up name	Any	`status=no_match`	live count

Each signal only returns a result if it is enabled for your account.

⌘I