Skip to main content
The Alacriti Batch integration handles high-volume ACH (Automated Clearing House) processing with the Alacriti batch platform. The batch payment connector is outbound: it submits, validates, and cancels bulk payment instructions across the supported SEC codes. The batch payment inbound connector receives asynchronous batch and payment status webhooks from Alacriti and publishes events to the Sync Hub ASB producer. For setup steps, see Get started. For single (non-batch) Alacriti payments, see the Alacriti Connector reference.

Configuration properties

Values to obtain from Alacriti

Obtain the following values from Alacriti and set them in values.yaml. These values are environment-specific, so they have no default.

Common properties

Set these properties in values.yaml. They apply to both batch connectors.

gc-alacriti-batch-payment-connector

Set these properties in batch-payments-v0.values.yaml. This connector submits outbound ACH batches.

gc-alacriti-batch-payment-inbound-connector

Set these properties in inbound-batch-payments-v0.values.yaml. This connector receives Alacriti batch and payment status webhooks and publishes events to the Sync Hub ASB producer.

Supported operations

The Alacriti Batch Connector exposes the Grand Central Unified API for ACH batch submission, validation, and cancellation. For the operation-to-endpoint tables, see Overview. For the full contract, see the unified API specifications.

Events

The batch payment inbound connector publishes the following events to the Sync Hub ASB producer. The batch payment inbound connector consumes status notifications from the following sources. The batch payment connector is synchronous and doesn’t publish or consume events.

Error mapping

The connector maps Alacriti error codes to Grand Central status codes using the shared transform-alacriti-error-details.json template. For the full list, see Error codes.

Dependencies

  • Alacriti batch payment platform API (outbound), reachable at alacriti.baseUrl.
  • Alacriti batch and payment status webhooks (inbound), delivered to the registered callback URLs.
  • Sync Hub ASB producer, which receives the published batch status and payment status events.