comanage_nacha
A simple Wells Fargo flavor NACHA file builder, parser, and validation toolkit
pip install comanage_nacha
from comanage_nacha import NachaFile
with NachaFile(company_name='COMANAGE LLC',
file_id_modifier='A',
file_creation_date=datetime.date.today(),
file_creation_time=datetime.datetime.utcnow()) as nacha:
with nacha.add_batch(service_class_code=200,
company_name='COMANAGE LLC',
company_id='0123456789',
effective_entry_date=datetime.date.today()) as batch:
batch.add_entry(transaction_code=22,
receiving_dfi_routing_number='09100001',
routing_number_check_digit=0,
receiving_dfi_account_number='0123456789',
amount=10000,
individual_id='123',
individual_name='FRANK')
print(nacha.render_to_string())
nacha_string = nacha.render_to_string()
- Authors:
Franklyn Tackitt @kageurufu
Metadata
Release files for comanage_nacha 0.2.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| comanage_nacha-0.2.7.tar.gz | 18.6 kB | Without provenance | Details for comanage_nacha-0.2.7.tar.gz |
Release files / comanage_nacha-0.2.7.tar.gz
| Download URL | comanage_nacha-0.2.7.tar.gz |
|---|---|
| Size | 18.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d3336903fa4ee8ff8b515defb70fd1c11a22132f257dabe868784f130fab16a
|
|
BLAKE2b-256 checksum How to use checksums |
71277362834286b577aa102b6e1bf4b0e153092543071bb8243044d23c0749ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for comanage_nacha 0.2.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.