[Back to Evident](https://getevident.app/)

# A customer is more than a transaction.

A payment tells you that money moved. It rarely tells you enough about the person, the purchase, or what happened next.

We started Evident because SaaS teams often have to reconstruct a customer’s history from scratch. The payment is in one system, the account in another, and the conversation somewhere else. Each tool holds part of the answer. Someone still has to put it together.

A dispute turns that everyday friction into urgent work. A team has to explain a subscription charge, find the supporting records, and respond before a deadline. We’re building Evident to connect those scattered events into customer context that SaaS teams can use to fight fraud and prepare evidence.

## When a subscription is disputed

Consider a disputed subscription renewal. Billing shows a successful charge. The product shows recent use. Support holds a cancellation request. Read separately, these records suggest different answers. Read together, they help establish whether the renewal happened before or after the request, what the customer was told, and whether a refund was already issued.

Those distinctions matter. A stolen card, an unrecognized billing name, and a deliberate attempt to reverse a valid purchase can all lead to a dispute. “Friendly fraud” covers claims against legitimate transactions, including confusion and intentional misuse. Refund abuse raises similar questions: was access provided, was the account used, and has the charge already been refunded?

A business needs to distinguish these cases without treating every customer as a suspect. Sometimes the record supports defending a transaction. Sometimes it reveals a billing mistake that deserves a refund. The purpose of a complete history is to make either decision easier to support.

The cost extends beyond the payment itself. Finding records, investigating claims, and preparing responses consume time even when a business resolves a case correctly. For a small subscription payment, that work can cost more than the charge being disputed.

$69

Average disputed charge in subscription services.

[Mastercard / Datos Insights, 2025](https://www.mastercard.com/us/en/news-and-trends/Insights/2025/what-s-the-true-cost-of-a-chargeback-in-2025.html)

$128

Average handling cost, before the disputed payment.

[Mastercard / Javelin, 2026](https://www.mastercard.com/content/dam/mccom/shared/news-and-trends/insights/2026/2026-javelin-chargebacks-white/2026%20Chargebacks%20Javelin%20White%20Paper.pdf)

Separate studies, not a SaaS-specific benchmark. Handling costs cover large U.S. subscription and ecommerce merchants.

## One customer, several systems

The raw material already exists. Identity records describe the account and its sign-ins. Payments show charges, authentication, and refunds. Subscriptions add trials, plan changes, renewals, and cancellations. Product usage, devices, and sessions show activity around the purchase. Support records what the customer asked and what the business promised.

These systems were built for different jobs. A payment provider manages money; a support platform preserves conversations. Evident’s role is to bring their relevant records into a shared customer history, using the sources a business connects.

The value comes from the relationships between those records. A cancellation changes how a renewal should be understood. A refund changes the response to a dispute. A support conversation may explain activity that looks unusual in isolation. Collecting each event is useful only if the connection helps someone understand what happened.

## From events to a timeline

The workflow starts by gathering relevant events from the tools a business already uses. Those events are brought together around the customer and the subscription, then placed in sequence. The result should be a history a reviewer can follow, with the original records still available.

Timing can change the meaning of a case. An account is created, a subscription starts, the product is used, and a customer asks to cancel. A later charge is disputed. Looking at that sequence helps a reviewer ask the right questions: when did cancellation take effect, was the customer told, and was the disputed charge refunded?

Each question calls for different evidence. A claim about an unrecognized purchase needs different context from a complaint about an unfulfilled service. The customer history provides the starting point; the case determines which parts matter. A sign-in or a usage event alone should never be treated as a complete explanation.

## From context to evidence

A useful dispute response connects what is being claimed to records that support it. If a refund was issued, include its status. If support made a commitment, include the conversation and what followed. The aim is a concise account that someone else can inspect and assess.

Building Evident keeps bringing us back to the same lesson: more data does not necessarily mean more understanding. A larger inbox of events can leave the reviewer with just as much work. The product needs to make relevant information easy to find while keeping sources and uncertainties visible.

Completeness also includes the inconvenient details: lost access, billing errors, unresolved complaints, and promises the business did not keep. Evidence should support a fair decision. A clearer response cannot guarantee a particular outcome, and a convincing summary should never conceal a contradictory record.

That responsibility extends to the information itself. Customer knowledge should be complete enough to understand the relationship, accessible to the people who need it, and useful for the task at hand. It does not require collecting everything about a person.

## Beyond the dispute

Disputes are our starting point because the need is concrete. But the understanding built for one case should remain useful afterward. A support agent handling a refund and a payments reviewer investigating a charge are often asking different questions about the same relationship.

We want that history to help teams resolve support issues, investigate suspicious activity, and understand how payment problems relate to product experiences. Repeated cancellations after the same complaint, for example, may point to something the business needs to fix. Context can help explain patterns as well as individual cases.

AI makes this foundation more important. An assistant looking only at a charge can miss the cancellation conversation; one looking only at a support ticket can miss the refund. Automating a response does not remove the need to establish what happened. It increases the importance of giving software reliable context, clear sources, and limits on what it can conclude.

That is the direction of Evident: customer knowledge that lasts beyond a single dispute, helps businesses respond with evidence, and gives people and software a more complete view of the relationship.

Sources

1. [Mastercard — Chargeback amounts and costs](https://www.mastercard.com/us/en/news-and-trends/Insights/2025/what-s-the-true-cost-of-a-chargeback-in-2025.html)

   Updated June 2026. $69 is the subscription-services average in Datos Insights’ 2025 research; $128 combines $82 in internal costs and $46 in third-party fees from Javelin’s 2026 report.
2. [Javelin — Study methodology](https://www.mastercard.com/content/dam/mccom/shared/news-and-trends/insights/2026/2026-javelin-chargebacks-white/2026%20Chargebacks%20Javelin%20White%20Paper.pdf)

   September 2025 survey: 200 U.S. subscription and ecommerce merchants with $100m+ annual revenue; 100 issuer executives.

Canonical page: https://getevident.app/about