Skip to main content
This page describes the prerequisites and configuration steps you need to integrate the FIS Cardbase connector.

​
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.
  • FIS Cardbase Access: An active account in the FIS Cardbase environment.
  • Network Connectivity: Confirmed routing between the FIS Cardbase and the Grand Central (GC) iPaaS.
  • Environment details: The following table shows the environment variables needed from FIS Cardbase to configure the connector:
    KeyDescription
    client-idUnique public key generated by FIS to generate OAuth Token
    client-secretSecret password shared by FIS to generate OAuth Token
    ibs-authorizationKey consisting of **RACF ID(Resource Access Control Facility user identifier )** used by FIS for authentication and access control and password
    fis.baseUrlBase url of the FIS Application
    fis.organization-idInternal identifier used to designate your financial institution within the broader FIS system and its related applications
    fis.source-idIdentifies the application invoking the API

​
Configuration guide

Follow these steps to initialize and authorize your FIS Cardbase connector. 1. Establish connectivity Share the following details with the Grand Central team to establish secure connectivity between Grand Central and FIS Cardbase.
  • Environment Details baseUrl and ‘IP address’ of FIS application.
  • OAuth2 Credentials: client-id and client-secret for OAuth token generation.
  • Authorization: ibs-authorization details
2. Configure your environment Define your environment variables in the gc-applications-live repository within the device-administration-v0.values.yaml file. Here we need to configure values for following parameters:
  • fis.baseUrl
  • fis.organization-id
  • fis.source-id
Below is a sample device-administration-v0.values.yaml: 
# Sample FIS environment configuration
fis.baseUrl: "[https://api.tietoevry.sandbox.com](https://api.tietoevry.sandbox.com)" # Target environment URL
fis.organization-id: "ORG_12345"
fis.source-id: "SRC_98765"
Below is the path where the device-administration-v0.values.yaml needs to be placed: 
├── iPaaS
└── azure/runtimes
    ├── dev-v2
    └── test-v2
        └── values
            ├── gc-fis
                └── device-administration-v0.values.yaml

​
Testing your integration

To access the Cards 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>
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 FIS Cardbase endpoint. This typically indicates an upstream service outage at FIS or a network routing failure.Solution: Verify the operational status of the FIS Cardbase environment with FIS. If the service is operational, contact GC Support.
Cause: The Grand Central (GC) gateway cannot establish a handshake with the FIS Cardbase endpoint. This typically indicates an upstream service outage at FIS or a network routing failure.Solution: Verify the operational status of the FIS Cardbase environment with FIS. 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 FIS portal and contact the Grand Central 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.