Contact

Use the links below for source code, issue tracking, release notes, and package details.

Use the repository for bugs, feature requests, and source code. Use releases for version history. Use PyPI for install details.

For implementation work, start with the repository when you need examples, templates, or issue history. Check releases when you need a clear version record. Check PyPI when you need package metadata and install commands.

• Repository: https://github.com/sebastienrousseau/pacs008
• Releases: https://github.com/sebastienrousseau/pacs008/releases
• Package: https://pypi.org/project/pacs008/

Before reaching out

Many questions are already answered in existing project resources. The FAQ page covers common questions about ISO 20022 pacs messages, CBPR+ migration timelines, and toolkit usage. The API documentation explains installation, endpoints, CLI options, and Python library methods. The glossary defines over 60 ISO 20022 and payment messaging terms.

Bug reports benefit from including the message type, version, and a short example of the failing input. Attach the input file or a minimal reproduction case. Specify the Python version and operating system. The more context a report includes, the faster the resolution.

Before a rollout, review recent releases first to match implementation work to a known package version. If you need install or dependency details, PyPI is the fastest place to confirm the current package record.

Security issues

Report security vulnerabilities privately. Do not open a public GitHub issue for security concerns. Instead, use the GitHub security advisory form to submit a confidential report. Include a description of the vulnerability, steps to reproduce it, and the potential impact. Security reports receive priority handling.

Feature requests

Feature requests are welcome. Open a GitHub issue with the label enhancement. Describe the use case, the expected behaviour, and any relevant message types or versions. Requests that align with ISO 20022 standards adoption and payment operations workflows receive priority.

Response times

This is an open-source project maintained alongside other commitments. Most issues receive an initial response within a few business days. Bug reports with clear reproduction steps are prioritised. Feature requests are reviewed on a rolling basis and scheduled according to project roadmap alignment.

Community contributions

Contributions are encouraged. Fork the repository, create a feature branch, and open a pull request. All pull requests go through automated validation and a manual review. Contribution guidelines are available in the repository README. Accepted contributions follow the same editorial and coding standards as the rest of the project.