CHAPS same-day property completion with the BoE HLST purpose code.
A payment initiation file for United Kingdom on the priority-payment rail, shipped in pain.001.001.03, pain.001.001.09, generated and checked by pain001 0.0.70. It is a synthetic example built from the public scheme rulebooks: no real party, account or bank guideline behind it.
Files#
| Edition | Payment file | ISO 20022 JSON twin | Provenance record |
|---|---|---|---|
pain.001.001.03 |
gb.chaps.property-purchase.pain.001.001.03.xml | gb.chaps.property-purchase.pain.001.001.03.iso.json | gb.chaps.property-purchase.pain.001.001.03.provenance.yaml |
pain.001.001.09 |
gb.chaps.property-purchase.pain.001.001.09.xml | gb.chaps.property-purchase.pain.001.001.09.iso.json | gb.chaps.property-purchase.pain.001.001.09.provenance.yaml |
The twin is the same payment in the ISO 20022 Registration Authority's JSON convention, lossless in both directions; its JSON Schema (2020-12) is published per edition: pain.001.001.03, pain.001.001.09. An agent can produce a twin that validates against the schema and hand it to the library to render the XML.
Run it in your browser#
Open this scenario in the demo: the pain001 library loads in a Python runtime in your browser, rebuilds the file from the 1 record(s) below, checks it against the uk-chaps rulebook and the official XSD, and shows the JSON twin. Nothing leaves your machine.
The flat records the library rebuilds it from (the CSV pipeline's own column names):
id,date,nb_of_txs,ctrl_sum,initiator_name,payment_information_id,payment_method,batch_booking,service_level_code,requested_execution_date,debtor_name,debtor_account_IBAN,debtor_agent_BIC,charge_bearer,payment_id,payment_amount,currency,creditor_agent_BIC,creditor_name,creditor_account_IBAN,remittance_information,instruction_priority,initiator_postal_code,initiator_town_name,initiator_country_code,initiator_address_line,initiator_lei,debtor_postal_code,debtor_town_name,debtor_country_code,debtor_address_line,debtor_lei,debtor_account_currency,debtor_agent_clearing_system,debtor_agent_member_id,uetr,creditor_postal_code,creditor_town_name,creditor_country_code,creditor_address_line,creditor_agent_clearing_system,creditor_agent_member_id,purpose_code,payment_currency
ELMRD-20260912-0001,2026-09-12T08:30:00,1,425000.00,Elm Road Developments Ltd,CHAPS-20260912-001,TRF,false,SDVA,2026-09-12,Elm Road Developments Ltd,GB07OUER60969382168086,OICSGB40,SHAR,COMPLETION-2026-0912,425000.00,GBP,NPHBGBS0,Bramley and Co Solicitors Client Account,GB20OYKL60284231569811,Completion 14 Elm Road,HIGH,SW1A 1AA,London,GB,14 Elm Road,000000NMWEL2E9U1VL21,SW1A 1AA,London,GB,14 Elm Road,000000NMWEL2E9U1VL21,GBP,GBDSC,040004,069356c8-b718-4363-b1bc-824f86f5108f,RG1 2AB,Reading,GB,2 High Street,GBDSC,309634,HLST,GBPHow the library checked it#
- Official XSD: passed.
- ISO message definition rules: passed.
- Rail profile
uk-chaps: passed. - Rail profile
purpose-mandate-gb: passed. - Rail profile
anti-duplicate: passed.
Confidence derived: built from the public rulebook or implementation guide; no published sample was available to compare.
Where the content comes from#
- Bank of England: ISO 20022 purpose codes for CHAPS property transactions (read 2026-09-10)
SHA-256 of each file is in its provenance record. Your bank's own usage guideline is not represented here: apply it privately with the library's overlay tooling.