Skip to main content

Open Banking for Georgia - API Reference

Version: Georgia v0.8

The Paysera Open Banking API for Georgia provides PSD2-compliant access to account information and payment initiation services through Georgian Open Banking standards based on NextGenPSD2 XS2A Framework.

Base URL​

  • Production: https://open-banking-api.paysera.com/xs2a/georgia/0.8/v1
Looking for EU Standard?

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

Authentication​

All Open Banking API endpoints require MAC (Message Authentication Code) authentication with QWAC and QSealC certificates.

Authorization Header Format:

Authorization: MAC id="CLIENT_ID", ts="TIMESTAMP", nonce="RANDOM_STRING", mac="MAC_HASH", ext="body_hash=BODY_HASH"

Example:

Authorization: MAC id="a9b8c7d6e5f4g3h2", ts="1234567890", nonce="xyz123abc456def", mac="dGhpcyBpcyBhIHJhbmRvbSBtYWMgaGFzaCB2YWx1ZQ==", ext="body_hash=cmFuZG9tQm9keUhhc2hWYWx1ZQ%3D%3D"

For more details, please refer to the Open Banking for Georgia Authentication Documentation.

API Features​

Payment Initiation Services (PIS)​

Initiate single, bulk, and periodic payments with support for domestic and foreign payment products. Includes payment status tracking and cancellation with Strong Customer Authentication.

Account Information Services (AIS)​

Access account lists, details, real-time balances, and transaction history. Multi-currency account support with secure consent-based access.

Create and manage account access consents with SCA support. Multiple authorization approaches available: Redirect, Embedded, and Decoupled.

Strong Customer Authentication (SCA)​

Three SCA approaches supported:

  • Redirect Approach: User redirected to ASPSP for authentication
  • Embedded Approach: Authentication credentials provided directly through API
  • Decoupled Approach: Authentication through separate channel (e.g., mobile app)

Pagination​

Only the transaction list endpoints are paginated. They return up to 50 transactions per page; the page size is fixed and no parameter changes it. When more transactions exist in the requested period, the response carries a _links.next entry at its root pointing at the following page. Follow it until it is no longer present — a response without it is the last page.

Example:

GET /xs2a/georgia/0.8/v1/accounts/{account-id}/transactions?dateFrom=2026-03-01&bookingStatus=both&offset=50

Every other list endpoint returns its full result set in one response.

Rate Limits​

The API implements rate limiting to ensure service stability. If you exceed the rate limit, you will receive a 429 Too Many Requests response.

Contact​

Paysera Support: tech_support@paysera.com Website: https://www.paysera.com