Skip to main content
Backbase IO documents Grand Central integration for Digital Banking. The linked pages require a login. Access is limited to Backbase staff, partners, and customers. If you don’t have access, contact your Backbase account team.
Use this page when you integrate Backbase Digital Banking with Grand Central. It links to the Backbase IO documentation for each integration point. The following diagram shows the two mechanisms that Digital Banking and Grand Central use to exchange data: Digital Banking encompasses Foundation Services, Identity, Banking Services, Digital Investing, Digital Onboarding, Digital Lending, Flow Foundation, and Engage Services.

​
Integration methods

Digital Banking integrates with Grand Central in two ways:
  • REST API: Digital Banking services call Grand Central unified APIs directly or through an adapter.
  • Sync Hub (event-based): Grand Central publishes events on Sync Hub and Digital Banking services ingest them to keep local data in sync.
Not every Backbase backend service integrates with Grand Central. Some services are standalone and don’t rely on a third-party system.

​
REST API integration scenarios

Digital Banking services that use REST APIs to integrate with third-party systems define three types of integration APIs:
  • Outbound: The Digital Banking service calls this API to push changes to the external system.
  • Pull: The Digital Banking service calls this API to fetch updates from an external system.
  • Inbound (out of scope): The Digital Banking service exposes this API. The external system pushes changes to the Digital Banking service (often through an integration service). Inbound integrations are out of scope for Grand Central. Grand Central only uses events through Sync Hub to push changes to the Digital Banking services.
Grand Central doesn’t support the outbound and pull integration APIs. It only supports its unified APIs. To integrate with Grand Central, Digital Banking services either call the unified APIs instead of their outbound or pull APIs, or they use an adapter service to mediate between those APIs.

​
Scenario 1: Integration through an adapter

The Digital Banking service calls an adapter that implements its outbound integration API and consumes the corresponding unified API in Grand Central. A Grand Central-managed connector serves the unified API. The following diagram shows this flow: The following table lists the Digital Banking services that have an adapter:

​
Scenario 2: Direct integration

The Digital Banking service directly calls the unified API in Grand Central. A Grand Central-managed connector serves the unified API. The following diagram shows this flow: The following table lists the Digital Banking services that directly call unified APIs:

​
Scenario 3: Custom adapter

The following table lists the Digital Banking services that need a custom adapter. The adapter implements their outbound or pull API and calls the Grand Central unified API. Some of these services also ship with a connector that integrates directly with an external system and doesn’t use Grand Central.

​
Sync Hub integration

The following table lists the Digital Banking services that ingest events from Sync Hub to receive data from Grand Central. For an overview of event distribution, see Sync Hub overview.

​
Not applicable or no integrations

Some Backbase backend services don’t integrate with Grand Central because Grand Central does not have unified APIs for their purpose or because they don’t rely on a third-party system.
The following table lists the Digital Banking services that have integrations that are not covered by Grand Central unified APIs. Some ship with a connector that directly integrates with an external system without Grand Central.
The following table lists the Digital Banking services that have no integrations:

​
Backend service inventory

The following table lists all Digital Banking services, grouped by domain and capability with their integration scenarios (excluding Sync Hub).