Access
Was the account authenticated and the entitlement active?
Villow · Revenue Protection · Private early access
Build the evidence before the dispute starts.
Villow is designed to record access, delivery, usage, and approved visual evidence while a digital product is being used. When a dispute arrives, the evidence is already connected to the transaction and ready to shape into a provider-specific case.
- Transaction-linked evidence
- Structured + approved visual evidence
- Source and trust preserved
Keep your existing payment provider. You remain responsible for the sale and chargeback liability; Villow does not process the payment or guarantee the outcome.
The missing record
A payment record does not prove digital fulfillment.
For SaaS, courses, downloads, memberships, and APIs, the useful facts live inside the product: entitlement, login, access, usage, and consumption. Weeks later, those facts are often scattered across systems.
Usage
Which purchased content, feature, download, or API entitlement was used?
Visual context
What did the approved product surface show when the event occurred?
Planned product flow
Capture once. Prepare the case when it matters.
The first product slice is being built with synthetic transactions and disputes. Production provider connections come after the evidence flow is proven.
- 01
Bind
A merchant backend will create a short-lived evidence session for one transaction and entitlement.
- 02
Capture
villow.js and approved server events will record the minimum fulfillment facts.
- 03
Connect
The Evidence Graph will link access, usage, visual keyframes, and provenance.
- 04
Detect
A connected provider is planned to open or update a dispute automatically.
- 05
Compile
A versioned provider profile will select the strongest relevant evidence.
- 06
Review
The merchant will review the prepared package and choose the permitted action.
The core product model
One transaction. One evidence record.
Each planned item is designed to keep its source, timestamp, trust level, policy version, and integrity history. A screenshot does not become stronger evidence just because it looks convincing.
The Evidence Graph is a domain model, not a surveillance feed. Continuous session replay and arbitrary event capture are outside the MVP.
EvidenceSourceState
Payment reference Provider verified linked
Entitlement granted Merchant server linked
Authenticated access Bound client linked
Lesson milestone Bound client linked
Visual keyframe Derived artifact linked
Dispute + outcome Provider verified planned
Value before a dispute
See which revenue has evidence and where the gaps are.
The planned dashboard uses transparent coverage checks. It shows what exists, what is missing, and which instrumentation would strengthen a transaction. There is no black-box win score.
Transaction VP-10428
Evidence coverage · Strong- Payment reference check_circle
- Entitlement granted check_circle
- Authenticated access check_circle
- Usage evidence check_circle
- Visual keyframe check_circle
- Offer / terms version error
Evidence gap
Store the offer and terms version that applied to this order.
Initial design partners
Built for fulfillment that cannot be put in a parcel.
Private early access is focused on DACH merchants with real dispute volume and an authenticated product or members area where evidence capture can be tested safely.
Strong early fit
- SaaS and API products
- Courses and memberships
- Downloads and licensed software
- High-value digital services
- Teams assembling dispute evidence by hand
What the pilot needs
- Meaningful payment-dispute exposure
- Access, entitlement, or usage events
- Ability to integrate villow.js or a server API
- Willingness to test with synthetic data first
- A Legal/DPO review path before live capture
Frequently asked
Does Villow process payments?
No. You keep your existing payment provider and remain responsible for the underlying transaction.
Does Villow take chargeback liability?
No. Villow prepares evidence and workflow support. It does not insure revenue, absorb losses, or guarantee a result.
Is the product live?
No. Villow is in validation and early product development. The first end-to-end slice uses synthetic transactions and disputes.
Will it record complete user sessions?
No. The MVP uses allowlisted events and event-triggered visual keyframes on approved surfaces. Continuous replay and arbitrary DOM capture are excluded.
How will disputes enter Villow?
Production integrations are planned to receive provider dispute events automatically. Manual import is intended only as a fallback for delivery, mapping, or permission failures.
Will Villow submit cases automatically?
The first model is merchant-guided review and submission. Policy-driven automatic submission may come later only when authority, provider, evidence, privacy, deadline, and retry gates all pass.
Which providers are supported?
No production provider integration is claimed yet. The first vertical slice uses one simulated provider profile before a real adapter is selected and approved.
Private early access
Help shape Villow with real digital-fulfillment cases.
Tell us where to reach you. We will follow up about design-partner fit.