A definitive answer for every member, with nobody on your team in the loop

• The member alert lookalike

  "Unusual sign in on your account" from yourcu-alerts.com with your logo. It passes authentication for the attacker's domain. Forwarded to verify@, it comes back Not verified, and the domain is an indicator before the second member calls.

• The shared branch confusion

  Your members get real mail from partners, processors, and card vendors and cannot tell it apart from a lure. Register the vendor stream through the journal path and those messages verify too.

• The text to email pivot

  A lure arrives by SMS and points at a page that emails a "confirmation". The emailed confirmation is not in your registry. The web verify page answers in seconds. SMS itself, with the same code in a shorter footer, is on the roadmap.

• The copied footer

  A lure that copies your verify footer comes back Not verified and raises a replay flag. Attackers teach your members to use verify@, and then deliver their own lure to your fraud team through it.

• Five people, thousands of members

  A small fraud and security team cannot triage every "is this real" email. Submissions arrive with the signals, the indicators, and a verdict already attached, and the reply already went out.

• The "is this real" call

  Each one costs roughly $8 to $15 and the agent cannot answer with certainty. Every member who forwards to verify@ instead is a call that did not happen.

1. 01

   Fraud and card alerts

   The stream members scrutinize most. The best first stream for a pilot; register it from the ESP webhook or with a single call at send time.

2. 02

   Account and transaction alerts

   High volume, template driven, and where lures most often imitate you.

3. 03

   Loan and payment notices

   Auto loan, mortgage, and payment due notices from the loan servicing platform, registered through the journal BCC path when the vendor cannot call an API.

4. 04

   Statements and e-notices

   Batch runs through the batch endpoint, or a journal target on the statement vendor's sending system.

• Fewer calls, fewer tickets

  Contact center "is this real" volume and abuse mailbox volume on the pilot stream, before and during, reported at day 30, 60, and 90.

• Analyst hours back

  Suspicious message triage per week, before and during. Submissions come pre-extracted and pre-decided; the analyst reviews and overrides, they do not parse.

• Earlier detection

  Time from first member submission to analyst confirmation of a campaign, and lookalike domains discovered from member forwards rather than from a monitoring feed.

• Fewer takeovers

  Account takeover events traced to phishing of the pilot stream, and the reimbursement and card reissue costs that follow them.

• Members who keep reading

  A verifiable footer on every alert gives members a reason to trust real mail, which protects e-statement adoption and digital servicing.

• Intelligence yield

  Indicators not present in your existing feeds, verified by your team, exportable as CSV or STIX for your gateway, SIEM, or takedown vendor.

Examiners ask how members are protected from impersonation and how the credit union responds. Fromenance gives you a documented, member facing control: verdicts are immutable, analyst actions are audited, registered communications carry a timestamp and a recipient hash, and retention is a setting you own. Reports export from the admin app. We give you the evidence; your compliance officer frames it under NCUA guidance.

1. 1

   Step 1: Week 0

   We sign the contract and the DPA and create your tenant. You publish one TXT record and one redirect rule. The wizard sends itself a test message and tells you when the rule is right.

2. 2

   Step 2: Week 1

   You register one stream and paste the footer into that template. Replies go out from your own domain. The first customers usually ask that week.

3. 3

   Step 3: Weeks 2 to 12

   It runs. We sit with your fraud lead for 30 minutes a week over Submissions and Indicators, and you get a report at day 30, 60, and 90.

FAQ

Questions we get on the first call

We have a five person team. How much work is this, honestly?

One TXT record, one mailbox with a redirect rule, one footer paste, and one ESP webhook or a single call at send time. The setup wizard walks through the six steps and sends a test message before you go live, and the docs give click by click steps for Google Workspace and Microsoft 365. After that the reply is automatic and the analyst's job is review.

How is it priced for a credit union?

Annual contracts banded by protected members. The small credit union band, up to 250K, is $20K to $40K per year for the Verification tier with 2 domains, 3 sources, 5 users, and 90 day retention. The pilot is a fixed fee credited to the first contract.

Does it help with NCUA examinations?

It gives you a customer facing fraud control with an immutable verdict log, an audit trail of every analyst action, and a written pilot report with before and during numbers. That is evidence for your program, not a certification.

What happens when a vendor message is not registered?

The member gets Not verified with the words "no registered communication matches", never "fraudulent". An analyst can mark it legitimate, which registers it retroactively and flags the coverage gap on that source so you can add the vendor stream.

Can members use it without email?

Yes. yourcu.org/verify takes pasted text, an .eml file, or a screenshot and renders the verdict on the page in your branding. No account, nothing to install.