> ## Documentation Index
> Fetch the complete documentation index at: https://agenticbanking.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get started

> Configuration guide for FIS Cardbase Connector integration

export const VendorApiVersionTag = ({versions, label = "Supports"}) => {
  useEffect(() => {
    if (!versions || versions.length === 0) {
      return undefined;
    }
    const findAndSegmentStart = (reference, target) => {
      let i = 0;
      while (i < reference.length && i < target.length && reference[i] === target[i]) {
        i += 1;
      }
      let start = i;
      while (start > 0 && (/[0-9.vR]/).test(target[start - 1])) {
        start -= 1;
      }
      return start;
    };
    const formatText = () => {
      const suffix = " operations";
      if (versions.length === 1) {
        return `${label} ${versions[0]}${suffix}`;
      }
      const [first, ...rest] = versions;
      const last = rest[rest.length - 1];
      const andStart = findAndSegmentStart(first, last);
      const lead = first.slice(0, andStart);
      if (versions.length === 2) {
        return `${label} ${first} and ${last.slice(andStart)}${suffix}`;
      }
      const stems = versions.map(version => version.slice(andStart));
      return `${label} ${lead}${stems.slice(0, -1).join(", ")}, and ${stems[stems.length - 1]}${suffix}`;
    };
    const text = formatText();
    const mountCallout = () => {
      const titleRow = document.querySelector("#page-title")?.parentElement;
      if (!titleRow) {
        return null;
      }
      let callout = titleRow.querySelector("[data-vendor-api-version-callout='true']");
      if (!callout) {
        callout = document.createElement("div");
        callout.dataset.vendorApiVersionCallout = "true";
        callout.className = "vendor-api-version-callout vendor-api-version-callout--in-title";
        titleRow.appendChild(callout);
      }
      callout.replaceChildren();
      const textEl = document.createElement("span");
      textEl.className = "vendor-api-version-text";
      textEl.textContent = text;
      callout.appendChild(textEl);
      return callout;
    };
    let callout = mountCallout();
    if (callout) {
      return () => {
        callout?.remove();
      };
    }
    const observer = new MutationObserver(() => {
      callout = mountCallout();
      if (callout) {
        observer.disconnect();
      }
    });
    observer.observe(document.body, {
      childList: true,
      subtree: true
    });
    return () => {
      observer.disconnect();
      callout?.remove();
    };
  }, [versions, label]);
  return null;
};

export const vendorApiVersions = ["FIS Cardbase API v4.0"];

<VendorApiVersionTag versions={vendorApiVersions} />

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**](/connectors/getting-started).
* **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:

| Key                   | Description                                                                                                                                       |
| :-------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------ |
| `client-id`           | `Unique public key generated by FIS to generate OAuth Token`                                                                                      |
| `client-secret`       | `Secret password shared by FIS to generate OAuth Token`                                                                                           |
| `ibs-authorization`   | `Key consisting of **RACF ID(Resource Access Control Facility user identifier )** used by FIS for authentication and access control and password` |
| `fis.baseUrl`         | `Base url of the FIS Application`                                                                                                                 |
| `fis.organization-id` | `Internal identifier used to designate your financial institution within the broader FIS system and its related applications`                     |
| `fis.source-id`       | `Identifies 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**

For the full property list, including defaults and descriptions, see [Reference](/connectors/card-management/fis-cardbase/reference).

Define your environment variables in the `gc-applications-live` repository within the `device-administration-v0.values.yaml` file. Configure the following parameters:

* **fis.baseUrl**
* **fis.organization-id**
* **fis.source-id**

Below is a sample device-administration-v0.values.yaml:

```yaml theme={"system"}
# 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 use 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.

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

<AccordionGroup>
  <Accordion title="5xx: Internal server error / core system is down" icon="lock">
    **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**](mailto:gc_support@backbase.com).
  </Accordion>

  <Accordion title="5xx: Timeout from core / read timeout / SocketTimeoutException" icon="wifi-slash">
    **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**](mailto:gc_support@backbase.com).
  </Accordion>

  <Accordion title="Invalid OAuth token" icon="key">
    **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.
  </Accordion>

  <Accordion title="429: Rate limit exceeded" icon="gauge-high">
    **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.
  </Accordion>
</AccordionGroup>

## Need more help?

<Card title="Contact support" icon="envelope" href="mailto:support@grandcentral.io">
  Reach out to the Grand Central team for assistance with environment setup or rate limit increases.
</Card>