Catalogue des messages et des règles
Généré à partir des registres pacs008, jeu de règles 2026.11.0 (hash sha256:a27fe2e7a04f36e9645310984e7142e58d2d5467490207479e689dd6fbbb668f). La couverture reflète les modèles livrés dans le paquet : elle ne peut donc pas prétendre à plus que ce que fait le logiciel.
Familles de messages
| Famille | Nom | Versions | Nombre | Règles applicables |
|---|---|---|---|---|
pacs.008 | FI to FI Customer Credit Transfer | pacs.008.001.01 - .13 | 13 | CBPR-ADDR-001, CBPR-ADDR-002, CBPR-ADDR-003, CBPR-ADDR-004, CBPR-ADDR-005, CHAPS-ADDR-001, CHAPS-PURP-001, CHAPS-RMT-001 |
pacs.002 | FI to FI Payment Status Report | pacs.002.001.12 | 1 | — |
pacs.003 | FI to FI Customer Direct Debit | pacs.003.001.09 | 1 | CBPR-ADDR-001, CBPR-ADDR-002, CBPR-ADDR-003, CBPR-ADDR-004 |
pacs.004 | Payment Return | pacs.004.001.11 | 1 | CBPR-ADDR-001, CBPR-ADDR-002, CBPR-ADDR-003, CBPR-ADDR-004 |
pacs.007 | FI to FI Payment Reversal | pacs.007.001.11 | 1 | — |
pacs.009 | Financial Institution Credit Transfer | pacs.009.001.10 | 1 | CBPR-ADDR-001, CBPR-ADDR-002, CBPR-ADDR-003, CBPR-ADDR-004, CBPR-ADDR-005, CHAPS-ADDR-001, CHAPS-PURP-001 |
pacs.010 | Financial Institution Direct Debit | pacs.010.001.05 | 1 | — |
pacs.028 | FI to FI Payment Status Request | pacs.028.001.05 | 1 | — |
Non implémenté
Nous les listons parce que leur absence est facile à supposer acquise.
| Famille | Statut | Remarque |
|---|---|---|
pain.* | Not implemented | The package cannot generate or parse pain messages. The browser workbench can now validate pain.001, pain.002, pain.007 and pain.008 against their XSDs. Structural validation only. Scoped in sebastienrousseau/pacs008#13. Tracked |
camt.* | Not implemented | The package cannot generate or parse camt messages. The browser workbench can now validate camt.110 and camt.111 against their XSDs, which covers the November 2026 receive-and-consume obligation for reading an incoming camt.110 — but structural validation is not the same as support. Scoped in sebastienrousseau/pacs008#12. Tracked |
head.001 | Not implemented | Business Application Header not shipped as a standalone template. |
Profils de schéma
| Profil | Nom | Statut | Entrée en vigueur |
|---|---|---|---|
cbpr-plus | SWIFT CBPR+ | stable | 2026-11-14 |
chaps-uk | Bank of England CHAPS | stable | 2026-11-14 |
t2-rtgs | Eurosystem T2 RTGS | stable | 2026-11-14 |
fedwire | US Federal Reserve Fedwire | stable | 2025-03-10 |
hvps-plus | HVPS+ High-Value Payments | stable | 2026-11-14 |
sct-inst | SEPA Instant Credit Transfer | stable | 2025-01-01 |
Règles
Chaque règle possède un identifiant stable qui ne change pas entre versions mineures. Toute modification du résultat (succès/échec) impose une nouvelle version du jeu de règles.
Les résumés de règles et les textes de correction sont en anglais : ils constituent le contenu normatif des règles, référencé par identifiant depuis chaque interface.
CBPR-ADDR-001 — Fully unstructured postal address is not accepted
| Profil | cbpr-plus |
| Couche | scheme |
| Gravité | error |
| En vigueur depuis | 2026-11-14 |
| Messages | pacs.008, pacs.009, pacs.004, pacs.003 |
| Chemin | {party}/PstlAdr |
| Source | SWIFT-ADDR-2026, vérifié 2026-07-28 |
| Jeux de test | structured-valid.csv (réussit) · hybrid-valid.csv (réussit) · unstructured-invalid.csv (échoue) |
From 14 November 2026 a fully unstructured postal address is rejected in CBPR+ payment messages.
Correction. Supply Town Name and Country in their structured elements. A compliant hybrid address is sufficient; a fully structured address is preferred.
CBPR-ADDR-002 — Town Name is mandatory in a structured element
| Profil | cbpr-plus |
| Couche | scheme |
| Gravité | error |
| En vigueur depuis | 2026-11-14 |
| Messages | pacs.008, pacs.009, pacs.004, pacs.003 |
| Chemin | {party}/PstlAdr/TwnNm |
| Source | SWIFT-ADDR-2026, vérifié 2026-07-28 |
| Jeux de test | hybrid-valid.csv (réussit) · missing-town-invalid.csv (échoue) |
Town Name must be carried in TwnNm, not in an address line.
Correction. Move the town into
CBPR-ADDR-003 — Country is mandatory as a two-letter ISO 3166 code
| Profil | cbpr-plus |
| Couche | scheme |
| Gravité | error |
| En vigueur depuis | 2026-11-14 |
| Messages | pacs.008, pacs.009, pacs.004, pacs.003 |
| Chemin | {party}/PstlAdr/Ctry |
| Source | SWIFT-ADDR-2026, vérifié 2026-07-28 |
| Jeux de test | hybrid-valid.csv (réussit) · missing-country-invalid.csv (échoue) |
Country must be carried in Ctry as a two-letter ISO 3166 alpha-2 code.
Correction. Use the alpha-2 code, for example GB rather than United Kingdom or GBR.
CBPR-ADDR-004 — Hybrid postal address is accepted
| Profil | cbpr-plus |
| Couche | scheme |
| Gravité | info |
| En vigueur depuis | 2025-11-22 |
| Messages | pacs.008, pacs.009, pacs.004, pacs.003 |
| Chemin | {party}/PstlAdr |
| Source | SWIFT-ADDR-2026, vérifié 2026-07-28 |
| Jeux de test | hybrid-valid.csv (réussit) |
A hybrid address — structured Town Name and Country alongside address lines — is accepted, both before and after the November 2026 change.
Correction. No action required. Note that a fully structured address remains preferable for downstream data quality.
CBPR-ADDR-005 — Agent identified by BIC only is exempt
| Profil | cbpr-plus |
| Couche | scheme |
| Gravité | info |
| En vigueur depuis | 2026-11-14 |
| Messages | pacs.008, pacs.009 |
| Chemin | {agent}/FinInstnId/BICFI |
| Source | SWIFT-ADDR-2026, vérifié 2026-07-28 |
| Jeux de test | agent-bic-only-valid.csv (réussit) |
For agent fields, BIC-only identification remains valid; no postal address is required.
Correction. No action required. Do not add a partial address purely to satisfy the address rule.
CBPR-ADDR-006 — Message types excepted from the address requirement
| Profil | cbpr-plus |
| Couche | scheme |
| Gravité | info |
| En vigueur depuis | 2026-11-14 |
| Messages | admi.024, camt.025, camt.052, camt.053, camt.054, camt.060 |
| Chemin | — |
| Source | SWIFT-ADDR-2026, vérifié 2026-07-28 |
| Jeux de test | — |
The structured address requirement does not apply to admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.
Correction. No action required for these message types.
CHAPS-ADDR-001 — CHAPS validation library rejects fully unstructured addresses
| Profil | chaps-uk |
| Couche | scheme |
| Gravité | error |
| En vigueur depuis | 2026-11-14 |
| Messages | pacs.008, pacs.009 |
| Chemin | {party}/PstlAdr |
| Source | BOE-CHAPS-2026, vérifié 2026-07-28 |
| Jeux de test | hybrid-valid.csv (réussit) · unstructured-invalid.csv (échoue) |
From November 2026 the CHAPS validation library rejects payments carrying a fully unstructured address. Hybrid is the minimum acceptable form.
Correction. Structure the address to at least hybrid form before submission to CHAPS.
CHAPS-PURP-001 — Purpose codes become mandatory on all CHAPS payments — annoncée, pas encore applicable
| Profil | chaps-uk |
| Couche | scheme |
| Gravité | error |
| En vigueur depuis | 2027-11-01 |
| Messages | pacs.008, pacs.009 |
| Chemin | CdtTrfTxInf/Purp/Cd |
| Source | BOE-CHAPS-2026, vérifié 2026-07-28 |
| Jeux de test | — |
From November 2027 the Bank of England requires a purpose code on all CHAPS payments, extending the earlier property and FI-to-FI requirement.
Correction. Populate
Effective date is the announced month; the exact day should be re-verified against the Bank of England policy statement before this rule is enforced.
CHAPS-RMT-001 — Structured remittance information becomes mandatory for CHAPS — annoncée, pas encore applicable
| Profil | chaps-uk |
| Couche | scheme |
| Gravité | error |
| En vigueur depuis | 2027-11-01 |
| Messages | pacs.008 |
| Chemin | CdtTrfTxInf/RmtInf/Strd |
| Source | BOE-CHAPS-2026, vérifié 2026-07-28 |
| Jeux de test | — |
From November 2027 remittance information carried in CHAPS payments must be structured.
Correction. Carry remittance data in
Announced in the Bank of England consultation; re-verify scope and exact date before enforcement.
Sources
| Source | Éditeur | Document | Entrée en vigueur | Vérifié |
|---|---|---|---|---|
SWIFT-ADDR-2026 | S.W.I.F.T. SC | SWIFT CBPR+ Removal of Unstructured Address Guidelines | 2026-11-14 | 2026-07-28 |
BOE-CHAPS-2026 | Bank of England | Policy Statement — Mandating ISO 20022 Enhanced Data in CHAPS | 2026-11-14 | 2026-07-28 |
ISO-20022-PACS008-13 | ISO 20022 Registration Authority | Financial Innovation & Transfer — pacs.008.001.13 Message Definition | 2025-01-01 | 2026-07-28 |
Attribution ISO 20022
pacs008.com is not the official ISO 20022 website. The sole source of up-to-date materials and information on ISO 20022 message standards and the Repository is https://www.iso20022.org/.
Les définitions et identifiants de messages de cette page proviennent de matériel ISO 20022, utilisé selon la ISO 20022 Intellectual Property Right Policy.