Urgent euro payment (TARGET) from a German account, DK order type CCU.
A payment initiation file for Germany on the urgent-euro 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 |
de.ccu.urgent.pain.001.001.03.xml | de.ccu.urgent.pain.001.001.03.iso.json | de.ccu.urgent.pain.001.001.03.provenance.yaml |
pain.001.001.09 |
de.ccu.urgent.pain.001.001.09.xml | de.ccu.urgent.pain.001.001.09.iso.json | de.ccu.urgent.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 de-ccu 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,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_street_name,initiator_building_number,initiator_postal_code,initiator_town_name,initiator_country_subdivision,initiator_country_code,debtor_street_name,debtor_building_number,debtor_postal_code,debtor_town_name,debtor_country_subdivision,debtor_country_code,uetr,creditor_street_name,creditor_building_number,creditor_postal_code,creditor_town_name,creditor_country_subdivision,creditor_country_code,purpose_code,debtor_agent_town_name,debtor_agent_country_code,creditor_agent_town_name,creditor_agent_country_code,payment_currency
MSTR-CCU-20260921-01,2026-09-21T09:30:00,1,250000.00,Musterfirma GmbH,CCU-20260921-01,TRF,URGP,2026-09-21,Musterfirma GmbH,DE89099991287457870052,HPXTDEW0,SHAR,MSTR-CCU-2026-0921-01,250000.00,EUR,FVEHFRT0,Compagnie Industrielle de Lorraine,FR2485465373980A5BUYVL3NS43,Anzahlung Auftrag 2026-4471,HIGH,Hauptstrasse,12,80331,Muenchen,BY,DE,Hauptstrasse,12,80331,Muenchen,BY,DE,12a4be1a-5290-4d64-97a5-6607b041914b,Rue de Metz,7,54000,Nancy,GES,FR,GDDS,Muenchen,DE,Paris,FR,EURHow the library checked it#
- Official XSD: passed.
- ISO message definition rules: passed.
- Rail profile
de-ccu: 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#
- DK DFUE-Abkommen Anlage 3 V26.11, order type CCU (read 2026-09-10)
- DZ BANK, CCU product description (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.