Buyer questions, answered plainly

The short answers are first. Deeper commercial and technical detail is still here — open the section you need. Where something is not done, not certified or not integrated, it says so.

What CheckGuard does today

Frequently asked

Does AI make the final fraud decision?

No. The risk score is produced by deterministic, weighted signals. The AI Investigator is read-only: it summarises and explains evidence already recorded and cannot change a score, create a signal, alter evidence, close a case or declare fraud. Every binding decision is recorded against a named human reviewer with rationale.

What data does CheckGuard store?

Case metadata (amount, date, check number, channel, payee and maker names as submitted), check captures in private storage, machine-generated signals and evidence, reviewer decisions and an immutable audit trail.

Does CheckGuard store full account or routing numbers?

No. Only the last four digits of routing and account numbers are persisted. Full values submitted for validation are used in-request and are not written to the database.

Can CheckGuard integrate by API?

Yes. There is a versioned REST API (v1) for case submission, capture upload, status, and explainable assessments, plus signed outbound webhooks. A machine-readable OpenAPI document is published by the platform.

Is there a sandbox?

Yes. Sandbox is a separate environment bound at the credential level; sandbox cases are flagged and never mix with production records. Production credentials are issued only after a staged activation.

How does tenant isolation work?

Every record carries its institution and every access policy is enforced in the database per record, not in the interface. Cross-institution reads return nothing, including for API credentials, which are bound to one institution and one environment.

Can CheckGuard support multiple reviewers?

Yes. Roles cover submitters, analysts, senior reviewers, institution administrators and platform administrators, with a review queue, senior review lane and escalation path.

What happens when OCR cannot read a check?

Unreadable or poor-quality captures are treated as an intake problem, not fraud evidence. The case is routed for additional information; image quality never raises the fraud score by itself.

Is CheckGuard SOC 2 certified?

No. CheckGuard is not SOC 2 certified and no audit has been performed. We maintain a documented SOC 2 readiness gap map and can share our control descriptions and evidence for diligence.

What core platforms are currently integrated?

None. There are no vendor partnerships or certified core integrations today. Integration is via the CheckGuard API, webhooks, or an adapter built to the institution's transport.

Security, penetration-test, business-continuity, access and tenant-security detail, and what still depends on external parties, all live on one page. View assurance status →

How a design partnership runs

Four phases, sandbox first. No pilot outcome automatically enables production.

1. Phase 1 — Discovery & acceptance

   Fit, use case and pilot appetite confirmed, tenant provisioned, a named institution admin identified and data handling acknowledged.

   Steps 1–4 of 14

2. Phase 2 — Sandbox setup

   Sandbox and pilot mode issued, optional least-privilege service account and webhook receiver configured, then a synthetic end-to-end test.

   Steps 5–8 of 14

3. Phase 3 — Pilot evaluation

   Reviewers trained, approved pilot items loaded with expected outcomes, and labels, reviewer agreement and signal feedback recorded in pilot mode.

   Steps 9–11 of 14

4. Phase 4 — Review & next-step decision

   Scorecard walked through against the agreed criteria, then a documented go / no-go / extend decision. Production activation is a separate staged, audited control.

   Steps 12–14 of 14

Pricing structure

This is the shape of commercial terms, not a quote. Final pricing depends on volume, institution size and scope.

Integration readiness

CheckGuard supports API, webhook, and adapter-based integration. No vendor-specific core integration is certified today, and there are no vendor partnerships. Integration requirements are evaluated with each institution during the sandbox / design-partner process.

Architecture and API readiness is not a certified partner integration.

Support model (draft)

These are discussion targets, not contractual service levels until written into an agreement.