Protect revenue
Transaction evidence: what was sold, shown, accepted and delivered
When a payment is questioned months later, the argument is rarely about the money. It is about what the customer was told and what they received. EPG records that at the moment of sale: your published policy wording, whether the customer read a version or explicitly agreed to it, what was bought, and what the business recorded as delivered or completed.
What is EPG transaction evidence?
EPG transaction evidence is an append-only, tenant-isolated record attached to a payment. It stores an immutable snapshot of the merchant's published policy versions with a SHA-256 content hash, whether each applicable policy was presented or explicitly accepted, the purchase details, and any delivery or service-completion record the merchant entered. Records are never edited: a correction is added and supersedes the earlier entry.
Presented is not accepted
EPG distinguishes two very different facts. PRESENTED means the exact policy version was displayed at checkout. EXPLICITLY_ACCEPTED means the customer ticked a box agreeing to that exact version. Acceptance is never inferred from a page view, a scroll or the payment itself, because a claim like that would not survive scrutiny — and should not.
Policies with versions, not a document that quietly changes
- Publish terms of sale, a refund policy and a cancellation policy from your settings.
- Publishing a change creates a new version; older versions stay exactly as the customers who read them saw them.
- Each version carries a content hash, so a stored snapshot can be checked against the published text.
- Templates are starting points to review and edit — they are not legal advice.
Evidence for services, not just parcels
Most businesses on EPG do not ship anything. A completed appointment, a session drawn from a package or a job signed off is the delivery. The business records it, EPG timestamps it and labels it as the merchant's own record — never as something EPG independently verified.
Where it surfaces
The record appears next to the payment and inside a dispute, with a timeline separating what happened before the dispute from what came after.
What is available today
| Capability | Where it stands |
|---|---|
Transaction evidence records An append-only record per payment: what was sold, which policy versions were shown, whether the customer explicitly accepted them, and what the business recorded as delivered. | Available now |
Published policies with versions Publish terms of sale, refund and cancellation policies. Publishing a change creates a new version; earlier versions stay exactly as customers read them. | Available now Templates are starting points you review and publish yourself. EPG does not provide legal advice. |
Dispute tracking See open chargebacks, their deadlines and what evidence is needed. | Available now |
The full list is on the features page.
The facts
- Evidence records are append-only; corrections supersede rather than overwrite.
- Policy versions are immutable once published and carry a SHA-256 content hash.
- EPG distinguishes PRESENTED from EXPLICITLY_ACCEPTED and never infers acceptance.
- Records are scoped to the merchant that took the payment and tagged with the environment they came from.
- Fulfilment records are labelled as merchant-recorded and not independently verified by EPG.
What this does not do
- EPG does not provide legal advice, and published templates are not a legal review of your business.
- EPG makes no claim that stored evidence will change a dispute outcome.
- Evidence exists only from the point it was captured; EPG cannot reconstruct records for past payments.
- Acceptance can only be recorded on checkout surfaces EPG controls.
Common questions
- What is the difference between a policy being presented and being accepted?
- Presented means the exact policy version was shown at checkout. Explicitly accepted means the customer ticked a box agreeing to that exact version. EPG records which of the two happened and never treats a view, a scroll or a completed payment as agreement.
- What happens when I update a policy?
- A new version is published. Earlier versions are kept unchanged, because a customer who bought last month agreed to what they read last month, not to your current wording.
- Does EPG verify that I delivered the goods or service?
- No. The business records delivery or service completion, and EPG timestamps and stores it, clearly labelled as the merchant's own record.
- Will this win a chargeback?
- No software can promise that. Evidence makes it possible to answer a dispute with facts and dates instead of recollection. The issuer and network decide the outcome.
- Can a stored record be edited?
- No. Records are append-only. A correction is added as a new entry that supersedes the earlier one, and both remain visible.
Keep reading
Keep Stripe. Add EPG.
Stripe processes your payments. Enterprise Pay Gateway helps you run, understand and protect the business behind them. Connect your account and see your own numbers.