Mandate Labs
use case fraud

Stop the fraud. Keep the customer.

Ward scores a payment in the authorization path, reviews an account's history when a transaction is disputed, and tells you which merchants to stay away from. It approves the genuine first purchase.

[02] Evidence

The cost of a false decline is a customer.

New customers have no history, which is where false declines pile up. On our cold-start card benchmark Ward approved all but one genuine customer.

228 / 229genuine new customers approved
51 / 65frauds stopped on the same cases
40 msp50 server time

Cold-start card benchmark, October 2026: 229 genuine customers, 65 frauds. Full results →

[03] In your stack

Fits where your decision is made.

  • In the authorization path. 40 ms p50 server time on card decisions. A component that cannot run returns a review, never a pass.
  • Your thresholds. Set the step-up and decline cuts and your base rate per client. Each decision records what it ran with.
  • Your outcomes. Send chargebacks and confirmed fraud back. A per-client model trains in shadow and decides only when you approve it.
  • Explanations on demand. GET /decide/{id}/explain shows which signals moved the answer and by how much.

See Ward on your own cases.

Bring a statement, a declines export or the case your team is stuck on.