Validation build: the evidence log is live; the pricing example is simulated and places no cover. What that means

For banks, consumer and mortgage lenders, and credit platforms

When a borrower contests a credit decision, show the assessment exactly as it was made.

A borrower in arrears says the loan should never have been granted. An applicant refused by a scoring model wants to know why. Either way the answer is the creditworthiness assessment on the day, and the doubt is whether it still reads as it did.

Try it in two minutes Talk about a pilot
When it is tested
A complaint or court case about irresponsible lending; an applicant contesting an automated refusal; a supervisor reviewing your credit files.
What you will be asked for
The creditworthiness assessment and the information it rested on (Consumer Credit Directive (EU) 2023/2225, Article 18(1); for mortgages, Directive 2014/17/EU, Article 18); where the assessment involves automated processing, the consumer’s right to human intervention, an explanation and a review of the decision (Article 18(8)); for a decision based solely on automated processing, what was decided and the human review the person may ask for (GDPR, Article 22).
What goes wrong today
Scores are recomputed when models change, inputs are refreshed, and the file shows today’s data rather than what the decision saw. An assessment rebuilt after the fact proves nothing.
What changes
Each assessment is sealed when the decision is made: a fingerprint of the inputs, the model or policy version, the outcome and any human review. The file stays in your systems; only a salted fingerprint reaches us. Asked about one decision, you can disclose the score it used and keep the rest of the file sealed.

Sealing shows that a record existed unchanged from a given moment; whether your records are enough is yours to judge. What the Consumer Credit Directive asks · GDPR Article 22 · One field, not the whole file

Try it in two minutes

  1. Choose a real file of your own: a credit assessment export or a decision letter. It is read in your browser and never uploaded.
  2. Seal it on Seal a file. A free sandbox key is issued on the page; only a salted fingerprint reaches the log.
  3. Make a copy, change one character in it, and check both against the receipt at Check. The copy fails; the original passes.

From your own systems it is one API call per record. Integrate · Other industries