Which version is recorded if I publish new terms while a customer is paying?

The one the customer saw. The module notes the version displayed above the payment methods and records it when the order is validated. If no display was traced, for example with a checkout that does not use the payment step hook, it records the version in force on the order date and says so.

Can I edit a version that is already published?

No, on purpose: an editable version would prove nothing. You create a new version from the previous one, edit the text, then publish it immediately or on a future date. The comparison screen shows what changes before you publish.

What about orders placed before I installed the module?

Add your previous terms as versions dated in the past, then start the linking from the register. Each order gets the version in force on its date and stays marked as linked afterwards, with no IP address or display trace, so the module never claims something it did not observe.

What is the RFC 3161 timestamp for?

An independent authority signs the fingerprint of your versions and of your register together with the date. This proves that the text and the records existed on that date and have not changed since. Anyone can check it with OpenSSL and the authority's public certificate. DigiCert is used by default, with no account or fee.

The module hooks into the official PrestaShop GDPR module: acceptances are included in the customer data export. For erasure requests you choose between keeping the evidence, which article 17.3.e allows for the defence of legal claims, and erasing the IP address and browser. An option also anonymises IP addresses as soon as they are recorded.

Is the module compatible with PrestaShop 9?

Yes, from PrestaShop 8.0 to 9.x with the same ZIP, multistore included. It uses ModuleAdminController, PrestaShop's built-in TCPDF for PDFs and no Composer dependency.

Terms and Conditions Versioning & Acceptance Proof PrestaShop

Terms and Conditions Versioning & Acceptance Proof for PrestaShop 8 & 9

Which version of your terms did this customer accept? The answer, with the proof.

When a customer disputes an order or files a chargeback, you are asked for the terms they accepted on that day. PrestaShop only keeps the current version of your terms page. This module archives every version with its date, records on each order the version shown at payment, with the IP address, the browser and the SHA-256 fingerprint of the text, and attaches the PDF of that version to the confirmation email. When a dispute comes, one click on the order gives you an evidence pack ready to send.

At a glance

Every version of your terms archived with its effective date, locked once published
Version actually shown at payment recorded on each order (IP, browser, SHA-256)
PDF of the accepted version attached to the order confirmation email
Third party timestamps (RFC 3161) and a sealed acceptance register
One-click evidence pack ZIP from the order page

PrestaShop 8 & 9 RFC 3161 timestamps Sealed register psgdpr compatible

30-day refund

12 months updates

24h support

The long version

Everything you'd want to know before you install.

A detailed look at how Terms and Conditions Versioning & Acceptance Proof for PrestaShop 8 & 9 works, why we built it the way we did, and the thinking behind the features above.

§ 01

What PrestaShop does not keep

PrestaShop shows an "I agree to the terms of service" checkbox that links to a CMS page. When you edit that page, the previous version is gone. Six months later, facing a customer who disputes return fees or a bank handling a chargeback, you cannot prove which text they accepted. That is exactly what this module records, order by order.

§ 02

A dated, locked history

Each version of your terms has a number, a text per language, an effective date and a change summary. On publication the version is locked, its SHA-256 fingerprint computed and its PDF generated in every language. You can schedule a future version, add your previous terms with their past date and compare two versions to see exactly what changed.

§ 03

The accepted version, order by order

At payment, the module shows the number of the version in force and a link to its PDF, and notes which version was shown to that customer. When the order is validated, it records this version with the fingerprint of the text in the customer's language, their IP address and browser. The PDF of that version is attached to the confirmation email, and the version appears in the customer account and, if you wish, on the invoice.

§ 04

Evidence a third party can verify

Records are chained: each acceptance includes the fingerprint of the previous one, so any later change, insertion or deletion becomes detectable. Published versions and the state of the register are timestamped by an independent authority under the RFC 3161 standard. An expert can check everything with OpenSSL, without having to trust you.

§ 05

For shops that are already trading

Add your previous terms with their effective date, then let the module link your past orders to the version that applied on their date. These orders are clearly marked as linked afterwards: the module does not claim a display it never saw.

Terms and Conditions Versioning & Acceptance Proof for PrestaShop 8 & 9

The short version.

The version the customer actually saw

Versions that cannot be touched afterwards

Evidence that holds up when challenged

The dispute file in one click