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: The following table shows the environment variables you need from Alacriti to configure the connector:
KeyDescriptionEnvironment key
alacriti.baseUrlThe base URL to access the Alacriti environmentalacriti-base-url
alacriti.client_keyThe unique identifier assigned to the client by Alacritialacriti-client-key

​
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 the Alacriti application.

​
2. Environment configuration

To initialize the Alacriti connector, define specific environment variables within your gc-applications-live repository. Store these variables in the payments-v0.values.yaml file for outbound requests and inbound-payments-v0.values.yaml for inbound webhook events.

​
Define outbound parameters

The following table shows variables that 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.productProducts to indicate what type of transfers are supported (for example, business_transfer).
alacriti.payment_channelPayment channel to identify if its business banking or retail banking or any other channel (for example, business_banking).
alacriti.requestor_typeWho is requesting the payment as its a party or company or any mode (for example, party).
alacriti.access_channelIf multiple organizations or banks inside main organization you can split it into various access channels (for example, backbase_business).
retryFlagSet to true to enable automatic request retries.
Below is a sample payments-v0.values.yaml: 
# 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.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
Below is the path where the payments-v0.values.yaml file needs to be placed: 
├── 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. The following table shows the inbound payment connector parameters:
KeyDescription
asb.event.versionVersion of the Async Service Bridge (ASB) schema.
asb.producer.apiUriThe callback URI for receiving incoming events.
asb.event.topicThe ASB topic to send messages.
asb.event.typeThe ASB event type to send messages.
asb.event.sourceThe ASB source to send messages.
Below is a sample inbound-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.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://asb-producer-v0.synchub-producer.svc.cluster.local
  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 inbound-payments-v0.values.yaml file needs to be placed: 
├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-alacriti
                └── inbound-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, contact the Grand Central Support Team to have one provisioned.
KeyValue
api-key<your_subscription_key>
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.
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.