> For the complete documentation index, see [llms.txt](https://koova.gitbook.io/koova-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://koova.gitbook.io/koova-whitepaper/introduction/problem.md).

# Problem

## Broken Trust Model

Commerce today operates on a simple but fragile premise: trust. When you buy something online, you trust the merchant to deliver what they promised. When an AI agent completes a transaction, you trust it actually happened. When a supply chain reports a shipment, you trust it’s real.

#### This trust model has three fundamental problems:

* **First, trust is expensive.** Merchants pay 1-3% in chargeback fees to cover the cost of disputes. Payment processors charge premium rates for high-risk categories. Insurance companies charge for fraud protection. All of this expense exists because trust is expensive to maintain and verify.
* **Second, trust is fragile.** When a dispute arises, there’s no objective way to determine what actually happened. The merchant says they delivered the product. The customer says they never received it. The platform has no way to prove either claim. The result: chargebacks, fraud losses, and broken commerce.
* **Third, trust doesn’t scale.** As commerce becomes more complex—with AI agents, cross-border transactions, and real-time settlement—the trust model breaks down. You can’t verify every transaction manually. You can’t trust every participant. You need a better way.

***

## Impact by Audience

#### **E-Commerce Merchants** 

Chargebacks cost the industry $117 billion annually. For an average online merchant, chargeback rates run 0.5-1% of transaction volume. This means a merchant processing $1 million in annual transactions loses $5,000-10,000 to chargebacks. When a customer disputes a transaction, the merchant has no way to prove what actually happened. The burden of proof falls on the merchant, and most merchants lose.

#### **AI Agents**

AI agents handle more commerce, they face a trust problem. When an agent completes a transaction on behalf of a user, how does the user know it actually happened? How does a smart contract verify the transaction was real? Today, agents have no way to prove their actions. This limits what they can do and who will trust them.

#### **Enterprise & Compliance** 

Supply chains, healthcare systems, and financial institutions all need auditable records. When something goes wrong, they need to prove what happened. Today, they rely on centralized databases that can be altered or disputed. They need immutable proof.

#### **DeFi & Smart Contracts** 

Smart contracts need to know what happened in the real world. Did that payment actually go through? Was that offer real? Today, they rely on centralized oracles that require trust. They need a better way.

***

### The Root Cause

{% hint style="danger" %}
**The root cause of all these problems is simple: commerce is unverifiable.**

There’s no way to prove that a transaction happened, exactly as described. There’s no objective record that can’t be disputed. There’s no mechanism to verify claims without trusting a central authority.
{% endhint %}

Traditional solutions fail because they all require trust in a middleman. Banks trust each other. Platforms trust their own servers. But what if you could verify transactions directly, without needing to trust anyone?


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://koova.gitbook.io/koova-whitepaper/introduction/problem.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.