CapchaCloud × VeraBank

One proof layer. Seven bank workflows.

Identity, consent, signatures, screening, KYC/AML, disputes and ISO 20022 evidence — connected by one verifiable chain.

The evidence gap

When trust breaks, the evidence is scattered across systems.

79% of corporate practitioners reported attempted or actual payments fraud in 2024 AFP 2025 survey

$3.5B reported lost to imposter scams in 2025 FTC, 2026

15+ min Every dispute = manual screenshot archaeology: find the transaction, find the login, find the consent, build the file — 15+ minutes per case, every case.

VeraBank does not need another decision engine. It needs a provable record of the identity, consent, decision and message.

The current platform

One proof layer across the bank's highest-friction trust moments.

Identity & sessions

Consent & leads

E-signatures

KYC / AML

Transactions & ISO 20022

↓

One append-only evidence chain public and offline verification

Use a widget, API, typed SDK, signed webhooks or MCP. VeraBank keeps every source system and every final decision; CapchaCloud stays outside the funds path.

CapchaID + consent

Prove who signed in and what they agreed to — in the same flow.

CapchaID: social OAuth, email/password, magic link, email OTP, TOTP 2FA, sessions and JWKS/JWT.
Consent evidence: exact disclosure, timestamp, origin and available IP/device and human-check context sealed into the same trail.
Honest boundary: passkeys are not represented as a live CapchaID method in the current public API.

Start on one public intake or employee flow in shadow mode. No core replacement, funds movement or bank-wide fraud promise.

CapchaSign

The document, signer, consent and audit trail seal together.

Document: templates, bulk sends, fields and the exact PDF version remain tied to the envelope.
Signer: identity assurance tiers L1–L4; higher tiers can use VeraBank's certified identity vendor.
Workflow: sequential routing, signer consent, optional pay-at-signing and video-consent evidence.
Proof: sealed PDF, certificate, append-only event log and public verification.

CapchaSign strengthens the evidence trail; VeraBank and counsel still determine enforceability and retention requirements.

Independent verification

The proof can be checked without trusting the dashboard.

Append-only chain: linked records make later alteration detectable.
Merkle proofs + time anchors: inclusion and claimed history are independently testable.
Public and offline verification: certificates, the chain explorer and offline tools do not require a tenant dashboard login.

Counterparty-independent verification is the product — not a screenshot from the vendor.

Integration model

One platform. Four integration paths.

Widgets: embed CapchaID and supported proof flows into an approved web experience.
API + typed SDK: integrate the public REST surface directly or through @capchacloud/sdk.
Signed webhooks: HMAC-SHA256 delivery, idempotency, logs and replay support downstream bank workflows.
Remote MCP: authorized operators can provision, configure, export and administer platform operations.

Chargeback Armor

Every covered transaction can generate its own defense package.

Record sealed→ dispute received→ evidence matched→ packet generated→ VeraBank / processor submits→ outcome recorded

VeraBank's own cardholders

Reg E debit disputes: an investigation-ready file is generated and routed. Adjudication stays 100% VeraBank's.

VeraBank's merchants

Chargebacks: a reason-code-ready evidence packet is generated; the merchant, VeraBank or its processor performs authorized submission.

Boundary: CapchaCloud assembles, verifies and routes evidence. It does not submit to Visa, Mastercard or Nacha, and it does not adjudicate.

ISO 20022 evidence

Seal the exact payment message — then corroborate what came back.

Seal the exact raw ISO 20022 bytes before or alongside the rail. Single records and batches of up to 50 are supported.
Bank-received pacs.002 or pacs.004 responses can be matched by UETR / OrgnlUETR and preserved with bank-submitted provenance.
10 credits, about $0.05 at published pricing. Proves message integrity and chain inclusion — not network signature or settlement validity.

CapchaVerify + CapchaShield

Screen first. Escalate with one sealed case file.

CapchaVerify: sanctions, device, transaction-monitoring and media checks create evidence; native checks are not certified KYC.
CapchaShield: VeraBank's contracted vendor remains the program of record; failed vendor calls do not silently downgrade.
Case export: checks, notes and status updates can export with actual media and a SHA-256 manifest.

Economic sensitivity

Use $2.16M as a testable gross-value hypothesis — not a forecast.

$656,250/yr dispute-handling labor, at a 75,000-dispute midpoint, saving 15 minutes per case at $35/hr loaded cost

+$1.5M/yr recovery lift at just $20 more recovered per dispute

≈ $2.16M/yr illustrative combined value — before platform, integration and vendor-management costs

Value not in that number: fewer fraud losses from bot-screened channels, merchant retention/attraction for the merchant-services book, examiner/audit time saved.

Branch count does not determine disputes. Every input is illustrative; discovery must replace it with VeraBank portfolio data before value is credited.

VeraBank value

The same proof layer compounds across the bank.

Operations: evidence matching and packet generation can reduce handling time per covered dispute.
Merchant services: offer merchants stronger checkout proof without replacing their processor or card-entry fields.
Risk + compliance: identity, screening, consent and transaction evidence can converge in one chronological case file.
Technology: one tenant with widgets, API, SDK, signed webhooks and MCP — additive to current systems.

Risk boundaries

What CapchaCloud is — and what it is not.

We are

A shipping platform with a public API
Additive and outside the funds path
Public and offline verification
Published DPA, BAA and trust materials

We are not

SOC 2 certified
A bank, processor, card network or adjudicator
Certified KYC without VeraBank's BYO vendor
A guarantee of fraud, legal or compliance outcomes

Pilot posture: non-sensitive, shadow-mode and due-diligence first. Public materials do not substitute for VeraBank security review.

The decision path

One architecture review. Then one measurable 60-day pilot.

1

Week 0 — architecture + diligence: compliance, infosec, operations and data mapping. No production banking data required.

2

60-day shadow-mode pilot: one low-risk flow, synthetic or non-sensitive data, and success metrics agreed before start.

3

Enterprise production: published tier starts at $999/month for 250,000+ credits, plus agreed integration scope — never an automatic commitment.

Adam Woodward, Founder · CapchaCloud (ServiceAutomations.ai)