pain.001.001.08 closes the first generation of the message. Its structures sit closest to version 9 while retaining the older element names, which occasionally makes it a low-friction stop in staged migrations.
What to know about this version#
- A pragmatic halfway house when moving a v03-era integration towards CBPR+ alignment in two steps.
- Pain001 validates it against the official XSD like every other version.
Element structure (all versions share this skeleton)#
<GrpHdr>Group Header — message id, creation timestamp,NbOfTxs,CtrlSum, initiating party. Pain001 recomputes the control totals from validated records.<PmtInf>Payment Information — debtor, debtor account and agent, requested execution date, payment method, charge bearer; one block can carry many transactions.<CdtTrfTxInf>Credit Transfer Transaction — amount and currency, creditor, creditor account and agent, remittance information, end-to-end reference.
Generate and inspect#
pain001 init pain.001.001.08 -o work/ # scaffold a starter CSV
pain001 inspect pain.001.001.08 # list required + optional fields
pain001 -t pain.001.001.08 -d payments.csv -o out/ --dry-run
Records can be reshaped between supported versions. The mapper renames and defaults fields to match the target version; elements the target does not model are not carried over, so re-validate after migrating:
from pain001.migration import VersionMapper
rows = VersionMapper().migrate_rows(
rows, "pain.001.001.08", "pain.001.001.09"
)
See the full version catalogue, or the glossary for the vocabulary used here.