Skip to main content
The Alacriti integration bridges Banking OS and the Alacriti payment platform for Fedwire, FedNow, and Real-Time Payments (RTP). The payment connector is outbound: it transforms Banking OS Unified API payloads into rail-specific instructions. The payment inbound connector receives asynchronous status webhooks from Alacriti and publishes events to the Sync Hub ASB producer. For the environment details you send to Backbase, see Get started. For batch (mass) payments, see the Alacriti Batch Connector reference.

Configuration properties

Values to obtain from Alacriti

Obtain the following values from Alacriti and send them to your Backbase support team. Backbase sets them in payments-v0.values.yaml. These values are environment-specific, so they have no default.

gc-alacriti-payment-connector

Set these properties in payments-v0.values.yaml. This connector sends outbound requests to Alacriti.

gc-alacriti-payment-inbound-connector

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

Supported operations

The Alacriti Connector exposes the Banking OS Unified API across the Fedwire, FedNow, and RTP rails. For the operation-to-endpoint tables, see Overview. For the full contract, see the API playground.

Events

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

Error mapping

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

Dependencies

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