Skip to main content

​
Prerequisites

Before initiating the configuration, ensure you have the following credentials and connectivity in place:
  • Make sure that you have followed Get started with connectors.
  • Alacriti Access: An active account in the Alacriti environment.
  • Network Connectivity: Confirmed routing between the Alacriti environment and the Grand Central (GC) iPaaS.
  • Environment Details: Following environment variables are needed from Alacriti to configure the connector:
KeyDescription
alacriti.baseUrlThe base URL to access the Alacriti environment
alacriti.client_keyThe unique identifier assigned to the client by Alacriti

​
Configuration guide

Follow these steps to initialize and authorize your Alacriti connector.

​
1. Establishing connectivity

Share the following details with Grand Central team to establish secure connectivity between Grand Central and Alacriti
  • Environment Details: baseUrl and ipaddress of Alacriti application.

​
2. Environment configuration

To initialize the Alacriti connector, you must define specific environment variables within your gc-applications-live repository. These variables are stored in the paymentsv01.values.yaml file and handle both outbound request metadata and inbound webhook events.

​
Define outbound parameters

These variables authorize and route requests sent from Grand Central to Alacriti.
KeyDescription
alacriti.baseUrlTarget API endpoint for the Alacriti gateway.
alacriti.client_keyUnique organizational identifier assigned by Alacriti.
alacriti.client_requestor_referenceMandatory: Internal identifier for audit logging.
alacriti.productThe specific Alacriti module (e.g., ACH, FedNow).
retryFlagSet to true to enable automatic request retries.

​
Define inbound/webhook parameters

Configure how Grand Central receives asynchronous updates from Alacriti to GC.
KeyDescription
asb.event.versionVersion of the Async Service Bridge (ASB) schema.
asb.producer.apiUriThe callback URI for receiving incoming events.
backbase.gc.enable.batch.rejectionEnables logic to handle full batch rejections.
Below is a sample paymentsv01.values.yaml: 
# Sample Alacriti batch environment configuration
alacriti.baseUrl: "https://api.alacriti.com"
alacriti.client_key: "your_client_key"
alacriti.client_requestor_reference: "your_reference"
alacriti.product: "ACH"
retryFlag: true
Below is the path where the paymentsv01.values.yaml needs to be placed: 
├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-alacriti
                └── payments-v0.values.yaml

​
Testing your integration

To access the Payments Unified API, you must include your Grand Central subscription key in the request header. If you do not have a key, please contact the Grand Central Support Team to have one provisioned.
KeyValue
api-key<your_subscription_key>
Webhook Registration: To process asynchronous updates (e.g., successful settlements or network rejections), you must register your environment’s callback URL in the Alacriti Portal.
Test the API using the Postman Collection

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Grand Central (GC) gateway cannot establish a handshake with the Alacriti endpoint. This typically indicates an upstream service outage at Alacriti or a network routing failure.Solution: Verify the operational status of the Alacriti environment with Alacriti. If the service is operational, contact GC Support.
Cause: The request to Alacriti timed out before receiving a response. This may indicate high latency or an unresponsive endpoint.Solution: Verify the operational status of the Alacriti environment. If the service is operational, contact GC Support.
Cause: The client_id or client_secret provided during setup is incorrect.Solution: Re-verify your credentials with the Alacriti portal and contact the GC team to update the connection.
Cause: The number of incoming requests has exceeded the defined threshold for your subscription tier. This “429 Too Many Requests” response is a protective measure to ensure the stability of the Grand Central and Core Banking infrastructure.Solution: Review your application’s request patterns to identify unexpected spikes. If your business requirements have evolved and you require a higher throughput, contact the Grand Central Team to request an adjustment to your APIM rate limit policy.

​
Need more help?

Contact support

Reach out to the Grand Central team for assistance with environment setup or rate limit increases.