BEAP v0.1 is in design-partner review
BEAP v0.1 ยท Draft / Design Partner ReviewDated 2026-09-11. A draft the banks reviewing it can still change. Not a finished standard, and it may change before v1.0.
The draft is not published on this site. It is being read by the banks it was written for, and it can still change in response to them.
If you are reviewing it, or would like to, write to beap@decionis.com and say which part of your bank you are mapping it onto. Discussion is the point of this stage, and a comment that changes a rule is worth more to us now than after it is fixed.
What is published
The machine-readable half of the same work, at /spec/v0.1/. Every JSON Schema identifies itself by a URL under that prefix, so they stay where they are: an identifier that stops resolving is worse than one nobody published.
- requirements.json, all 194 tagged requirements with their level and section, which is enough to see what each conformance level asks for
- the JSON Schemas, the shapes an implementation actually has to produce
- the registries, the fixed lists a second implementation has to agree with
Those are generated from the draft itself: 30 sections, source digest sha256:e7484b1ee1036d1d918de7336614b050b42cb61005629e3652adedfa5e0e52d1. Nothing on this site is derived from a different text.