Skip to main content
Before you can use the Open Banking connector, configure its two integrations: Salt Edge for consent management and the Backbase Engagement Banking Platform (EBP) for account information retrieval.

Prerequisites

Before you begin, ensure the following:
  • You have completed the steps in Get started with connectors.
  • You have an active contract with Salt Edge and your own accounts and credentials configured for Salt Edge services.
Open Banking connectors let you run separate connector instances for different lines of business (RETAIL and BUSINESS).
To enable line-of-business routing, set the openBankingLobEnabled property to true in the connector’s values.yaml file in gc-applications-live. Callers select the line of business by sending the Open-Banking-Lob HTTP header on each request to the Grand Central Unified API. Supported values are RETAIL and BUSINESS. The following table describes the routing behavior.

Configure connectors for Open Banking UK

Configure the Salt Edge connector

To configure your Salt Edge connector, follow these steps:
  1. Add your Azure API Management (APIM) subscription key to the request header:
    • Key: api-key
    • Value: <your subscription key>
  2. Request that the Grand Central team set up a connection with Salt Edge, and obtain the App-Id and App-Secret from Salt Edge. The Grand Central team configures these values as secrets in the APIM environment.
  3. Configure the Salt Edge base URL in gc-applications-live in the connector’s values.yaml file:
The following example shows the connector’s values.yaml file location:

Configure the Backbase EBP connector

To configure your Backbase EBP connector, follow these steps:
  1. Add your Azure API Management (APIM) subscription key to the request header:
    • Key: api-key
    • Value: <your subscription key>
  2. Create a ticket with the Managed Hosting team to set up a private link for the EBP environment.
  3. After the Managed Hosting team creates the private link, ask the Platform team to configure the connection from the Grand Central environment to the EBP environment.
  4. After the Platform team configures the connection, the EBP team updates their Istio policies to allow traffic over the private link.
  5. After you complete these steps, you receive the URL to access the EBP environment from Grand Central.
  6. Configure the Backbase base URL in gc-applications-live in the connector’s values.yaml file:
The following examples show the connector’s values.yaml file locations:

Configure connectors for Berlin Group EU

Configure the Salt Edge connector

To configure your Salt Edge connector, follow these steps:
  1. Add your Azure API Management (APIM) subscription key to the request header:
    • Key: api-key
    • Value: <your subscription key>
  2. Request that the Grand Central team set up a connection with Salt Edge, and obtain the App-Id and App-Secret from Salt Edge. The Grand Central team configures these values as secrets in the APIM environment.
  3. Configure the Salt Edge base URL in gc-applications-live in the connector’s values.yaml file:
The following example shows the connector’s values.yaml file location:

Configure the Backbase EBP connector

To configure your Backbase EBP connector, follow these steps:
  1. Add your Azure API Management (APIM) subscription key to the request header:
    • Key: api-key
    • Value: <your subscription key>
  2. Create a ticket with the Managed Hosting team to set up a private link for the EBP environment.
  3. After the Managed Hosting team creates the private link, ask the Platform team to configure the connection from the Grand Central environment to the EBP environment.
  4. After the Platform team configures the connection, the EBP team updates their Istio policies to allow traffic over the private link.
  5. After you complete these steps, you receive the URL to access the EBP environment from Grand Central.
  6. Configure the Backbase base URL in gc-applications-live in the connector’s values.yaml file:
The following examples show the connector’s values.yaml file locations: