For banks and financial institutions

Web content disappears. The regulator still asks about it.

Four situations where a sealed capture is the difference between an assertion and evidence.

A capture takes minutes and then sits in the file, with a timestamp, a hash list and a report you can attach to a regulatory filing or an ombudsman response. The examples are invented, the workflows are the real ones.

Case 1, capture 5309, a rate sheet before it changed
URLhttps://www.nordwest-sparkasse.de/baufinanzierung
SEAL VALIDi
Captured (UTC)2026-01-09T08:17:51Z
SHA-256, first 165e1a8d34f7c209b6
TimestampA-Trust, RFC 3161
Scope1,284 pages, 412.7 MB
Nordwest SparkasseKontenBaufinanzierungBeratungFilialen
Aktion bis Monatsende
Baufinanzierung ab 3,20%, fest für 10 Jahre
Konditionen vorbehaltlich Bonitätsprüfung. Beratung in der Filiale oder online, ohne Wartezeit.
Beratung vereinbarenKonditionen ansehen
Konditionen
Baufinanzierung, Sollzins gebunden
3,20 %
Bearbeitungsgebühr
0,00 EUR
Sondertilgung pro Jahr
bis 5 %
Erstberatung
kostenlos
Angaben ohne Gewähr. Nordwest Sparkasse AöR, Beispielstrasse 8, 28195 Bremen. Diese Seite ist erfunden und dient nur der Veranschaulichung.
Full page screenshot of the captured page, invented examplenordwest-sparkasse-20260109.wacz
9 minper capture312 pages, rate sheet and fee schedule
3widths per page1440, 768 and 390 pixels
11 p.evidence reportPDF/A-3, attachable to a filing as it is
365captures a yearDaily at 05:00Z, an unbroken chain
FILE STATEa3f9c1d2 e4b70855 c61f0da9 773be248 1c0596e7 f0a4bb2d 3e8c9517 0fbe4a622026-03-11T09:41:07Z

Four use cases

Ordered by how often they come up in our conversations with banks, payment institutions and insurers in Germany and Austria.

365 captures, one report per reference date

Proving publication duties to the FMA or BaFin were met

01 · Regulatory
Situation

Your institution has to show that a mandatory disclosure, a withdrawal notice or a PRIIP key information document for instance, was publicly available throughout the required period.

What you do

You set up a recurring order that captures the page concerned at fixed times and seals each capture on its own, with nobody needing to remember to run it.

What ends up in the file

A chain of proof across the whole reporting period, exportable as one report per reference date, with a verification log for the regulator.

order daily 05:00Z365 capturesdiscrepancies 0
A competitor's rates, secured before they changed

Preserving a competitor's advertised rate

02 · Advertised rates
Situation

A competitor advertises an interest rate or a fee waiver without naming the exclusions. In practice the page changes within hours of a regulator's enquiry.

What you do

You capture the offer page with its rate sheet, footnotes and linked fee schedule in three widths, before the first enquiry goes out. The capture is sealed immediately.

What ends up in the file

An evidence report with a timestamp, full page screenshots at desktop, tablet and mobile width, the hash list and the WARC archive for independent checking.

capture 5309312 pages 94.2 MBsealed 2026-04-02T06:00:07Z
Your own site, sealed every day

Proving the terms in effect when a contract was signed

03 · Contract disputes
Situation

A customer disputes, in a complaint proceeding, which fees, rates or terms stood on the website at the moment their contract was signed.

What you do

You capture your own website on a recurring schedule, daily for instance, and store the captures unchanged in WORM storage, referenced by contract number.

What ends up in the file

A series of sealed states on an unbroken timeline. The terms in effect on the contract date can be shown file by file.

series contract 2026-30471365 captures a yeardifferences 6 files
The state of the page on the day of the complaint

Answering a customer complaint to the ombudsman

04 · Ombudsman proceedings
Situation

A customer tells the dispute resolution body they were misled by an advertising claim or a product page. The page has since been revised more than once.

What you do

You pull the sealed capture from the day of the alleged claim and generate an evidence report from it for the institution's response.

What ends up in the file

A report showing the page's actual content on that day, with a timestamp and hash value, independent of any later revision.

capture 51881 page product detailretention 10 years

From order to case file, in six steps

This is the workflow for compliance setting up the capture itself. No IT knowledge needed, no command line.

a3f9c1d2 e4b70855
2026-03-11T09:41:07Z
01
Enter the address and crawl depth, pick the contract or filing number2 fields 30 seconds
02
The capture runs, progress visible per page312 pages runtime 9 min 10 s
03
The seal is applied, the timestamp is fetchedroot b7e2a4f1 tsa D-Trust
04
Generate the report, choose scope and extractspdf/a-3 11 pages exhibits 3
05
File it, through the DMS connector or as an exportwebdav s3 folder drop
06
Verify later, in one click or without Webichiveverification log sha256sum -c

What we do not promise

So that nothing comes as a surprise in front of a regulator or an ombudsman.

01

No judgement on evidentiary weight

The software produces a technically verified document. How a regulator or a court weighs it is for that body to decide. We claim nothing about outcomes.

02

No capture behind logins without your instruction

Areas behind a login, online banking itself for instance, are captured only if you supply credentials and assess admissibility yourself. The software asks explicitly.

03

No reconstruction of the past

What is captured is the state at the time of capture. Webichive cannot secure what stood on the page before that.

For banks and financial institutions | Webichive