ExampleEditorialv1.0.0

Webshop builds its own consumer credit check: what belongs in the file

A non-food retail chain lets customers pay later in its webshop and decides at checkout whether a consumer qualifies. The team builds that assessment system in house, on top of a pre-trained model supplied by a vendor. The question is what has to be on record before the feature goes live, and who has to put it there.

The official source remains authoritative. This is general information about obligations and not legal advice. See this object on the map

Address and citation

This object has an address of its own that is never renamed or reused. Store the identifier in your own file, not the title or the link.

Identifier: praxikon:eu:ai-act:example:example-webshop-kredietcheck-technisch-dossier
Payload hash (sha256): d78a5fb746a80b877e3392af6e2f5baa03e844e1777db2c3b305ccb327eb0704

Citation line

Praxikon, "Webshop builds its own consumer credit check: what belongs in the file", praxikon:eu:ai-act:example:example-webshop-kredietcheck-technisch-dossier@1.0.0, dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0 (schema 1.4.0), effective_at 2026-08-08T00:00:00.000Z, known_at 2026-08-14T00:00:00.000Z, sha256 d78a5fb746a80b877e3392af6e2f5baa03e844e1777db2c3b305ccb327eb0704

Version: 1.0.0
Legal time (effective_at): 1 August 2024
Knowledge time (known_at): 8 August 2026
Closed on: Not closed
Topics: examples

Review status: Placed against the official source (8 August 2026). Next check due by 4 February 2027. The check date is the knowledge date of this version; no later recheck has been recorded.

What this object links to

Every relation appears below as a path: from the source with its locator, through the conditions and exceptions of the object carrying the relation, to the consequence. A locator belongs to a statement in the data and not to a relation, so the source is the source anchor of the carrying object.

The obligation this hangs off

1 of 1 shown

The object belongs to this obligation. The source line it hangs off sits there.

Source
Official fact on this object, with its locator.
- EU Artificial Intelligence Act 2024/1689
  Locator: Article 11(1) and Annex IV
  praxikon:eu:ai-act:source:reg-eu-2024-1689
  Open official source
Via
No condition or exception recorded on this object.
Consequence
- ObligationArticle 11: technical documentation
  praxikon:eu:ai-act:obligation:article-11-technical-documentation

What this object is about

2 of 2 shown

The object is about this role. Undifferentiated: it does not follow that the duty rests on this role.

Source
Official fact on this object, with its locator.
- EU Artificial Intelligence Act 2024/1689
  Locator: Article 11(1) and Annex IV
  praxikon:eu:ai-act:source:reg-eu-2024-1689
  Open official source
Via
No condition or exception recorded on this object.
Consequence
- ActorDeployer
  praxikon:eu:ai-act:actor:deployer
- ActorProvider of an AI system
  praxikon:eu:ai-act:actor:provider

What this object states

Official fact

Attributable to a named primary source, with a locator. Where they differ, the official source prevails.

Article 11(1) requires the technical documentation of a high-risk AI system to be drawn up before that system is placed on the market or put into service, and to be kept up to date. It must be drawn up so as to demonstrate compliance with the requirements of that Section and to give national competent authorities and notified bodies the necessary information, in a clear and comprehensive form, to assess that compliance; it contains at a minimum the elements set out in Annex IV. Annex IV lists those elements as applicable to the AI system concerned, and asks among other things for the methods and steps performed for development, including, where relevant, recourse to pre-trained systems or tools provided by third parties and how those were used, integrated or modified by the provider, for the validation and testing procedures used, and for a description of relevant changes made by the provider to the system through its lifecycle. SMEs, including start-ups, may supply those elements in a simplified manner; where they take that route, they must use the simplified form the Commission is to establish for that purpose.
- Locator: Article 11(1) and Annex IVpraxikon:eu:ai-act:source:reg-eu-2024-1689Open official source

Our interpretation

Our own reading. It can change without the law changing, and it is not the position of a supervisory authority.

Article 11 puts the documentation duty on the provider, so the first open question here is who that provider is. If the creditworthiness assessment of consumers counts as high-risk in your situation, then in our reading there is a strong case that a webshop assembling the system itself and putting it into service under its own name is no longer merely a deployer but ends up on the provider side, carrying the documentation duty that comes with it. Article 11 does not settle that allocation of roles, so test it against the definitions and against Article 25 before assuming the file is your vendor's problem. In our reading the hard part in retail is not the first version of the file but the pace afterwards, because a webshop often ships changes per release while the file stays frozen at the state it had when the feature went into service. So contract for the provenance, training and testing information that Annex IV expects from you when you buy the pre-trained model, and assign per release who updates the file.
- Locator: Article 11(1) and Annex IVpraxikon:eu:ai-act:source:reg-eu-2024-1689Open official source

When this applies

No condition recorded on this object.

When this does not apply

No exception recorded on this object.

Referring to this object

Citation block

Copy this reference into your advice, article or file. The identifier, the version and the hash keep the statement findable later, even once the dataset has moved on.

Reference

Praxikon, "Webshop builds its own consumer credit check: what belongs in the file",
praxikon:eu:ai-act:example:example-webshop-kredietcheck-technisch-dossier@1.0.0,
dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0 (schema 1.4.0),
effective_at 2024-08-01T00:00:00.000Z, known_at 2026-08-08T00:00:00.000Z,
sha256 d78a5fb746a80b877e3392af6e2f5baa03e844e1777db2c3b305ccb327eb0704,
https://www.praxikon.com/en/verkenner/example/example-webshop-kredietcheck-technisch-dossier
(https://www.praxikon.com/api/v1/entities?id=praxikon%3Aeu%3Aai-act%3Aexample%3Aexample-webshop-kredietcheck-technisch-dossier&effective_at=2024-08-01&known_at=2026-08-08&lang=en, accessed 2026-08-25)

Short form

praxikon:eu:ai-act:example:example-webshop-kredietcheck-technisch-dossier@1.0.0 (sha256 d78a5fb7)

BibTeX

@misc{praxikon-eu-ai-act-example-example-webshop-kredietcheck-technisch-dossier-1-0-0,
  author       = {{Praxikon}},
  title        = {Webshop builds its own consumer credit check: what belongs in the file},
  year         = {2026},
  version      = {1.0.0},
  number       = {praxikon:eu:ai-act:example:example-webshop-kredietcheck-technisch-dossier},
  howpublished = {AI Act Change \& Evidence Graph, dataset 2.1.0, schema 1.4.0},
  note         = {effective_at 2024-08-01T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 d78a5fb746a80b877e3392af6e2f5baa03e844e1777db2c3b305ccb327eb0704},
  url          = {https://www.praxikon.com/en/verkenner/example/example-webshop-kredietcheck-technisch-dossier},
  urldate      = {2026-08-25},
  language     = {en}
}

CSL JSON

[
  {
    "id": "praxikon:eu:ai-act:example:example-webshop-kredietcheck-technisch-dossier@1.0.0",
    "type": "dataset",
    "title": "Webshop builds its own consumer credit check: what belongs in the file",
    "container-title": "AI Act Change & Evidence Graph",
    "publisher": "Praxikon",
    "version": "1.0.0",
    "number": "praxikon:eu:ai-act:example:example-webshop-kredietcheck-technisch-dossier",
    "URL": "https://www.praxikon.com/en/verkenner/example/example-webshop-kredietcheck-technisch-dossier",
    "language": "en",
    "issued": {
      "date-parts": [
        [
          2026,
          8,
          8
        ]
      ]
    },
    "accessed": {
      "date-parts": [
        [
          2026,
          8,
          25
        ]
      ]
    },
    "note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.1.0; schema 1.4.0; effective_at 2024-08-01T00:00:00.000Z; known_at 2026-08-08T00:00:00.000Z; sha256 d78a5fb746a80b877e3392af6e2f5baa03e844e1777db2c3b305ccb327eb0704; retrieved_from https://www.praxikon.com/api/v1/entities?id=praxikon%3Aeu%3Aai-act%3Aexample%3Aexample-webshop-kredietcheck-technisch-dossier&effective_at=2024-08-01&known_at=2026-08-08&lang=en; licence https://www.praxikon.com/nl/legal/terms"
  }
]

How to verify a reference later is set out in the methodology. Terms

For agents and integrations

This page and the machine output come from the same object and the same two time axes.

Open as JSON Open as JSON-LD Read the methodology