Skip to main content
The FIS Cardbase integration issues debit and credit cards through FIS Cardbase and links them to deposit accounts. It includes a single outbound (synchronous) connector, gc-fis-device-administration-connector. Backbase configures it in device-administration-v0.values.yaml. The connector shares the fis-connector-sdk with the FIS IBS connectors. For the environment details you send to Backbase, see Get started.

Configuration properties

Configure the connector in device-administration-v0.values.yaml.

Values to obtain from FIS

Obtain the following values from FIS and send them to your Backbase support team. Backbase sets them in device-administration-v0.values.yaml. These values are environment-specific, so they have no default.

gc-fis-device-administration-connector

Set the following tunable properties in device-administration-v0.values.yaml.

SOPS secrets

The connector authenticates to FIS with OAuth2 and a custom ibs-authorization header. Obtain the following credentials from FIS. Backbase stores them in a SOPS secret.

Supported operations

The FIS Cardbase Connector exposes the Banking OS Unified API for card number generation, card issuing, and account linking. For the operation-to-endpoint table, see Overview. For the full contract, see the API playground.

Events

This connector is synchronous and doesn’t publish or consume events.

Error mapping

The connector maps FIS error codes to Banking OS status codes using the shared transform-fis-error-details.json template. For the full list, see Error codes.

Dependencies

  • FIS Cardbase REST API (outbound), reachable at fis.baseUrl.
  • FIS OAuth2 token endpoint (outbound), for Bearer token authentication.
  • fis-connector-sdk (shared HTTP configuration, request encryption, and FIS error code mapping).