Representative examples, effective rates, offer dates and the statements a regulator wants word for word, often behind a hover or an info button. Vadilator reads all of it straight out of every banner, holds every number against the approved copy and against each other, and checks that the legal can actually be read. A validator signs the report.
A headline is written once. The representative example is copied into every size and every language by hand, and updated when the rate changes.
"Legal information" as a link. The text appears only with the mouse over it, so in review nobody sees it at all.
A layer that opens on a click. Same problem, one click further away.
The headline says 4,9 %, the representative example says 5,9 % because the template came from the last campaign.
Valid until the end of last year. The banner went live this year.
The sentence a regulator requires word for word, with one umlaut missing in one size.
All the legal fits, because it is too small to read.
For an HTML5 banner the text is in its code. We open every layer it has and read it letter for letter.
Per creative and language, plus an [All] block for what every file must carry: the lender's name and seat, the mandatory statement, the representative example.
The banner plays, the mouse goes over it, every link or button named like legal, info or terms is hovered and clicked. Whatever appears is read, letter for letter.
Rates, amounts, terms, total cost and dates are compared as numbers. 5,9 instead of 4,9 is a number finding, the most serious kind, with both values side by side.
An offer date, a "valid until" or a deadline already in the past is flagged on its own.
Smallest type in pixels, contrast against the background, legal that needs a mouse, legal that never shows, and every link opened once to see that it answers.
A person goes through every finding with its evidence. Version 2 of a banner is compared word by word with version 1, so a changed number shows up even when nobody mentions it.
Three HTML5 banners for Fennek Bank, a bank we made up, with faults planted on purpose, and the approved copy as a text file. This is what the automatic pass found, before any person looked.
Which statements a credit ad must carry, and where, is your compliance team's decision for each market. We check the files against the copy and the rules they give us.
A finding in a rate, a date or a mandatory statement is marked, never corrected by us. The fix goes back to whoever owns the approved copy.
Files are seen by the validator only, deleted after the retention period, never used as examples. NDA first, hosted in Switzerland.
One product, all its sizes and languages, and the approved copy. You get the signed report and decide from that.