Engines
The following diagram shows the engines in the control plane and the matching tenant APIs in a tenant installation: Banking OS has a connector engine and an agent engine. Each engine has a control-plane API and a tenant API.Connector engine
The connector engine includes Connector Studio. You use Connector Studio to design a connector, including its Camel routes. For more information, see Connector Studio overview and Route Builder. The connector tenant API runs that connector in the tenant installation. A connector implements a unified API specification or a custom API that you build. For more information, see Get started with connectors and the API playground.Agent engine
The agent engine is the Banking OS Agent Platform. You build agents on the platform, and the platform runs those agents. For more information, see Banking OS Agent Platform overview.Integration and hosting
A call reaches a system of record through Azure API Management (APIM), a unified API or a custom API, and a connector. You use OAuth 2.0 to authorize the call. The following sections describe API management, managed connectors, and Managed Hosting. For more information about unified APIs and BIAN, see Unified APIs and BIAN.API management
APIM is the managed gateway for Banking OS APIs. It creates, publishes, monitors, and governs APIs. Between backend services and API consumers, APIM enforces authentication, rate limiting, and request transformation. APIM provides the following benefits:- You scale, monitor, and analyze APIs from one place.
- You govern API security from one place.
- You connect diverse systems, and consumers can discover the APIs.
Managed connectors
The Backbase support team manages Banking OS connectors according to the service level agreements (SLAs). This managed service includes application-level functionality and hosting of the underlying runtime. For more information about core banking connectors, see Core connectors.Managed Hosting
Managed Hosting for Banking OS Connectivity runs on Microsoft Azure. It provides the cloud infrastructure for connectors.Infrastructure management
Banking OS hosts and manages the infrastructure that the integration platform runs on. This includes servers, networking, storage, and related components.High availability and disaster recovery
Managed Hosting keeps the Banking OS Connectivity environment available, and it provides disaster recovery, as follows:Availability design
- Three geographically redundant availability zones
- An active-active-active deployment that continues to serve traffic when two availability zones are unavailable
- A disaster recovery region for the loss of the primary region
Geographic deployment locations
- Primary deployment: A full Backbase reference deployment in one region, with high availability across multiple data centers
- Disaster recovery: A secondary region that continues service if the primary region fails
Scalability
The hosting service scales the Banking OS Connectivity environment as workloads change, so you don’t manage capacity yourself.Security
Banking OS uses access controls, encryption, and vulnerability management for the Banking OS Connectivity environment and its data. Banking OS supports these connectivity methods:- Azure-hosted services through Azure Private Link
- Third-party services on the internet, using mutual TLS (mTLS) or IP address allowlists
- On-premises services, using site-to-site virtual private networks (VPNs)
Authentication
Banking OS uses OAuth 2.0 to authorize inbound and system-to-system API calls.Technical support
Banking OS provides technical support for issues in the hosting environment and infrastructure.Unified APIs and BIAN
The unified API layer gives applications and channels one contract when the underlying systems change. BIAN standards keep those contracts interoperable across the banking industry. The following sections describe the value of unified APIs, the API layer, standardization benefits, the implementation strategy, and coverage. The BIAN sections then describe the standards and the main service domains. For more information about the contracts, see the API playground.The value of unified APIs
One consistent model
Unified APIs give applications and channels one interface and hide the underlying systems.
Modernize at your pace
You modernize one system at a time by aggregating and orchestrating APIs across legacy and new systems.
Decouple systems
You can change the system behind a unified API without changing the applications that call the API.
Independent upgrades
You can improve and upgrade connectors without affecting consuming applications.
API layer architecture
The unified API architecture provides abstraction layers that insulate consumers from backend complexity.System API unification
System API unification hides the system-of-record APIs from digital channels and internal applications. You can migrate one system at a time, run more than one core banking system side by side, and keep one API contract for every consumer. A change in a system of record doesn’t change that contract.Integration path
An application calls the unified API, or a custom API, on APIM. A connector behind that API integrates with the system of record. For more information about API management and managed connectors, see Integration and hosting.API standardization benefits
Development benefits
Standardized APIs provide the following development benefits:- Standardized APIs use familiar patterns and consistent interfaces, so you can apply what you learn about one API to the next.
- Consistent patterns enable component reuse across different implementations, reducing duplication and improving code quality.
- Standardized interfaces reduce the custom integration you build.
Operational benefits
Standardized APIs provide the following operational benefits:- Consistent patterns reduce operational complexity and maintenance overhead by providing predictable behavior across all API endpoints.
- Standardized APIs support consistent monitoring, so you can track performance, identify issues, and compare results with your SLAs.
- Common patterns help support teams identify and resolve issues.
Business benefits
Standardized APIs provide the following business benefits:- Standardized interfaces reduce vendor lock-in and increase choice, so you can swap implementations without disrupting consumers.
- Reusable components and patterns support product delivery and prototyping.
- Shared standards and code reuse reduce the custom work you maintain.
Implementation strategy
Assessment phase
- Analyze existing APIs and systems.
- Identify BIAN service domain mappings.
- Define unification requirements.
Design phase
- Create unified API specifications.
- Map BIAN service domains to business functions.
- Design transformation layers.
Implementation phase
- Implement the unified API layer.
- Deploy services that follow BIAN service domains.
- Test and validate integrations.
Unified API coverage
The API playground lists unified API endpoints and how they map to core banking platforms and third-party integrations.API playground
Browse the OpenAPI specifications for each unified API domain and calendar version (CalVer) in the API explorer.
BIAN: Banking Industry Architecture Network
Backbase is a member of the Banking Industry Architecture Network (BIAN). Backbase uses BIAN service domains so banking systems can interoperate. Backbase products use BIAN standards for the following benefits:Greater interoperability
Standardized interfaces help systems integrate with each other.
Streamlined operations
Consistent patterns reduce operational complexity.
Innovation and adaptability
This standard provides a base for the services that you add.
Connected ecosystem
Systems stay interoperable when you change them.
Industry innovation
Teams collaborate on services that share the standard.
Market adaptation
When market conditions change, you can adapt the services that you offer.
Key BIAN service domain implementations
The following sections describe the BIAN service domains that Banking OS implements, from deposits and loans to party access entitlement:Deposits
Deposits
Deposits give you a combined view of the customer and their accounts. Deposit account management includes the following:
- Account creation and maintenance
- Balance inquiries and statements
- Interest calculations and posting
- Account status management
Loans
Loans
Loans cover lending from application through servicing. Loan management includes the following:
- Loan origination and application processing
- Credit assessment and approval workflows
- Disbursement and repayment processing
- Loan servicing and maintenance
Transactions
Transactions
Transactions cover account history and transaction processing. Transaction management includes the following:
- Real-time transaction processing
- Historical transaction retrieval
- Transaction categorization and enrichment
- Dispute and error resolution
Party lifecycle
Party lifecycle
Party lifecycle covers customer verification during onboarding and the customer record after onboarding. Customer lifecycle management includes the following:
- Identity verification and know your customer (KYC) processes
- Customer onboarding workflows
- Profile maintenance and updates
- Relationship status management
Payments initiation
Payments initiation
Payments initiation covers payment processing across channels. Payment processing includes the following:
- Payment initiation and authorization
- Multi-channel payment support
- Payment status tracking and notifications
- Settlement and reconciliation
Party access entitlement
Party access entitlement
Party access entitlement covers role-based access to channels and services. Access control includes the following:
- User authentication and authorization
- Service entitlement assignment
- Channel access permissions
- Security policy enforcement