RTP real-time payment, single.
A payment initiation file for United States on the instant-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 |
us.rtp.single.pain.001.001.03.xml | us.rtp.single.pain.001.001.03.iso.json | us.rtp.single.pain.001.001.03.provenance.yaml |
pain.001.001.09 |
us.rtp.single.pain.001.001.09.xml | us.rtp.single.pain.001.001.09.iso.json | us.rtp.single.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 us-rtp 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_agent_BIC,charge_bearer,payment_id,payment_amount,currency,creditor_agent_BIC,creditor_name,remittance_information,local_instrument_proprietary,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,debtor_account_number,debtor_account_scheme,debtor_agent_clearing_system,debtor_agent_member_id,uetr,creditor_street_name,creditor_building_number,creditor_postal_code,creditor_town_name,creditor_country_subdivision,creditor_country_code,creditor_account_number,creditor_account_scheme,creditor_agent_clearing_system,creditor_agent_member_id,debtor_agent_town_name,debtor_agent_country_subdivision,debtor_agent_country_code,creditor_agent_town_name,creditor_agent_country_subdivision,creditor_agent_country_code,payment_currency
CMI-RTP-20260922-01,2026-09-22T12:00:00,1,8600.00,Cascade Millwork Inc,RTP-20260922-01,TRF,URNS,2026-09-22,Cascade Millwork Inc,GDNXUSX0,SLEV,CMI-RTP-2026-0922-01,8600.00,USD,TLSEUSI0,Redwood Hardware Supply LLC,INV 2026-0912,rtp,Pine Street,1200,97204,Portland,OR,US,Pine Street,1200,97204,Portland,OR,US,4412345678,BBAN,USABA,021000021,5105128c-2397-45c1-977e-7a3a69182632,Mission Street,800,94103,San Francisco,CA,US,5512345678,BBAN,USABA,121000248,New York,NY,US,San Francisco,CA,US,USDHow the library checked it#
- Official XSD: passed.
- ISO message definition rules: passed.
- Rail profile
us-rtp: 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#
- The Clearing House RTP network rules (per-item limit) (read 2026-09-10)
- Cross River RTP pain.001 input specification (local instrument rtp) (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.