Skip to main content
The Grand Central Alacriti Batch Connector provides a standardized interface for high-volume ACH (Automated Clearing House) processing. It bridges the gap between your internal systems and Alacriti’s batch platform, allowing for the submission, validation, and status tracking of bulk payment instructions. By utilizing the Grand Central Unified API, this connector abstracts the complexities of NACHA file formatting and SEC code specific requirements.

​
Supported use cases

The connectors are designed to handle diverse ACH workflows, ranging from payroll to corporate tax settlements. The following use cases are supported using Alacriti Batch outbound and inbound connectors.

​
ACH SEC code support

The connectors support multiple Standard Entry Class (SEC) codes to ensure compliance across different transaction types:
  • PPD: Prearranged Payment and Deposit (Consumer accounts, for example, Payroll).
  • CCD / CCD+: Corporate Credit or Debit (B2B payments, including Child Support and Tax payments).
  • CTX: Corporate Trade Exchange (B2B with extended remittance information).

​
Processing capabilities

  • Standard & Same-Day ACH: Flexibility to choose between standard clearing cycles or Same-Day ACH for urgent settlements.
  • Batch Lifecycle Management: Submit entire batches for pre-validation or trigger full/partial cancellations for pending instructions.
  • Account Verification: Supports Prenote validation to verify recipient account details before actual funds transfer.

​
Asynchronous status tracking

Because ACH is not an instant rail, the connector relies on webhooks, which are delivered through the Alacriti Batch inbound connector.
  • Use the /batch/statusupdate for high-level lifecycle events.
  • Use /payment/paymentupdate to handle ACH Returns (for example, R01 - Insufficient Funds) at the individual transaction level.

​
Supported Grand Central endpoints:

The following endpoints are implemented to manage the lifecycle of an ACH batch.
MethodEndpointOperation
POST/batchesBatch Submission & Pre-validation: Submits batch details to verify formatting and requirement compliance before processing.
PUT/batchesBatch Cancellation: Instructs the system to cancel an entire batch or specific instructions within a batch (provided they haven’t settled).
POST/webhooks/batch/statusupdateBatch Status Webhook: Asynchronous updates for the overall batch status (for example, Accepted, Rejected, Partially Processed).
POST/webhooks/payment/paymentupdateIndividual Status Webhook: Granular updates for specific payments within a larger batch (useful for tracking specific returns).

​
Technical considerations

​
Pre-validation logic

Before a batch is moved to “Settlement” status, the connector performs a pre-validation check. This ensures that:
  1. Total credit/debit counts match the header.
  2. Routing numbers pass checksum validation.
  3. Required addenda records for specific SEC codes (like CCD/CTX) are present.