Skip to main content
The FIS IBS integration includes several outbound (synchronous) runtime connectors. Backbase configures each connector in its own values.yaml file. For the environment details you send to Backbase, see Get started. FIS also provides a card issuing connector (gc-fis-device-administration-connector) that shares the fis-connector-sdk. It’s documented separately under card management. For details, see the FIS Cardbase Connector reference.

Configuration properties

Values to obtain from FIS

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

Common properties

Set these properties in values.yaml. They apply across all FIS IBS connectors.

gc-fis-deposit-connector

Set these properties in deposit-v0.values.yaml, in addition to the common properties.

gc-fis-deposit-transaction-connector

Set these properties in deposit-transactions-v0.values.yaml, in addition to the common properties.

gc-fis-loan-connector and gc-fis-loan-transaction-connector

Both connectors use the common properties, and coreMessageVisibility and normalizeNumericContainers as described for the deposit connector. Neither connector sets isEncryptionRequired; encryption follows the fis-connector-sdk default of true.

gc-fis-party-connector

Set these properties in party-v0.values.yaml and party-v2.values.yaml, in addition to the common properties. The properties apply to both party versions.

SOPS secrets

The connectors authenticate 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 IBS connectors expose the Banking OS Unified API. For the operation-to-endpoint tables per domain (deposit, deposit transactions, loan, party) and per API version, see Overview. For the full contract, see the API playground.

Events

These connectors are synchronous and do not publish or consume events.

Error mapping

The connector maps FIS IBS error codes to Banking OS status codes. For the full list, see Error codes. No connector-specific overrides exist for these connectors. When you set errorCodesToIgnore, the connector filters matching Metadata.MsgLst entries before it maps errors. Filtering is per entry: if a response includes both an ignorable code and a real error, only the real error is reported. If every non-blank MsgLst entry is ignorable, the connector leaves the response body unchanged and the call succeeds. Fault envelope errors always fail, regardless of errorCodesToIgnore.

Dependencies

  • FIS IBS REST API (outbound), reachable at fis.baseUrl.
  • FIS OAuth2 token endpoint (outbound), reachable at http.client.oauth2.token-url.
  • fis-connector-sdk (shared HTTP configuration, request encryption, and FIS error code mapping).