For fraud, payments & risk leadership
Your controls asked whether the person was allowed in, and whether the activity looked unusual. Neither question catches a payment whose recipient details changed after it was authorized. CapchaCloud answers one question the rest of the stack does not: do the final payment details still match what was actually authorized?
CapchaCloud does not move funds, does not block payments, and does not decide anything. It returns a comparison and a receipt. Your people make the call.
Business email compromise does not look like an intrusion, because it usually is not one. Nothing gets hacked. A legitimate person, correctly authenticated, is persuaded to send money to the wrong place — or a correct instruction is quietly altered somewhere between approval and execution.
These are complementary controls, not competing ones. Authentication, risk analytics, and case management are each necessary, each mature, and each good at what they were built for. The table below is about scope, not quality — CapchaCloud is the fourth column, not a replacement for the first three.
| Control | Question it answers | Output | Timing |
|---|---|---|---|
| Authentication & access | Is this person who they claim to be, and are they permitted to act? | An allow or deny decision on access, plus a session. | At sign-in and at step-up, before the payment exists. |
| Risk scoring & behavioral analytics | Does this activity look anomalous relative to expected patterns? | A score, a rule hit, or a ranked alert for human review. | Continuously, and at submission of the transaction. |
| Case management | How should a raised alert be triaged, investigated and dispositioned? | A workflow, an assigned owner, an investigation trail, a disposition. | After an alert exists, on the investigator's clock. |
| CapchaCloud | Do the final payment details still match what was actually authorized? | A field-level match or mismatch, plus a sealed Evidence Record you can verify without trusting us. | Between authorization and release, while the payment is still recallable. |
A note on honesty: nothing here computes a fraud score. CapchaCloud has no model, no classifier and no anomaly engine in this path. The comparison is deterministic — details are normalized and compared, and the result is a match, a mismatch, or a pending confirmation.
Most vendors ask a bank to accept their word about what happened. CapchaCloud is built so you never have to. Every Evidence Record is cryptographically sealed, and its integrity can be checked by your own people, on your own hardware, with no call back to CapchaCloud.
The verifier is a standalone script with zero dependencies beyond Node 18 built-ins. Download it once, review the source, and run it against any evidence bundle. It re-derives the hashes and checks the signatures itself.
curl -O https://capchacloud.com/verify-evidence-bundle.mjs curl -o bundle.json "https://capchacloud.com/api/v1/public/evidence-bundle/<id>" node verify-evidence-bundle.mjs bundle.json
A second verifier re-derives every block in the append-only ledger independently. Walkthrough and live chain state: public chain explorer. Live anchor status: /api/v1/transparency.
This matters in a dispute. An Evidence Record that only CapchaCloud can vouch for is worth very little to a bank's counsel. One that your own examiner can re-derive from the bytes is a different kind of artifact.
This is the part procurement cares about most, so it is worth being blunt about it. CapchaCloud is not in your payment path, not in your ledger, and not in your authority chain.
CapchaCloud does not execute, custody, hold, transmit, or settle money — for anyone, in any product. Every response from the verification gate carries a standing advisory note stating exactly that, so the boundary travels with the data instead of living only in a slide.
A mismatch marks CapchaCloud's own record as not released and seals a receipt saying why. Nothing reaches into a payment rail, a core system, or a queue. Your systems remain the only thing that can stop or send a payment.
CapchaCloud returns a comparison and a receipt. An authorized bank employee reads it and decides to release, hold, or escalate. There is no automated action, no auto-decline, and no place where our software substitutes for your judgment.
Illustrative — synthetic data
The record below is a rendering with invented values, shown to make the shape concrete. It is not a real customer record, not a real payment, and not a screenshot of a bank deployment.
Four states are sealed independently and cross-linked: submitted, verdict, confirmation, final.
| Field | Sealed at authorization | Independently re-stated at confirmation | Result |
|---|---|---|---|
| Recipient name | NORTHRIDGE FABRICATION LLC | NORTHRIDGE FABRICATION LLC | match |
| Recipient account | ••••4471 (SHA-256 of full number held; number itself never stored) | ••••9038 | mismatch |
| Amount | USD 184,200.00 (sealed at authorization) | not re-stated by confirmer | unchanged against sealed record |
| Confirming party | — | approver_ref: ops-4412 | recorded |
The account comparison is a hash comparison. The confirming party types the account number independently rather than reading it back from the instruction, it is normalized and hashed, and the hashes are compared. The full number is never written down on either side of the comparison — only a SHA-256 hash and the last four digits are persisted.
Result: mismatch on recipient account. CapchaCloud's record is marked not released and a receipt is sealed stating the reason. No payment was stopped by CapchaCloud, and no funds were touched by CapchaCloud. The receipt goes to an authorized bank employee, who decides what happens next.
Only figures we can point at directly. Each is linked to the publishing body so your team can check it rather than take it from a vendor page.
Source: Federal Bureau of Investigation, Internet Crime Complaint Center — 2025 Internet Crime Report (PDF). Figures are reported losses from complaints received by IC3; they are not an estimate of total losses economy-wide.
Source: Deloitte Center for Financial Services — Deepfake banking fraud risk on the rise. These are projections by Deloitte, not measurements, and not a forecast of losses this product would prevent.
We would rather be measured than believed. So the first step is not a contract, a pilot, or an integration — it is an evidence exercise run entirely on history that has already happened.
A closed, historical window of already-resolved payment activity — authorization records and release records for a period that is finished and settled. Scope, field set, format, and any de-identification are yours to define before anything is shared.
A count of authorized-versus-released detail mismatches we would have surfaced before release, in your numbers rather than our projections — with the specific records named so your team can check each one against what actually happened.
Described in capability terms. The third parties that process data on our behalf are named in full in the Subprocessors Policy — we publish that list rather than obscure it, and it is the right document for your vendor-risk team.
Full detail: Trust Center · Security overview · Data residency · Data Processing Addendum
CapchaCloud receipts carry their own limits with them — a standing advisory note on every verification-gate response, and an explicit does_not_prove list on the receipt types that publish one. A record that overstates itself is worse than no record, so the same discipline applies to this page.
You are going to find this out in diligence, so you should hear it from us first.
No. CapchaCloud never executes, custodies, holds, or moves funds. Every response from the verification gate carries a standing advisory note saying so. The bank's own systems move money; CapchaCloud only compares details and seals a record of the comparison.
No. CapchaCloud records a verdict on its own record — matched, mismatched, or awaiting confirmation — and returns it with a sealed receipt. Nothing in CapchaCloud reaches into a payment rail. An authorized bank employee decides whether to release, hold, or investigate.
No. There is no score, no model, and no classifier anywhere in this path. It is a deterministic comparison: the details a confirming party independently re-states are normalized and compared against the details sealed at authorization. The result is a match or a mismatch, plus evidence of the check.
Yes. That is the point. Download the standalone verifier and the evidence bundle and run the check offline, on your own hardware, with no network calls to CapchaCloud. The verifier re-derives the record hash, checks the signatures, and checks the record's inclusion in the append-only ledger.
Yes, two ways. A retrospective audit runs entirely on a closed, historical window of already-resolved payment activity and touches no live workflow. Shadow mode runs the comparison alongside your existing process without gating, blocking, or altering anything in the live path.
No. CapchaCloud is pre-certification for its own SOC 2 Type II report and holds no ISO 27001 or PCI certification of its own. We publish that plainly rather than implying otherwise. Current posture is documented in the Trust Center.
← Home · Evidence methodology · Crypto inventory · Trust Center · Explorer · Support