Skip to main content
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: The following environment variables are needed from Alacriti to configure the connector:
Environmental KeyDescription
alacriti-urlThe 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 Batch 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.
    Istio configuration: To add Alacriti IPs and DNS to the allowlist, see this page which describes how to configure Istio and how to add IPs and certificates to the allowlist.

​
2. Environment configuration

To initialize the Alacriti Batch connector, you must define specific environment variables within your gc-applications-live repository. These variables are stored in the values.yaml for common parameters and batch-payments-v0.values.yaml file for outbound request and batch-inbound-payments-v0.values.yaml for inbound webhook events.

​
Define common parameters

These variables are used across both outbound and inbound connectors connecting Grand Central to Alacriti and Alacriti to Grand Central.
values.yamlDescriptionEnvironmental Key
alacriti.baseUrlTarget API endpoint for the Alacriti gateway.alacriti-url
alacriti.client_keyUnique organizational identifier assigned by Alacriti.alacriti-client-key
alacriti.client_requestor_referenceMandatory: Internal identifier for audit logging.
alacriti.productProducts to indicate what type of transfers are supported (eg: business_transfer)
alacriti.payment_channelPayment channel to identify its business banking or retail baning or any other channel (eg: business_banking)
alacriti.requestor_typeWho is requesting the payment as its a party or company or any mode (eg: party)
alacriti.access_channelIf mutiple organisation or banks inside main organisation we can split it into various access channel (eg: backbase_business)
Below is a sample values.yaml: 
# Sample Alacriti Environment Configuration
connector:
  properties:
    alacriti.baseUrl: https://demoapi.orbipay.com
    alacriti.client_key: AB1CDE23FG
    alacriti.client_requestor_reference: Test
    alacriti.product: business_transfers
    alacriti.payment_channel: business_banking
    alacriti.requestor_type: party
    alacriti.client_requestor_reference: Test
    alacriti.access_channel: backbase_business
Below is the path where the values.yaml needs to be placed: 
├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-alacriti
                └── values.yaml

​
Define outbound parameters

These variables along with common parameters in values.yamlare to authorize and route requests sent from Grand Central to Alacriti.
batch-payments-v0.values.yamlDescriptionEnvironmental Key
retryFlagSet to true to enable automatic request retries.
Below is a sample batch-payments-v0.values.yaml: 
# Sample Alacriti Batch Outbound Environment Configuration
connector:
  properties:
    retryFlag: true

  traits:
    knativeservice:
      # IMPORTANT: Cost-related. Keeping minScale >0 causes continuous cost even when idle.
      # With minScale: 0, each request grants 30 min uptime (extended if new requests arrive).
      # Use >0 only if hot start is required, and reset to 0 afterward to avoid unnecessary cost.
      minScale: 0
    logging:
      # DEBUG adds significant log output during startup and runtime.
      # This can noticeably slow down starts due to extra logging work and I/O.
      # Use only for troubleshooting and disable when not needed.
      level: INFO
Below is the path where the batch-payments-v0.values.yaml needs to be placed: 
├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-alacriti
                └── batch-payments-v0.values.yaml

​
Define inbound/webhook parameters

Configure along with common parameters in values.yaml on how Grand Central receives asynchronous updates from Alacriti to GC.
Set up the sync-hub component as described in Sync Hub. The following ASB variables are available after configuring Sync Hub. This is a mandatory component for inbound connectivity.
Webhook registration: To process asynchronous updates (for example, successful settlements or network rejections), you must register your environment’s callback URL in the Alacriti Portal.
inbound-batch-payments-v0.values.yamlDescription
asb.producer.apiUriThe callback URI for receiving incoming events.
asb.batch.status.update.event.topicThe ASB topic to send messages for batch status updates
asb.batch.payment.status.update.event.topicThe ASB topic to send messages for payment status updates
asb.batch.status.update.event.typeThe ASB event type to send messages for batch status
asb.batch.payment.status.update.event.typeThe ASB event type to send messages for payment status
asb.event.sourceThe ASB source to send messages.
asb.event.versionVersion of the Async Service Bridge (ASB) schema.
asb.event.typeEvent type of the Async Service Bridge (ASB) schema.
retryFlagSet to true to enable automatic request retries.
Below is a sample inbound-batch-payments-v0.values.yaml: 
# Sample Alacriti Inbound Environment Configuration
connector:
  customLabels:
    app.gcservices.io/synchub-enabled: "true"
    app.gcservices.io/synchub-type: "producer"
  properties:
    retryFlag: true
    asb.batch.status.update.event.type: com.backbase.paymentbatchintegration.event.spec.v1.BatchStatusUpdateEvent
    asb.batch.payment.status.update.event.type: com.backbase.paymentbatchintegration.event.spec.v1.BatchPaymentStatusUpdateEvent
    asb.batch.status.update.event.topic: batch-orders
    asb.batch.payment.status.update.event.topic: batch-payments
    asb.producer.apiUri: http://wiremock-obpm-payments.gc-obpm.svc.cluster.local:9021
	asb.event.type: com.backbase.paymentbatchintegration.event.spec.v1.BatchStatusUpdateV1Event
    asb.event.source: com.backbase.payments
    asb.event.version: 1.0.0  
traits:
    knativeservice:
      # IMPORTANT: Cost-related. Keeping minScale >0 causes continuous cost even when idle.
      # With minScale: 0, each request grants 30 min uptime (extended if new requests arrive).
      # Use >0 only if hot start is required, and reset to 0 afterward to avoid unnecessary cost.
      minScale: 0
    logging:
      # DEBUG adds significant log output during startup and runtime.
      # This can noticeably slow down starts due to extra logging work and I/O.
      # Use only for troubleshooting and disable when not needed.
      level: INFO
CustomLabels: CustomLabels are part of the Sync Hub setup. Once Sync Hub is enabled, adding the customLabels to the connector automatically invokes the Sync Hub URLs.
Below is the path where the inbound-batch-payments-v0.values.yaml needs to be placed: 
├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-obpm
                └── inbound-batch-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 integration: Share the API Key through 1Password or any standard tool with Alacriti to call the inbound APIs.
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 the GC Support team.
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 the GC Support team.
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.