Dispute Defense · Identity Scoring in Milliseconds
Stop refunding money you don't owe.
Kombatix Defense scores the identity of anyone disputing a charge — against the original transaction and a verified identity network — in under a second. Three engines, one composite score, one clear answer. Use it at first contact to deflect refund abuse, or at chargeback time to strengthen your representment package.
Defense Report
Request ID fd8c7a53 · 2026-04-22
When You Use It
Defense fits into two points in the merchant dispute workflow.
Most customers use both.
Use Case 1
At First Contact
When a customer calls, emails, or submits a ticket claiming fraud, your support agent runs them through Defense. If the score shows friendly fraud, the agent follows a pre-written script: the identity was verified against the original purchase, the account will be closed, no refund will be issued, and the report will accompany any bank dispute.
Outcome: Most friendly fraudsters back down once they know they've been caught.
Use Case 2
At Chargeback Representment
When a fraud-coded chargeback lands, you attach the Kombatix Defense Report to your representment package. The bank sees timestamped identity evidence — disputing party's name, email, phone, and address all matching the original transaction — and a clear defense narrative they can act on.
Outcome: Fraud-coded chargebacks that used to be write-offs become winnable cases.
The Three Scoring Engines
One composite score from three independent engines.
Defense runs three independent scoring engines in parallel and combines them into a single composite score. Each engine tells you something different; the composite tells you what to do.
Engine 01 — Identity Match
Did the same person who bought it just claim they didn't?
Cross-references the disputing party's name, email, phone, and address against the data submitted at the time of the original transaction, and against a verified identity network.
Engine 02 — Identity Risk
Is this a trustworthy identity or one with a history?
Evaluates the identity itself — separate from whether it matches the transaction. Looks at identity age, fraud history connections, verified data point volume, and consistency across data streams. An identity can match the transaction perfectly and still carry fraud history; this engine surfaces that.
Engine 03 — Behavioral Risk
Does this person behave like a legitimate customer?
Analyzes activity patterns — transaction velocity, payment method stability, IP and location changes, identity element modifications, and chargeback history. A legitimate customer looks stable. A fraud actor shows sudden changes around the disputed transaction.
What You Get
Every Defense search returns a structured report your agents can act on immediately.
| Component | What It's For |
|---|---|
| Composite Score (0–100) | One number your team can route on. Above 80 = confident friendly fraud. Below 50 = possible true fraud. In between = review warranted. |
| Sub-scores | Identity Match, Identity Risk, Behavioral Risk — individually scored. Shows why the composite landed where it did. |
| Reason Codes | Specific flags — "Multiple payment methods (8)", "Transactions from different locations (5)", etc. Explainability for agents and for bank evidence. |
| Identity Match Breakdown | Field-level match view — name, email, phone, billing, shipping — green check or red X per field. Instantly readable. |
| AI Defense Narrative | Plain-English summary of the result, template-generated from the data. Agents copy-paste into support tickets or bank evidence packages. No writing required. |
| Transaction Metadata | Payment card type, transaction date, transaction amount, first-seen / last-seen dates for the identity. Context for the score. |
| Request ID + Timestamp | Every report timestamped and uniquely identified — admissible as structured evidence in bank dispute workflows. |
How You Access It
Defense API or Web Portal Access — independent subscriptions.
Defense scoring is available two ways, sold separately. Pick one or run both side-by-side — most teams start with one and add the other later.
Defense API
From $75/month · for engineering integrations
Full Defense scoring via a single POST endpoint. Integrate into your helpdesk (Zendesk, Intercom, Gorgias), CRM, or chargeback workflow. API access is granted as soon as you subscribe and your first month is paid — keys can be generated in the developer portal in minutes.
Web Portal Access
From $35/month · for support & CX teams (no-code)
No-code access via browser. Your team logs into the Kombatix Web Portal, pastes dispute details, runs a Defense Search, and gets a full report — composite score, AI Defense Narrative, identity match breakdown, exportable PDF, and searchable history. Separate subscription from the Defense API.
Defense Pricing
One score. Two channels. Pick how you access it.
Defense Score is sold through two independent channels — a REST API for engineering integrations and a Web Portal for support teams without developer capacity. Subscribe to one, the other, or both. Both bill for actionable results — scores in the friendly-fraud band (60+) — not for low-confidence noise.
Channel · API
Defense API
$75/month
Standard 75 hits · Advanced 1,000 hits · Enterprise custom
- • Embed in CRM, helpdesk, or chargeback workflow
- • REST + JSON, sub-second response
- • Sandbox environment included
Channel · Web Portal
Web Portal Access
$35/month
Standard 10 reports · Pro 100 reports · Enterprise custom
- • No-code, browser-based, no integration required
- • PDF export with AI Defense Narrative
- • Searchable history of every search