QATCH.ai FAQ

QATCH.ai is an AI-powered wire-verification layer for title, escrow, and high-stakes B2B payments. Add your QATCH inbound address to a wire-request email thread — either from the first message (recommended) or by forwarding once something feels off — and our engine reads the conversation, runs a multi-signal verification, and replies with a verdict you can act on. Phase 1 (today) ships verification-only; Phase 2 (coming Q3 2026) adds escrow execution and approved-fraud insurance.

Real estate wire fraud, also called business email compromise (BEC) at closing. The FBI's Internet Crime Complaint Center reported $446M in real-estate BEC losses in 2024, growing 38% year over year. The most common attack: a typo-squat domain joins a legitimate email thread mid-conversation and quietly introduces new wire instructions. Single-address verification tools clear it; the fraud goes through. QATCH reads the whole thread and catches the impersonation.

Year-1 target customers are title companies, escrow agencies, and real-estate-adjacent law firms in the United States. Year-2 expansion targets mid-market accounts-payable teams and construction general contractors. The common pattern: businesses that wire substantial dollar amounts to new counterparties on a daily or weekly basis, where the recipient changes frequently and BEC pain is acute.

QATCH and CertifID are complementary, not competing. CertifID verifies the wire recipient's identity at the point of sale via KBA — useful against account takeover at the recipient's bank. It can't see what happened inside the email conversation that produced the wire instructions. If a typo-squat domain joined the thread mid-conversation and introduced new bank details, CertifID will still happily clear the recipient who happens to be the fraudster. QATCH reads the thread. Most of our pilot customers run QATCH alongside their existing CertifID subscription as a second, email-side layer.

Bill.com is an accounts-payable automation platform — it processes invoices, schedules payments, and provides workflow automation. QATCH is built for the CFO + security persona at firms where wire fraud is an existential risk. Bill.com has lightweight fraud features; QATCH leads with email-thread fraud prevention as the core product.

No. QATCH supplements cyber insurance. Most commercial cyber policies exclude BEC losses entirely under 'social engineering' exclusions or sub-limit BEC coverage to $100,000–$250,000. Phase 1 of QATCH does not add insurance; we improve detection so fewer wires get to the loss stage. Phase 2 will add an approved-wire insurance guarantee for the wires we execute through escrow.

Two ways. (1) Loop us in from the start: add your QATCH address — your-org@inbound.qatch.ai — to the To: or CC: of the wire-request thread from the first message. We sit in the background and speak up only when we see something worth flagging. (2) Forward when something feels off: if you're already past the start, forward the suspicious email to your QATCH address. Either way, our engine reads the entire thread (including any quoted history) and replies with a verdict.

Our multi-signal engine is proprietary by design — we don't publish the specific tests so fraudsters can't reverse-engineer evasion. The categories of attack we flag include: vendor impersonation via typo-squat domains, mid-thread instruction changes, cold beneficiaries with no payment history, throwaway sender domains (recently registered, no mail infrastructure, parked sites), invoice/wire mismatches across any field, and the BEC linguistic playbook (urgency, 'do not call to confirm', last-minute account changes, AI voice-clone setup phrases). Your verifiers see the full reasoning behind every verdict in the portal.

An acknowledgment lands in the forwarder's inbox within ~1 second of receipt. The full verdict arrives in under 10 seconds for cleared wires. For wires that need human review, the engine replies with an interim 'under verifier review' notice and follows up with a final email once the human review completes.

In our design-partner data, approximately 5–8% of wires require human review. The remaining 92–95% clear via AI verification only. The rate is higher early on (less behavioral history) and decreases quickly as the beneficiary database for that customer's typical recipients builds up.

Your choice. (1) Your team's verifier role in the portal — included in your subscription. (2) A QATCH expert callback — uses one of your monthly credits (or overage). A QATCH analyst makes the verification call to a publicly-sourced phone number (never one from the email), documents it, and returns the verdict in ~30 minutes during business hours.

BLOCK means do not wire, full stop. The engine has caught signals consistent with active fraud. BLOCK is never overridable — no credit, no fee, no escalation will turn a BLOCK into an APPROVE. If you disagree with a block, contact QATCH support; we'll review the evidence with you, but the BLOCK decision stays in effect until the underlying signals are resolved.

Yes — this is one of the primary design goals. Traditional 'call to verify' defenses fail against AI voice clones because the scammer can spoof both directions of the call. QATCH catches the email-side setup of voice-clone attacks (the language used to prime the recipient, the urgency around 'I'm in a meeting, just confirm with the email instructions') AND requires callbacks to publicly-sourced phone numbers — not numbers provided in the email. Defeating this requires a much larger attack surface than compromising a single email account.

Three tiers in Phase 1, all with unlimited AI verification: Starter $199/month (3 expert callbacks included, $50 per additional callback) — for small offices under 30 closings/month. Pro $799/month (15 callbacks included, $35 per additional) — the typical title-firm tier. Enterprise — custom pricing, unlimited callbacks, dedicated success manager. Design partners get 14 days free with 3 callbacks included.

A callback is a QATCH-side analyst doing the verification call for you. Customer-side review by your own verifier role in the portal is included in your subscription and never counts as a callback. Callbacks are the explicit, metered service line; everything else is bundled.

No. Onboarding typically completes in 30 minutes. The initial behavioral baseline for your existing recipient list builds automatically as wires flow through.

Design partner pilots run for 14 days free with no commitment. Post-pilot, contracts are month-to-month with no annual minimum. We believe in earning the relationship every month.

Callback overage above your monthly allowance is billed monthly in arrears via ACH against your primary funding account. Subscription is billed monthly in advance. Detailed per-callback invoices are provided with every billing cycle.

AI-powered wire verification: forward or CC us on the email thread, get a verdict back. Multi-signal engine reads the full conversation, catches in-thread impersonation, flags suspect domains, and surfaces BEC patterns. Customer wires through their own bank after receiving the verdict. QATCH never holds or moves money in Phase 1.

Approved-wire insurance + escrow execution. Customers will be able to route the wire through a QATCH escrow account; we verify, we release, we back approved transactions with insurance (target: $2M per transaction, 30-day payout, no social-engineering exclusion). Phase 2 ships Q3 2026 subject to regulatory approvals (state money-transmitter licensing, reinsurance partner agreements). Design partners ride along when it ships.

Phase 1 is a pure software product — no money movement, no money-transmitter registration, no banking partner required. We can ship it now. Phase 2 (handling funds) needs licensing, reinsurance, and partner banks; that's months of legal/compliance work that shouldn't gate the verification product customers can use today.

Not in Phase 1. We are a software platform — we read email threads and return verdicts. No money movement, no custody, no MSB registration required. Phase 2 will operate on top of a Banking-as-a-Service partner that holds the underlying banking license; we will not be a bank in Phase 2 either.

Today (Phase 1) — no, and we don't need to. Forward the wire-request email or CC us; that's the integration. No new tool to deploy inside Qualia, RamQuest, or SoftPro. Enterprise customers can get a roadmap for native integration with their title platform as part of onboarding.

Phase 1 doesn't require accounting integration — wires happen at your bank, not inside QATCH. Phase 2 will integrate with QuickBooks Online, Xero, NetSuite, Sage Intacct, and Bill.com for invoice syncing once we add escrow execution.

No. Phase 1 doesn't touch your banking at all. Phase 2 will use a separate escrow account at QATCH's BaaS partner for funds in flight, but your primary banking relationship stays exactly where it is.

Phase 1 fails open at the customer's discretion — your bank wire capability is untouched. If the QATCH engine is unavailable, customers can still wire through their normal channels without the verification verdict. Published SLA target is 99.95% engine uptime. Sustained outages would surface in the inbound webhook errors and we'd notify directly.

SOC 2 Type I is targeted for Q3 2026; Type II by Q1 2027. Customers with strict procurement requirements can request our current security posture documentation under NDA.

Customer data is encrypted in transit (TLS 1.3) and at rest (AES-256). Email-thread content is retained for the regulatory minimum for financial-records review (typically 7 years) and offered for customer-controlled deletion after the retention period elapses.

We share anonymized beneficiary reputation signals across the customer network — if a recipient bank account has been involved in fraud at Customer A, that signal protects Customer B who later attempts to wire to the same account. Customer A's identity is never shared. Customer-specific email content and transaction data is never shared with any third party.

Customer can export their full transaction history and beneficiary database via API or CSV at any time. After contract termination, data is retained for the regulatory retention period (typically 7 years) then deleted upon customer request.

QATCH was founded in 2026 by a solo technical founder with a background in full-stack software, AI/ML, and embedded systems. Our team scales with customer count and revenue.

QATCH is headquartered in the United States and serves US-based customers only at launch. International expansion is on the Year-3+ roadmap.

QATCH launched with a small angel round and is self-funded toward cash positivity. We have not raised institutional venture capital as of mid-2026.

For design partner inquiries, use the application form on qatch.ai. For general questions: hello@qatch.ai. For media: press@qatch.ai. For BaaS or reinsurance partnership: partners@qatch.ai. We respond to every inquiry personally within one business day.