Back to News & Insights

Georgia · Horizon published 14 Oct 2026 · Source published 19 May 2026 · Reviewed 14 Oct 2026

Georgia modernises RTGS infrastructure, creating a clearer reference

The National Bank of Georgia reported completion of an RTGS and clearing-system modernisation in May 2026, including a transition to ISO 20022 and a technical basis for future payment innovation. The change gives payments, fintech, banking and enterprise-software teams a current reference point for researching local integration and operating models.

Verified facts

  • The National Bank of Georgia reported on 19 May 2026 that it had completed the RTGS and clearing-system upgrade and transitioned the infrastructure to ISO 20022. The announcement identifies a system change, not an individual participant’s onboarding, service availability or technical integration.
  • NBG stated that eligible non-bank payment service providers may participate in the system upon meeting relevant requirements. Eligibility language does not establish that a particular applicant meets registration, technical, operational, capital, risk, compliance, connectivity, security or other requirements.
  • The NBG payment-services framework separately identifies regulated categories, payment-service-user information and strong-customer-authentication requirements. Infrastructure modernisation does not displace the need to determine the correct regulated role, consumer, security, AML/CFT, data and contractual obligations for a product.
  • World Bank material describes Georgia’s broader digital-inclusion and innovation efforts and notes remaining access and capability gaps. Independent context supports a targeted operating hypothesis but cannot validate a payment product, customer need, compliance outcome or investment case.
  • BIS/IOSCO principles provide the international risk, access and operational-resilience frame for financial-market infrastructure. They are not an assessment of Georgia’s upgraded system and do not evidence compliance, participant onboarding, technical connection or commercial readiness for a named firm.

Horizon view

The update supports an ecosystem and technical-integration research track. The decision unit remains a specific regulated service, named legal entity, current NBG classification and authority path, bank or PSP counterparty, documented interface and customer-consent or payment workflow. ISO 20022 adoption gives well-prepared teams a stronger basis for identifying relevant local use cases and accountable operating partners.

Commercial implication and next step

For a payment, fintech, merchant, open-banking, cross-border or data proposition, begin with a controlled service file: legal entity and ownership; exact functionality and regulated-role analysis; named NBG/bank/PSP and documented route; interface/sandbox, security, resilience and incident controls; consent and data map; financial-crime, consumer-disclosure and complaint processes; commercial pricing/liability/settlement model; and a capped proof of technical and business acceptance. Do not represent a connection, authorisation, participation or interoperability outcome before it is evidenced by the relevant authority and counterparties.

What to verify before acting

The sources do not establish licence or registration, technical connectivity, system participation, API access, customer consent, payment initiation, service availability, bank partnership, pricing, settlement, payment, contract or transaction. This is not Georgia payments, banking, financial-services, AML/CFT, data-protection, cybersecurity, consumer-protection, tax, insurance or legal advice.

Related intelligence

Relevant market platforms

Go deeper

Decision dossiers for this market question

Use the dossier library when the signal needs to become a structured country-sector workstream, rather than a standalone news item.