Get started

Follow the steps in Get started before proceeding. FIS IBS access: An active account in the FIS IBS production or sandbox environment. Network connectivity: Verify that your network routes traffic between the FIS IBS environment and Grand Central iPaaS. For supported options, see Network connectivity. Environment details: You need the following environment details from FIS to configure the connector:

Parameter	Description
`fis-base-url`	The API endpoint URL for the FIS IBS environment.
`fis-client-id`	Client ID for OAuth token generation.
`fis-client-secret`	Client Secret for OAuth token generation.
`fis-organization-id`	Your organization identifier in FIS.
`fis-source-id`	Source identifier for API requests.
`ibs-authorization`	IBS authorization details (RACF ID and password).

Configuration guide

Follow these steps to initialize and authorize your FIS IBS Connector.

1. Establish connectivity

Share connectivity details between Grand Central and FIS IBS as described in Network connectivity.

VPN connectivity to the FIS IBS environment must be established before proceeding with configuration.

2. FIS IBS authentication

The FIS IBS Connector uses Basic Authentication for API access. To configure authentication, create a secret using Secrets Operations (SOPS). For more information, see How to create SOPS.

To share credentials between FIS IBS and Grand Central, consider using 1Password.

3. Environment configuration

To initialize the FIS IBS Connector, define the required environment variables in your gc-applications-live repository. These variables are stored in values.yaml for configuration common to all connectors, and in the following files for connector-specific configuration:

Connector	Property	Description
`gc-fis-deposit-connector`	`deposit-v0.values.yaml`	Outbound deposit connector for deposit account operations
`gc-fis-deposit-transactions-connector`	`deposit-transactions-v0.values.yaml`	Outbound deposit transactions connector for transaction operations
`gc-fis-loan-connector`	`loan-v0.values.yaml`	Outbound loan connector for loan account operations
`gc-fis-loan-transactions-connector`	`loan-transactions-v0.values.yaml`	Outbound loan transactions connector for transaction operations
`gc-fis-party-connector`	`party-v0.values.yaml`, `party-v2.values.yaml`	Outbound party connector for party management operations

For the full property list for each connector, including defaults and descriptions, see Reference.

Define common parameters

These variables are stored in values.yaml and are used across all FIS IBS connectors:

Parameter	Description	Example value
`fis.baseUrl`	Target API endpoint for the FIS IBS environment.	`https://api.fisglobal.com/rest`
`fis.organization-id`	Your organization identifier in FIS.	`YOUR_ORGANIZATION_ID`
`fis.source-id`	Source identifier for API requests.	`YOUR_SOURCE_ID`
`fis.security-token-type`	Security token type for authentication.	`OAuth2`
`enableValidation`	Enable or disable input validation for operations.	`false`
`isEncryptionRequired`	Enables encryption for sensitive data in API requests.	`false`
`client.ssl.ca.cert.path`	Path to the SSL CA certificate for secure connections.	`/etc/camel/conf.d/_secrets/fis-secret/fis-cert.jks`
`http.client.oauth2.token-url`	OAuth2 token endpoint URL for FIS authentication.	`https://api.fisglobal.com/token`
`http.client.oauth2.grant-type`	OAuth2 grant type for authentication.	`client_credentials`
`http.client.oauth2.client.assertion.required`	Specifies whether client assertion is required for OAuth2.	`false`

The following example shows the values.yaml configuration:

# Common FIS IBS Configuration
# Place this in: values.yaml
connector:
  properties:
    # FIS IBS Connection Settings
    # fis.baseUrl: <FIS_API_Endpoint>
    # fis.organization-id: <Organization_ID>
    # fis.source-id: <Source_ID>
    # fis.security-token-type: <Security_Token_Type>
    # enableValidation: <true|false>
    # isEncryptionRequired: <true|false>
    # client.ssl.ca.cert.path: <SSL_Certificate_Path>
    
    # OAuth2 Configuration
    # http.client.oauth2.token-url: <OAuth2_Token_URL>
    # http.client.oauth2.grant-type: <Grant_Type>
    # http.client.oauth2.client.assertion.required: <true|false>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Place the values files at the following paths:

iPaaS/azure/runtimes/{runtime}/values/gc-fis/
├── values.yaml
├── deposit-v0.values.yaml
├── deposit-transactions-v0.values.yaml
├── loan-v0.values.yaml
├── loan-transactions-v0.values.yaml
├── party-v0.values.yaml
└── party-v2.values.yaml

Define deposit connector parameters

For the deposit connector, configure the following parameters: Deposit configuration (deposit-v0.values.yaml):

Parameter	Description	Example value
`trimPartyId`	Enables trimming of party ID values to remove leading/trailing whitespace.	`false`

# Deposit Connector Configuration
# Place this in: deposit-v0.values.yaml
connector:
  properties:
    # Deposit connector specific parameters
    # trimPartyId: <true|false>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define deposit-transactions connector parameters

For the deposit-transactions connector, configure the following parameters: Deposit transactions configuration (deposit-transactions-v0.values.yaml):

Parameter	Description	Example value
`isIntradayEnabled`	Enable or disable intraday transaction processing. Set to `N` to disable.	`N`

# Deposit Transactions Connector Configuration
# Place this in: deposit-transactions-v0.values.yaml
connector:
  properties:
    # Deposit transactions connector specific parameters
    # isIntradayEnabled: <Y|N>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define loan connector parameters

For the loan connector, use the following configuration: Loan configuration (loan-v0.values.yaml):

# Loan Connector Configuration
# Place this in: loan-v0.values.yaml
connector:
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define party connector parameters

For the party connector, configure the following parameters based on the version you’re using: Party v0 and v2 configuration (party-v0.values.yaml, party-v2.values.yaml):

Parameter	Description	Example value
`trimPartyId`	Enables trimming of party ID values to remove leading/trailing whitespace.	`true`

# Party Connector Configuration
# Place this in: party-v0.values.yaml, party-v2.values.yaml
connector:
  properties:
    # Party connector specific parameters
    # trimPartyId: <true|false>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

These parameters apply to both party v0 and party v2 connectors.

Testing the connector

After configuration, test the connector using the API key authentication:

Header	Value
`api-key`	`<your_subscription_key>`

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 gateway cannot establish a handshake with the FIS IBS endpoint. This typically indicates an upstream service outage at FIS or a network routing failure.Solution: Verify the operational status of the FIS IBS environment with FIS. If the service is operational, contact Grand Central Support.

5XX: Timeout from core / Read timeout / SocketTimeoutException

Cause: The request to FIS IBS times out before receiving a response. This may indicate high latency or an unresponsive endpoint.Solution: Verify the operational status of the FIS IBS environment. If the service is operational, contact Grand Central Support.

Invalid OAuth token

Cause: The client-id or client-secret provided during setup is incorrect.Solution: Verify your credentials with FIS and contact the Grand Central team to update the connection.

Invalid ibs-authorization

Cause: The ibs-authorization header is missing or contains invalid credentials.Solution: Verify your RACF ID and password with FIS, and ensure the authorization header is correctly formatted.

429: Rate limit exceeded

Cause: The number of incoming requests exceeds the defined threshold for your subscription tier. This “429 Too Many Requests” response protects the stability of the Grand Central and FIS IBS infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact the Grand Central team to request a higher rate limit.

Need more help?

Contact support

Contact the Grand Central team for help with environment setup or rate limit increases.

Overview

Grand Central connectors

Release notes

Configuration guide

1. Establish connectivity

2. FIS IBS authentication

3. Environment configuration

Define common parameters

Define deposit connector parameters

Define deposit-transactions connector parameters

Define loan connector parameters

Define party connector parameters

Testing the connector

Troubleshooting

Need more help?

Contact support

​Configuration guide

​1. Establish connectivity

​2. FIS IBS authentication

​3. Environment configuration

​Define common parameters

​Define deposit connector parameters

​Define deposit-transactions connector parameters

​Define loan connector parameters

​Define party connector parameters

​Testing the connector

​Troubleshooting

​Need more help?

Contact support

Configuration guide

1. Establish connectivity

2. FIS IBS authentication

3. Environment configuration

Define common parameters

Define deposit connector parameters

Define deposit-transactions connector parameters

Define loan connector parameters

Define party connector parameters

Testing the connector

Troubleshooting

Need more help?