Skip to main content
The Finastra Essence integration includes three runtime connectors. Configure each connector in its own values.yaml file under values/gc-finastra/. For setup steps, see Get started. The following table lists the connector artifacts and property files.

Configuration properties

Values to obtain from Finastra

Obtain the following value from Finastra Fusion Essence or your FusionFabric.cloud (FFDC) subscription and set it in the connector values.yaml file. This value is environment-specific, so it has no default. For OAuth deployments, also set finastra.oauth.tokenUrl in the connector values.yaml file (not in SOPS). Example: https://api.fusionfabric.cloud/login/v1/sandbox/oidc/token.
The HTTP client properties in the following sections tune the outbound connection pool and timeouts. Deployed gc-applications-live values may override connector defaults. Test and development overlays under values/gc-finastra/ may raise request and socket timeouts and set http.client.proxy.activate to false.

gc-finastra-party-connector

Set these properties in party-v2.values.yaml. Defaults are from the connector application.properties. Use the connector property names above. Overlay files must match those keys.

gc-finastra-deposit-connector

Set these properties in deposit-v0.values.yaml. Defaults are from the connector application.properties. getDepositBalances calls GET {finastra.base.url}{finastra.get-account.path}/{depositId}/balances for each ID in the depositIds header.

gc-finastra-deposit-transaction-connector

Set these properties in deposit-transaction-v0.values.yaml.

SOPS secrets

SOPS secret: finastra-client-id

The following table lists the SOPS secret for the FFDC OAuth client ID.

SOPS secret: finastra-client-secret

The following table lists the SOPS secret for the FFDC OAuth client secret. For more information about test and development values files and subscription-key forwarding, see Get started.

Supported operations

The Finastra Essence connectors expose the Grand Central Unified API. For the operation-to-endpoint tables, 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 connectors map Finastra vendor codes to Grand Central status codes. For the full Grand Central list, see Error codes. Unmapped 4xx responses stay GC055 from finastra-connector-sdk. Vendor events arrays are shifted to causes through finastra-events-to-causes.json before that mapping. The following table lists deposit connector mappings from application.properties. Do not map vendor code 40311807. Get deposit by ID uses that code as the CASA-first breaker and falls through to the fixed-deposit path.

Dependencies

  • Finastra Fusion Essence retail HTTP APIs, reachable at finastra.base.url.
  • Grand Central Unified API (party and deposit).
  • finastra-connector-sdk for shared HTTP configuration and vendor error mapping.
  • FusionFabric.cloud OAuth2 when you configure SOPS client credentials and finastra.oauth.tokenUrl.