values.yaml file. For the environment details you send to Backbase, 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 send it to your Backbase support team. Backbase sets it in the connectorvalues.yaml file. This value is environment-specific, so it has no default.
For OAuth deployments, also send
finastra.oauth.tokenUrl to your Backbase support team. Backbase sets it in the connector values.yaml file, not in a SOPS secret. 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 values may override connector defaults. Test and development environments may raise request and socket timeouts and set
http.client.proxy.activate to false.gc-finastra-party-connector
Set these properties inparty-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 indeposit-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. The connector maps the Finastra INTERIMAVAILABLE balance to availableBalance and the INTERIMCLEARED balance to currentBalance.
gc-finastra-deposit-transaction-connector
Set these properties indeposit-transaction-v0.values.yaml.
gc-finastra-loan-connector
Set these properties inloan-v0.values.yaml. Defaults are from the connector application.properties.
getLoanBalances calls GET {finastra.base.url}{finastra.create-loan.path}/{loanId} for each ID in the loanIds query parameter.
gc-finastra-loan-transaction-connector
Set these properties inloan-transaction-v0.values.yaml. Defaults are from the connector application.properties.
getLoanTransactionsForMultipleLoans calls GET {finastra.base.url}{finastra.loan-transactions.path}/{loanId}/transactions for each item in the request body.
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.
Test and development environments can omit the SOPS secret names. The connectors forward
Authorization and Ocp-Apim-Subscription-Key when the gateway uses subscription-key forwarding.
Supported operations
The Finastra Essence connectors expose the Banking OS 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 Banking OS status codes. For the full Banking OS list, see Error codes. Unmapped 4xx responses stayGC055 from finastra-connector-sdk. Vendor events arrays are shifted to causes through finastra-events-to-causes.json before that mapping.
The following table lists the shared mappings from finastra-connector-sdk. A connector mapping for the same vendor code takes precedence.
On get accounts by party ID, the party connector returns
GC055 when Finastra doesn’t recognize the party. A valid party with no accounts returns HTTP 200 with empty deposits and loans lists.
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. - Banking OS Unified API (party, deposit, and loan).
finastra-connector-sdkfor shared HTTP configuration and vendor error mapping.- FusionFabric.cloud OAuth2 when you configure SOPS client credentials and
finastra.oauth.tokenUrl.