The honeybot intercepts before the transfer confirms.
A step-by-step walk through how AVIEL's AI agent enters the fraud conversation, stalls the scammer, and hands your fraud ops a complete profile.
From scammer contact to fraud ops alert
Every interception follows the same sequence — invisible to the customer, invisible to the scammer, fully logged for your fraud ops team.
Customer receives contact from a scammer
The scammer impersonates a bank, utility, or investment platform. They establish trust via SMS, in-app message, or email thread. The customer begins to respond — and starts to believe.
AVIEL trigger fires on unusual payment intent
Your PSP stack sees a payment intent forming outside normal behavioral patterns. AVIEL's webhook listener flags the session. The trigger is silent — no visible change for the customer or scammer.
Honeybot injects into the communication channel
AVIEL's AI agent enters the conversation thread, presenting as a legitimate verification or hold step. The customer sees only a standard confirmation delay. The scammer continues engaging — with AVIEL.
Scammer engages — gets fingerprinted
The honeybot adapts its conversation style to match the scam type — investment fraud, impersonation, romance. It stalls with plausible friction while capturing device fingerprint, phone number metadata, message cadence, and language patterns.
Fraud ops receives real-time alert with full profile
Your fraud ops queue receives a structured alert: scam type classification, intercept timestamp, stall duration, scammer device hash, phone number, conversation graph. Transfer flag issued. The customer never confirms. The scammer never collects.
The honeybot is a trained AI agent, not a rule.
A rule-based response system can be learned and detected. A fixed template gets fingerprinted. The AVIEL honeybot is a fine-tuned conversation model — it adapts response cadence, friction level, and vocabulary to match the specific scam type (investment impersonation, authorised bank transfer, HMRC, romance). The scammer can't distinguish it from the PSP's legitimate hold process, which is precisely what keeps them engaged long enough to expose their device and communication fingerprint.
Technical Specification
