Anansy powers banks’ own “Forward to Verify” fraud services. Customers forward suspicious texts to your short code and get an instant, branded answer. No call. No hold. No Anansy name in sight.
Every fraud tool on the market analyses message content — suspicious links, odd language, unusual patterns. Educated guesses. Anansy doesn’t guess. We check whether the bank actually sent it. Yes or no — not probably.
Banks currently tell customers: “If you receive a suspicious message, call us on 0800 xxx xxxx.” Anansy changes that to: “Forward this message to [1234] for an instant check.”
The customer never sees the Anansy name. It’s the bank’s service, their branding, their customer relationship. Anansy is the invisible infrastructure underneath — the same way Visa is invisible when you tap your Barclays card.
In rare cases where forwarding has altered the text, we say “call us to be safe” — routing any doubt to the bank’s human team rather than ever giving a wrong answer.
When a customer gets a suspicious text, every outcome costs the bank money. Ignore it, click it, or call about it — there’s no free option today.
Banks send messages through services like Twilio or Sinch. Anansy adds one webhook alongside the existing pipeline. One line of code. No rebuilds.
Anansy saves banks money in two distinct ways. Together, they compound. All figures per bank, per year.
Anansy never sees, stores, or has access to bank customer messages. This isn’t a promise — it’s how the system is built.
The bank creates a digital fingerprint on its own systems using SHA-256 cryptographic hashing and sends only that fingerprint to Anansy. We never get the actual message. When a customer forwards a suspicious text, we fingerprint it, compare, then immediately delete it.
If someone hacked Anansy, they’d find random letters and numbers. No names, no messages, no account details. Nothing usable.
For banks evaluating us, this removes the data protection concern entirely. There’s no customer data to protect. The usual months-long data review shrinks dramatically. This is a design choice, not a privacy policy. You can’t breach what doesn’t exist.
The first question any bank will ask. A bank could build the hash matching. But “could build” and “should build” are different questions.
| Existing Solution | What It Protects | The Gap | Anansy |
|---|---|---|---|
| BioCatch, Featurespace | Bank’s payment systems | Cannot verify messages before customer acts | ✓ Verifies at the message |
| Proofpoint, Mimecast | Bank’s email infrastructure | No presence in SMS channel | ✓ SMS + WhatsApp |
| Confirmation of Payee | Payment destination | Customer already convinced by the time they pay | ✓ Upstream of payment |
| Phone hotline | Customer enquiries | £8/call, 10 min wait, no lasting value | ✓ 10-second automated check |
A convergence of UK regulatory action has created conditions that didn’t exist 18 months ago. Every month without proactive fraud prevention is a month of avoidable liability.
One bank gets full value immediately. As more banks join, intelligence compounds. A scam targeting one bank becomes a known threat for all.
We’re inviting a select group of UK challenger banks and building societies to join our early pilot programme. First pilot live in 6–8 weeks. Every bank after that: 2–4 weeks.