SEPA credit transfer with a Belgian structured communication (BBA).
A payment initiation file for Belgium on the sepa-credit-transfer 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 |
be.sepa.sct-supplier.pain.001.001.03.xml | be.sepa.sct-supplier.pain.001.001.03.iso.json | be.sepa.sct-supplier.pain.001.001.03.provenance.yaml |
pain.001.001.09 |
be.sepa.sct-supplier.pain.001.001.09.xml | be.sepa.sct-supplier.pain.001.001.09.iso.json | be.sepa.sct-supplier.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 sepa-sct 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,initiator_postal_code,initiator_town_name,initiator_country_code,initiator_address_line,initiator_id,debtor_postal_code,debtor_town_name,debtor_country_code,debtor_address_line,debtor_id,creditor_postal_code,creditor_town_name,creditor_country_code,creditor_reference,creditor_reference_type,creditor_reference_issuer,initiator_id_scheme_proprietary,debtor_id_scheme_proprietary,payment_currency
BDS-SCT-20260921,2026-09-21T09:00:00,1,1180.00,Brasserie de la Senne NV,SCT-20260921-BE-01,TRF,true,SEPA,2026-09-22,Brasserie de la Senne NV,BE72536889307716,BWBGBE80,SLEV,BDS-2026-0921-001,1180.00,EUR,KWBZBE60,Mouterij Dingemans,BE22575526903747,1000,Brussels,BE,Rue Picard 3,0123456789,1000,Brussels,BE,Rue Picard 3,0123456789,2860,Sint-Katelijne-Waver,BE,090123456744,SCOR,BBA,KBO-BCE,KBO-BCE,EURHow the library checked it#
- Official XSD: passed.
- ISO message definition rules: passed.
- Rail profile
sepa-sct: 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#
- Febelfin, XML message for SEPA Credit Transfer initiation, implementation guidelines (pain.001) (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.