Official implementation-resource registry
Versioned XSD, rulebook, guideline, access, and ownership metadata beside the messages they govern.
What Payments Signal is building
The roadmap is ordered by learner and implementation value. Now, Next, and Later describe sequence—not promised delivery dates.
NOW
Now
Capabilities already delivered and verified in the current release line.
Downloadable teaching samples
Raw XML and FIN files generated from the canonical annotated examples, with honest validation labels.
Positive, exception, and MT lifecycle packs
Ordered ZIP packs with a manifest, exact namespaces, fictional-data notice, and implementation caveats.
Scheme and market-infrastructure expansion
CBPR+, SEPA SCT, SCT Inst, SDD, VoP, high-value, correspondent-banking, and reporting resources mapped to messages, flows, mappings, and topics.
Mappings, test packs, and BA checklists
Downloadable MT↔MX mapping tables, positive and negative tests, field matrices, acceptance criteria, migration notes, and profile ZIP packs.
Version and supersession tracking
Visible version history plus a Monday snapshot process that opens standards changes for human review and never auto-merges them.
Browser XSD feasibility prototype
A non-production Web Worker prototype with local-only files, pinned libxml2 WASM, package guards, separate validation stages, and a documented release gate.
Deeper domestic-profile implementation assets
Separate T2, TIPS, CHAPS, Fedwire, and CHIPS packs with verified rules, test cases, BA artefacts, checksums, and explicit restricted-source gaps.
NEXT
Next
The next useful implementation assets after the core lifecycle is complete.
Independent validator release review
A typed evidence matrix, production-host safeguard, synthetic fixtures, privacy-safe local review recorder, repeatable performance preflight, and fail-closed verifier are ready. Independent reviewers must still complete security, current-browser, accessibility, network-privacy, and browser-memory evidence before approval.
LATER
Later
Valuable work that must first clear security, rights, or technical feasibility gates.
Private browser-only XSD validation
Engineering is complete behind a 404-by-default runtime gate. Independent security review and the Safari, Chrome, Firefox, and Edge compatibility matrix must clear before release.
Profile-aware diagnostics
Engineering is complete: stage-separated results explain what supplied XSDs test and what remains outside XSD. It stays gated with the validator until independent review passes.