Pain001 Pain001
Try the demo ›

Enterprise

Pain001 for regulated teams: supported channel, private profiles, integration help

The software is free at any scale. What is offered around it, for teams that must show a procurement reviewer a supported path.

2 min read Last reviewed

The pain001 suite is free, dual-licensed Apache-2.0 or MIT, and will stay so at any scale. That is the trust the whole project rests on, and nothing on this page changes it. What a regulated team often needs in addition is a named party with obligations: someone who answers within a window, keeps a release line stable while you are mid-migration, and can turn your bank's usage guideline into a validated profile without that guideline ever leaving your control. Those three things are offered here.

01. Supported release channel#

  • A designated long-term-support line of the core and its companions, with security fixes backported for its lifetime rather than "the latest release is the supported release".
  • Response targets for reproducible defects and security reports, in writing.
  • Release notes annotated for your context: which changes touch your rails, which are silent.

02. Private profile derivation#

  • You hold your bank's usage guideline under its licence; it never enters a public repository and never reaches this site. The library's overlay tooling inventories the guideline, diffs it against the ISO edition, and produces a profile the library enforces beside the public rail rules.
  • Delivered under NDA as a validated profile, with the derivation evidence, so your validation runs the bank's rules before the bank does.
  • Refreshed when the bank publishes a new guideline version.

03. Integration recipes#

  • End-to-end mappings from your ERP or TMS export to pain.001, with the CSV pipeline's column vocabulary, run against the example corpus for your rails until every file is clean.
  • Pipeline design for batch, streaming or API submission, with pain.002 acknowledgement handling and camt.053 reconciliation.

What this is not#

No hosted service, no telemetry, no licence change, no feature held back from the open packages. Everything a paid engagement produces that is not your bank's material flows back into the public project.

Ask#

Say which rail and country, the volume you expect, and the date you are working to. Nothing is stored beyond the message itself.







Prefer email? contact@pain001.com with "enterprise" in the subject reaches the same place.