Skip to main content
This page explains the steps you need to take before you can start using your FIS IBS connector.

​
Prerequisites

Before you start, you require the following:
  • Make sure that you have followed Get started with connectors.
  • An active FIS account with the necessary permissions to access the FIS environment.
  • Valid API credentials from FIS such as username, password, and auth token information.

​
Configure the FIS IBS connector

To configure your connector, follow these steps:
  1. Set your APIM subscription key in the header as follows:
  • Key: api-key
  • Value: <your subscription key>
  1. Request the Grand Central team to set up a connection with FIS, and provide the following:
  • FIS client-id and client-secret for oAuth token generation.
  • ibs-authorization details.
  1. Configure the following details in gc-applications-live:
fis.baseUrl=<your_fis_base_url>  //FIS environment base URL
fis.organization-id=<your_organization_id>
fis.source-id=<your_source_id>
An example of the values.yaml file location: 
├── iPaaS
└── azure/runtimes
    ├── dev
    │   └── values
    │       └── gc-fis
    │           └── deposit-v0.values.yaml
    └── test
        └── values
            └── gc-fis
                └── deposit-v0.values.yaml

​
Testing your integration

To access the 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>

​
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 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 GC Support.
Cause: The request to FIS IBS timed 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 GC Support.
Cause: The client-id or client-secret provided during setup is incorrect.Solution: Re-verify your credentials with FIS and contact the GC team to update the connection.
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.
Cause: The number of incoming requests has exceeded the defined threshold for your subscription tier.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.