Skip to main content

Open Banking API for Georgia

PSD2-compliant Open Banking API based on NextGenPSD2 XS2A Framework adapted for Georgian market.

Overview​

Open Banking is a system that allows banks and financial institutions to provide secure access to customer financial data through standardized APIs. Third-party providers (TPPs) can access this data with customer consent to build innovative financial services.

Georgian Open Banking Standard is based on the NextGenPSD2 XS2A Framework, adapted for the Georgian financial market:

  • Compliant with National Bank of Georgia regulations
  • Implements Strong Customer Authentication (SCA)
  • Supports Payment Initiation Services (PIS) and Account Information Services (AIS)
  • Enables domestic and foreign payment initiation
  • Single payments only — bulk and periodic payments are not supported

API Version​

Georgia v0.8 (Framework: NextGenPSD2 v1.3.9) - NextGenPSD2 XS2A Framework compliant with National Bank of Georgia requirements.

Base URL: https://open-banking-api.paysera.com/xs2a/georgia/0.8/v1

Specification: Georgian Open Banking Standards

Looking for EU Standard?

For EU-wide operations, visit Open Banking API with Berlin Group v1.3.

TPP Requirements​

To access the production API, you must have:

QWAC Certificate Requirements:

  • Valid QWAC certificate for XS2A from a trusted Open Banking certificate authority recognized in Georgia
  • Certificate must not be suspended or revoked
  • Certificate must be validated via OCSP (Online Certificate Status Protocol)
  • All certificate testing mechanisms must comply with international standards
Access Control

If any QWAC requirements are not met, the connection is terminated and returns HTTP 403 (Access forbidden).

General Settings​

SCA ApproachSupported
Redirect OAuth 2.0 workflow✅
Decoupled workflow❌
Embedded workflow❌

Account Information Service​

ServicesSupported
Support of multiple consents❌
Support of Signing Baskets❌
Support of Card Accounts Endpoints❌
Support display of Account ownerName and ownerNames✅
Support display of Account psuName❌
Owner name always delivered without taking into account the consent scope❌
Support of Trusted Beneficiaries endpoint❌
Support of Multilevel SCA Approach✅
Maximum Frequency Per Day Value Supported on Consent Request4
SCA Validity for a current consent90 days
SCA Validity for a one-off consent1 hour
Consent establishment Timeout1 day
Support of parameter withBalance on APIs❌
Support of parameter combinedServiceIndicator on APIs❌
Supported Account Reference IdentifiersIBAN✅
MaskedPan❌
BBAN❌
Consent scopeDedicated consent (List of accounts)✅
Dedicated consent - Support of ownerName in additionalInformation property✅
Dedicated consent - Support of trustedBeneficiaries in additionalInformation property❌
Bank-offered consent✅
Global consent - availableAccounts = allAccounts✅
Global consent - availableAccountsWithBalance = allAccounts❌
Global consent - allPsd2 = allAccounts✅
Global consent - availableAccounts = allAccountsWithOwnerName❌
Global consent - availableAccountsWithBalance = allAccountsWithOwnerName❌
Global consent - allPsd2 = allAccountsWithOwnerName❌
Supported Access for MultiCurrency Accounts✅
Multicurrency levelAggregation level✅
Sub-account level✅
Aggregation & sub-account level❌
Balance TypeclosingBooked❌
expected❌
openingBooked❌
interimAvailable✅
interimBooked✅
forwardAvailable❌
Supported Transactions Query ParametersbookingStatus = booked✅
bookingStatus = pending✅
bookingStatus = both✅
bookingStatus = all to request all types of transactions (pending, booked and information) at once❌
dateFrom✅
dateTo✅
entryReferenceFrom❌
deltaList❌
Support of Standing orders endpoint (bookingStatus=information)❌
Supported optional transaction information (Standing Orders)debtorName❌
instructionIdentification❌
remittanceInformationUnstructuredArray❌
remittanceInformationStructuredArray❌
creditorAgent❌
debtorAgent❌
balanceAfterTransaction❌

Payment Initiation Service​

ServicesSupported
Support of Signing Baskets❌
Payment initiation timeout15 minutes
Support of PIS without IBAN - Retrieval of debtor accounts with AIS flow✅
Selection of debtor account on CBS pages when payment submission without IBAN❌
Funds Availability on Payment Status Information (implicit FCS over PIS)❌
Support of TPP-Rejection-NoFunds-Preferred Header❌
Support payment status notification (instant payment only)❌
Mandatory Authorisation on Payment Cancellation❌
Supported Access for MultiCurrency Accounts✅
Support display of ownerNames in payment status request❌
Support display of psuName in payment status request and SCA status request❌

Documentation​

Integration Guides​

API Specifications​

Resources​

External Resources​