Skip to main content

EDI Configuration

Core

StateSet integration

Event delivery signing

Two signing schemes are in play, and they are not interchangeable. Both produce sha256=<hex> HMAC-SHA256 values.
The event-delivery path binds the timestamp into the signed input to prevent replay. A receiver that verifies it as body-only will reject every delivery. Reconstruct the input as timestamp + "." + rawBody, using the timestamp from x-stateset-edi-timestamp.
Reject a delivery whose timestamp is outside your tolerance window β€” that’s what makes binding it useful.

Transports

See Transports for the file, SFTP, AS2, and AS1 variable groups.

Cryptography and key custody

EDI_SIGNING_STRICT=false adopts an explicit fail-open posture β€” events can be emitted unsigned. Use it only in development.

Alerting

Back-end adapters

Retention

All *_RETENTION_DAYS sweeps run hourly on the cluster monitor leader. 0 (default) keeps rows forever. See Operations.