## [TBC Bank Developer Portal (2026)](/nominees/2026/tbc-bank-portal) ![Screenshot of TBC Bank Developer Portal's Home header](/sites/default/files/styles/nominees_image/public/2026-10/Screenshot%202026-10-30%20at%2017.54.27.png?itok=eIqauCd1) Owner TBC Bank [ Visit the portal ](https://developers.tbcbank.ge/) ## NOMINEE OVERVIEW *Beyond Open Banking: Building an API Ecosystem for Real Business Innovation* The TBC Bank Developer Portal is a unified gateway to Georgia's leading banking API ecosystem, connecting developers, fintechs, merchants, and technology partners with the financial capabilities they need to build innovative digital services. Our ambition goes beyond regulatory compliance. While secure standards-based Open Banking APIs serve as a foundation, TBC’s developer ecosystem extends far beyond mandatory services. It brings together a diverse portfolio of API products spanning digital payments, e-commerce, online financing, exchange rates, digital identity, business software integration, and Open Banking. This approach transforms banking APIs from isolated technical interfaces into practical building blocks for business innovation. TBC's commitment to API innovation has earned international recognition. In 2026, Global Finance named TBC’s Open Banking API services the best in Central and Eastern Europe, highlighting the diversity and simplicity of our offerings, partner adoption, and API usage. Behind this recognition is a growing ecosystem of more than 3,000 partner companies and 3,200 registered developers, supported by over 22 million API operations per month. The Developer Portal brings these capabilities together through a consistent, business-oriented experience. Developers can discover relevant products, navigate standardized documentation, access product-specific technical guidance, explore testing environments, and manage multiple API products through a unified developer account. Our documentation is designed to support the entire integration journey, not merely describe endpoints. Depending on the product, developers can find business context, authentication requirements, API references, testing instructions, environment configurations, and production integration guidance. The portal evolves continuously through coordinated API publishing, proactive developer support, feedback-driven enhancements, and a strategic roadmap backed by leadership. For TBC, the developer portal is more than a documentation site or a regulatory requirement—it is a strategic bridge connecting banking infrastructure with the businesses, developers, and partners building the next generation of financial experiences. ## NOMINATION RATIONALE ### 1) BEST API PRODUCT MICROPORTAL INSIDE A DEVELOPER PORTAL **Why is this category a strong match?** *Bringing Banking into the Business Workflow* Business Integration Services (BIS) is a focused API product within TBC Bank's broader developer ecosystem, designed to connect banking capabilities directly with the accounting, ERP, and business applications companies use every day. Its purpose is straightforward: businesses should be able to work with banking information and authorized financial operations without constantly switching between disconnected systems. BIS addresses this need by enabling business software to retrieve account balances, transaction history, and statements, and to initiate transfers where appropriate permissions are granted. What makes this offering particularly relevant is the connection between the business user's experience and the developer's integration journey. TBC provides two practical paths for adoption. Businesses using supported ready-made accounting software can work with their software providers to enable the relevant API integration. Businesses using custom-built software can access the technical documentation through the TBC Bank Developer Portal and share it with their developers. The integration activation process is fully digital and takes place through TBC Business Internet Bank, where an authorized business user can create an API integration, select the relevant user, assign permissions, and obtain the credentials required for technical implementation. Within the Developer Portal, BIS provides a dedicated documentation experience covering its business capabilities, authentication requirements, API permissions, and test and production environments. This creates a seamless connection between a specific business need, a focused group of related APIs, and the practical steps required to implement the service. BIS illustrates how a banking API product can be presented as a comprehensive business integration solution rather than a collection of unrelated technical endpoints. **In what ways does your portal shine in this category?** Business Integration Services demonstrates how TBC Bank connects a specific commercial use case with the technical resources and access-management processes required to make it work. **1. Designed around a clear business problem** Businesses frequently rely on accounting, ERP, and other software to manage financial operations. BIS allows these systems to connect with relevant banking capabilities, supporting workflows such as retrieving account information, reconciling transactions, and initiating authorized transfers. Instead of requiring developers to start with an abstract API catalog, the offering begins with a recognizable business objective: integrating banking services into existing business software. **2. Two practical paths to integration** The product supports different business technology environments. Companies using supported ready-made accounting solutions can work with their software providers to activate the relevant integration. Companies with custom-built software can use the BIS documentation available through TBC Bank Developer Portal. This distinction makes the offering relevant both to businesses adopting existing software integrations and to developers building tailored solutions. **3. Fully digital integration activation** The BIS production integration activation journey is managed through TBC Business Internet Bank. An authorized business user can: - Create a new API integration. - Select the relevant business banking user. - Choose the required API permissions. - Obtain the Client ID and Client Secret needed for application authentication. The selected permissions are linked to the user's existing banking access rights, connecting technical API access with business-side authorization. This is an important part of the product experience: the business customer manages production integration through a familiar banking environment, while the developer receives the technical information needed to implement it. **4. A coherent group of related API capabilities** BIS brings together services that support a common business workflow, including: - Account balance information. - Account transaction history. - Account statements. - Transfer initiation, subject to the required permissions. These capabilities form a focused product offering rather than an unrelated collection of APIs. **5. Product-specific technical documentation and simplified sandbox access** The BIS documentation explains the available services and their implementation requirements. It includes guidance on OAuth 2.0 Client Credentials authentication, Bearer access tokens, API scopes, and the distinction between account information and transfer-related permissions. BIS provides a straightforward path from testing to production through two distinct access journeys: - **Sandbox access:** Developers can easily obtain sandbox credentials directly through TBC Bank Developer Portal, allowing them to start testing and exploring the available APIs without going through the business banking activation process. - **Production access:** When ready for live integration, authorized business users can activate API access through TBC Business Internet Bank, where they manage integrations, select permissions, and obtain production credentials. This approach enables developers to begin technical integration with minimal friction while ensuring that production access remains aligned with the business customer's authorization and banking permissions. By clearly separating testing and production access, BIS supports a practical developer onboarding experience while maintaining appropriate controls for live banking operations. **6. Business and developer experiences working together** BIS connects two important parts of the integration journey. The developer can independently explore the product documentation, obtain sandbox credentials, and begin testing through TBC Bank Developer Portal. When moving to production, the business user manages activation and access permissions through Business Internet Banking. This separation respects the different responsibilities of business users and developers while supporting a shared integration objective. It also creates a clear progression from technical exploration and testing to business-authorized production integration. **7. A product-focused experience within a wider API ecosystem** BIS is documented within TBC Bank Developer Portal, where developers can discover it alongside other banking capabilities. Its dedicated overview, authentication guidance, simplified sandbox access, and environment-specific instructions provide a focused entry point for developers working on business software integrations. By connecting business purpose, accessible testing, digital activation, access management, and technical documentation, BIS demonstrates how an API product can help turn banking infrastructure into a practical integration capability for businesses. ### 2) BEST UNIFIED OR FEDERATED ENTERPRISE DEVELOPER PORTAL **Why is this category a strong match?** *One Banking Ecosystem. Many Business Domains. One Coherent Developer Experience.* TBC Bank Developer Portal addresses a fundamental challenge faced by large financial institutions: how to make a diverse, technically complex API portfolio accessible through one coherent developer experience. A banking API ecosystem is inherently complex. Different products serve different audiences, operate under different security and authorization requirements, and support distinct business processes. Regulated Open Banking services, digital identity, merchant payments, financing solutions, and corporate banking integrations cannot all be approached in exactly the same way. Yet developers should not have to navigate a fragmented experience simply because the underlying banking capabilities are different. TBC addresses this challenge by bringing its API offerings into a unified developer environment, supported by consistent documentation standards, business-oriented product discovery, and shared developer account management. Crucially, the portal is not limited to APIs required by Open Banking regulations. Alongside Account Information and Payment Initiation Services, it provides access to commercial and business-oriented API products such as TBC E-Commerce, Online Installments, Exchange Rates, TBC ID, Online Mortgage, POS QR, and Business Integration Services. These products enable developers and partners to build solutions that extend beyond regulatory data access — from accepting online payments and enabling digital customer identification to connecting accounting software directly with banking services. The portal follows a centrally coordinated approach to developer experience, while preserving the specific technical requirements and integration journeys of individual products. Its long-term development is supported by established ownership, management commitment, coordinated API publishing, developer support, and feedback-driven improvements. This combination of enterprise complexity, portfolio diversity, consistent documentation, and a growing developer ecosystem makes TBC Bank Developer Portal a strong match for the Best Unified or Federated Enterprise Developer Portal category. Our achievement is not simply bringing multiple APIs together. It is making different banking capabilities easier to understand, discover, and integrate within one connected experience. **In what ways does your portal shine in this category?** *From Regulatory APIs to a Unified Platform for Business Innovation* TBC Bank Developer Portal stands out through its ability to combine a broad banking API portfolio, consistent technical documentation, unified developer account management, and measurable ecosystem adoption. **1. A diverse API ecosystem that goes beyond regulatory requirements** TBC's API strategy extends beyond providing mandatory Open Banking interfaces. The Developer Portal brings together regulatory and commercial API offerings across multiple business domains: - Open Banking services supporting secure, consent-based financial data access and payment initiation. - Online Installments, supporting installment financing through external digital channels. - Online Mortgage, providing mortgage loan calculation capabilities that can be integrated into external digital platforms. - TBC ID, enabling digital authentication and identity verification. - Exchange Rates, providing access to financial information for business applications. - Business Integration Services, connecting accounting and ERP software with banking capabilities. - POS QR, supporting additional digital payment scenarios. This breadth makes the portal relevant to different developer audiences, including fintechs, merchants, software vendors, and corporate technology partners. **2. A unified developer account across multiple API products** Developers can manage multiple API products through a single developer account. This creates continuity across integration journeys and reduces the need to navigate separate developer environments for different banking capabilities. The result is a more coherent experience for partners whose business solutions depend on more than one API product. **3. Consistent documentation with product-specific depth** TBC applies shared documentation standards across its API portfolio. The documentation is organized to help developers understand both the business purpose of an API product and its technical implementation requirements. Depending on the service, developers can access: - Product overviews and business context. - Authentication and authorization guidance. - API references and endpoint descriptions. - Request and response information. - Error handling instructions, including error codes, descriptions, and guidance for identifying and resolving integration issues. - Sandbox and production environment details. - Security and certificate requirements. - Testing and integration instructions. This structure makes different products easier to navigate while respecting their distinct technical requirements. For example, Business Integration Services provides dedicated guidance on OAuth 2.0 Client Credentials, permissions, account information, transfer initiation, and separate testing and production environments. TBC ID documents identity and authentication capabilities, including OpenID Connect and different authentication flows. These examples demonstrate how a common documentation approach can support different integration models without sacrificing clarity. **4. Internationally recognized API innovation** In 2026, Global Finance recognized TBC's Open Banking API services as the best in Central and Eastern Europe. The recognition highlighted the diversity and simplicity of the services, the number of partners using them, and their adoption. Although the award recognizes TBC's Open Banking API capabilities rather than the Developer Portal itself, it provides independent validation of the quality and maturity of an important part of the ecosystem presented through the portal. **5. A growing ecosystem with measurable adoption** TBC's developer ecosystem supports: - More than 3,000 partner companies. - More than 3,200 registered developers. - More than 22 million API operations per month. - Active service integrations increased from 628 in January 2026 to 778 in August 2026 — approximately 24% growth. These indicators demonstrate that the ecosystem is not simply a collection of published interfaces. It supports a substantial and growing network of real integrations. **6. A developer experience supported by people and processes** The portal is supported by a dedicated Open API function that coordinates API publication, documentation, and technical developer support in collaboration with relevant banking product and technology teams. Developer feedback contributes to ongoing improvements, supported by an established roadmap and management commitment. This operating model helps ensure that the portal evolves alongside both developer needs and the bank's expanding API portfolio. **7. Connecting banking capabilities with real business outcomes** The value of a unified developer portal becomes clearest when APIs support practical business needs. A merchant can explore online payment and financing capabilities. A software provider can integrate banking information into accounting applications. A fintech can build services using consent-based financial data. A digital platform can incorporate trusted identity capabilities. These are different products, audiences, and integration models — but they are discoverable through one developer ecosystem. The result is a developer portal that does more than centralize API documentation. It connects diverse banking capabilities with real opportunities for businesses and developers, while maintaining the consistency required to support an enterprise-scale API program. 2026