Skip to main content

Ctrl+K

Pain001 0.0.74 documentation

Installation
Using Pain001
Configuration
Plugin architecture
Request-local payment policies

GitHub
PyPI

Installation
Using Pain001
Configuration
Plugin architecture
Request-local payment policies
Explicit SFTP delivery
Template Registry
Version Migration
Security
Large-Batch Performance
Performance Playbook
Validate-Only And Streaming
Additional Message Types
Async Adapters
Troubleshooting
Testing Quality
Structured Logging
Examples
pain001
Frequently Asked Questions
Glossary
Pain001 Architecture
The example corpus
Twins: the same pain.001 message, losslessly, in JSON
Input columns: the flat vocabulary of the CSV pipeline
What each ISO 20022 edition changed
Development
Packaging notes for distribution maintainers
Architecture decision records
Toolchain and contribution policies
Scope comparison
Benchmark methodology
Verification coverage and limits
Open-issue audit for feat/v0.0.71
Code-scanning audit: feat/v0.0.71
Assurance case
Deployment cookbook: pain001 in production
Quickstart: from CSV to validated ISO 20022 in 10 minutes
Custom Validation with JSON Schemas
0001. Monotonic 0.0.x versioning and suite lockstep
0002. Dual licence, Apache-2.0 OR MIT, declared with PEP 639
0003. Example corpus: two corpora, one engine, twelve scoped decisions
0004. Python floor policy
0005. Twins preserve pain.001; faces express it for a compatible standard
0006. Local policies and review-only corrections
ADR-0007: Built-in rules do not depend on registry dispatch
0008. Preserve raw CSV values on ingress; formula neutralisation is opt-in
Lessons from shipping a 100%-coverage ISO 20022 payment library
Hacker News submission template
pain001.com

GitHub
PyPI

Indices

General Index
Python Module Index

Search

Ctrl+K

Created using Sphinx 8.1.3.