Integration methods
Digital Banking integrates with Banking OS in two ways:- REST API: Digital Banking services call Banking OS unified APIs directly or through an adapter.
- Sync Hub (event-based): Banking OS publishes events on Sync Hub and Digital Banking services ingest them to keep local data in sync.
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 Banking OS. Banking OS only uses events through Sync Hub to push changes to the Digital Banking services.
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 Banking OS. A Banking OS-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 Banking OS. A Banking OS-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 Banking OS unified API. Some of these services also ship with a connector that integrates directly with an external system and doesn’t use Banking OS.Sync Hub integration
The following table lists the Digital Banking services that ingest events from Sync Hub to receive data from Banking OS. For an overview of event distribution, see Sync Hub overview.Not applicable or no integrations
Some Backbase backend services don’t integrate with Banking OS because Banking OS does not have unified APIs for their purpose or because they don’t rely on a third-party system.List of services that are not applicable to Banking OS
List of services that are not applicable to Banking OS
The following table lists the Digital Banking services that have integrations that are not covered by Banking OS unified APIs.
Some ship with a connector that directly integrates with an external system without Banking OS.
List of services that have no integrations
List of services that have no integrations
The following table lists the Digital Banking services that have no integrations:
Backend service inventory
Full backend service inventory
Full backend service inventory
The following table lists all Digital Banking services, grouped by domain and capability with their integration scenarios (excluding Sync Hub).
Related topics
- Banking OS: platform overview and connector catalog
- Architecture: how Engagement Banking Platform services connect to Banking OS
- Sync Hub overview: event distribution between Banking OS and Digital Banking
- API playground: vendor-neutral API contracts for connectors
- HTTP Grand Central communication: synchronous HTTP calls from Engagement Banking Platform services to Banking OS (Backbase IO, login required)