Get started

Before initiating the configuration, ensure you have the following credentials and connectivity in place:

Follow the Get started with connectors guide.
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 Key	Description
`alacriti-url`	The base URL to access the Alacriti environment
`alacriti-client-key`	The unique identifier assigned to the client by Alacriti

GC managed connectors from shared ACR

The following table lists Alacriti managed connectors available in the GC shared Azure Container Registry (ACR) at gcshared671.azurecr.io/charts. Check your ACR for available versions.

Connector name	Chart path
gc-alacriti-batch-payment-connector	`charts/gc-alacriti-batch-payment-connector`
gc-alacriti-batch-payment-inbound-connector	`charts/gc-alacriti-batch-payment-inbound-connector`
gc-alacriti-payment-connector	`charts/gc-alacriti-payment-connector`
gc-alacriti-payment-inbound-connector	`charts/gc-alacriti-payment-inbound-connector`

Configuration guide

Follow these steps to initialize and authorize your Alacriti Connector.

1. Establish connectivity

Share the following details with the 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 Connector, you must define specific environment variables within your gc-applications-live repository. These variables are stored in payments-v0.values.yaml for outbound requests and inbound-payments-v0.values.yaml for inbound webhook events. For the full property list for each connector, including defaults and descriptions, see Reference.

Define outbound parameters

These variables authorize and route requests sent from Grand Central to Alacriti.

payments-v0.values.yaml	Description	Environmental Key
`alacriti.baseUrl`	Target API endpoint for the Alacriti gateway.	`alacriti-url`
`alacriti.client_key`	Unique organizational identifier assigned by Alacriti.	`alacriti-client-key`
`alacriti.client_requestor_reference`	Mandatory: Internal identifier for audit logging.
`alacriti.product`	Products to indicate what type of transfers are supported (eg: business_transfer)
`alacriti.payment_channel`	Payment channel to identify its business banking or retail baning or any other channel (eg: business_banking)
`alacriti.requestor_type`	Who is requesting the payment as its a party or company or any mode (eg: party)
`alacriti.access_channel`	If mutiple organisation or banks inside main organisation we can split it into various access channel (eg: backbase_business)
`retryFlag`	Set to `true` to enable automatic request retries.

The following is a sample payments-v0.values.yaml file:

# Sample Alacriti Outbound Environment Configuration
connector:
  properties:
    retryFlag: true
    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

  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

Place the payments-v0.values.yaml file in the following path:

├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-alacriti
                └── payments-v0.values.yaml

Define inbound/webhook parameters

Configure 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 share the Grand Central webhook url with Alacriti which needs to be registered.

inbound-payments-v0.values.yaml	Description
`asb.event.version`	Version of the Async Service Bridge (ASB) schema.
`asb.producer.apiUri`	The callback URI for receiving incoming events.
`asb.event.topic`	The ASB topic to send messages.
`asb.event.type`	The ASB event type to send messages.
`asb.event.source`	The ASB source to send messages.

The following is a sample inbound-payments-v0.values.yaml file:

# Sample Alacriti Inbound Environment Configuration
connector:
  customLabels:
    app.gcservices.io/synchub-enabled: "true"
    app.gcservices.io/synchub-type: "producer"
  properties:
    retryFlag: true
    asb.event.type: com.backbase.payment.event.spec.v1.PaymentOrderStatusEvent
    asb.event.source: com.backbase.payments
    asb.event.version: 1.0.0
    asb.event.topic: payment-status
    asb.producer.apiUri: http://wiremock-obpm-payments.gc-obpm.svc.cluster.local:9021
  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.

Place the inbound-payments-v0.values.yaml file in the following path:

├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-alacriti
                └── inbound-payments-v0.values.yaml

Test your integration

To access the Payments Unified API, you must include your Grand Central subscription key in the request header. If you don’t have a key, contact the Grand Central Support Team to request one.

Key	Value
`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.

5XX : Internal server error / Core system is down

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.

5XX : Timeout from Core / Read timeout / SocketTimeoutException

Invalid OAuth Token

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.

429: Rate limit exceeded

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.

Overview

Grand Central connectors

Release notes

GC managed connectors from shared ACR

Configuration guide

1. Establish connectivity

2. Environment configuration

Define outbound parameters

Define inbound/webhook parameters

Test your integration

Troubleshooting

Need more help?

Contact Support

​GC managed connectors from shared ACR

​Configuration guide

​1. Establish connectivity

​2. Environment configuration

​Define outbound parameters

​Define inbound/webhook parameters

​Test your integration

​Troubleshooting

​Need more help?

Contact Support

GC managed connectors from shared ACR

Configuration guide

1. Establish connectivity

2. Environment configuration

Define outbound parameters

Define inbound/webhook parameters

Test your integration

Troubleshooting

Need more help?