Skip to main content
The Finastra Essence connector family provides pre-built connectivity with Finastra Fusion Essence through FusionFabric.cloud (FFDC) retail banking APIs. It integrates with party management, deposit accounts, and deposit account balances.

​
Supported use cases

Party management

Search and retrieve parties, create personal customers, and list accounts by party

Deposit accounts

Create current accounts and savings accounts, retrieve deposit details by ID, and fetch balances for one or more deposit IDs

Account origination

Create parties and deposit accounts when write journeys are enabled

​
Connector artifacts

The following table lists the connector artifacts in this family.

​
Supported operations

The Finastra Essence connector family supports the following operations from the Grand Central Unified API specification. Vendor calls use finastra.base.url plus the path properties in Reference.

​
Party

The following table lists the party operations.
For account-list calls, the connector sends the Grand Central partyId to Finastra as the customerId, so treat the two identifiers as the same value when you troubleshoot 404 responses. The connector also maps the Grand Central partyType (PERSON or ORGANISATION) to the matching Essence party type code.

​
Deposit account

The following table lists the deposit account operations. The connector handles each deposit operation as follows:
  • Create a deposit account creates current accounts and savings accounts. The finastra.casa.deposit-types property in deposit-v0.values.yaml lists the Grand Central deposit types that the connector routes to Finastra. The default values are CURRENT_ACCOUNT and SAVINGS_ACCOUNT. The connector returns HTTP 400 for any other deposit type, and rejects a holderType of ORGANISATION in the create deposit request. This operation doesn’t create term deposits.
  • Get deposit account details looks up the deposit as a current or savings account first, then enriches the result with account details. When that probe returns vendor code 40311807, the connector retrieves the deposit as a fixed deposit. Other vendor errors on that probe follow the connector error path and do not fall through to a fixed deposit. The connector includes a balance for current and savings deposits when the balance lookup succeeds. Fixed-deposit lookups omit that enrichment.
  • Get deposit account balances retrieves a balance for each ID in the depositIds request header.
Deposit transactions come from the gc-finastra-deposit-transaction-connector artifact, not gc-finastra-deposit-connector. That artifact serves GET /deposits/{depositId}/transactions. Loan operations are outside the scope of this documentation set, although GET /parties/{partyId}/accounts can return loan accounts alongside deposit accounts.

​
API features

FFDC integration

OAuth2 client credentials and subscription key access to FusionFabric.cloud retail banking APIs

Data mapping

JOLT transformations between the Grand Central Unified API and Finastra payloads

Parallel processing

Concurrent vendor calls for party account aggregation

Correlation

X-Request-ID on outbound calls for traceability
  • Reference for configuration properties and vendor error mapping.
  • Get started for OAuth setup and values files.
  • Error codes for the full list of Grand Central error codes and their descriptions.