General information

TPP identification policy

QWAC verification

To access the production API, a valid QWAC certificate for XS2A is required. The following conditions must be met:

  • The certificate must be issued by a trusted Open Banking certificate authority recognized in Georgia.
  • The certificate must not be suspended or revoked.
  • The certificate must be validated via OCSP (Online Certificate Status Protocol).
  • All valid certificate testing mechanisms, including OCSP, must comply with international standards and best practices.

If any of the conditions are not met, the connection is terminated, and the TPP receives an HTTP 403 response (Access forbidden).

Market test requirements

To participate in the market test, the TPP must fulfill the following requirements:

  • Obtain a valid certificate from a Georgian certification authority.
  • Have one or more Paysera accounts with sufficient funds.

Getting started

To begin, contact Paysera and provide a description of how you plan to use the API. Include:

  • The specific APIs that you intend to use.
  • Whether they will be used with the Production environment.
Additional information may be requested during the process.

General settings

SCA Approach Supported

Redirect OAuth 2.0 workflow

Decoupled workflow

Embedded workflow

Account Information Service

Services

Supported

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 Request

4

SCA Validity for a current consent

90 days

SCA Validity for a one-off consent

1 hour

Consent establishment Timeout

1 day

Support of parameter withBalance on APIs

Supported Account Reference Identifiers

IBAN
MaskedPan
BBAN
Consent scope Dedicated 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 level Aggregation level
Sub-account level
Aggregation & sub-account level
Balance Type closingBooked
expected
openingBooked
interimAvailable
interimBooked
forwardAvailable
Supported Transactions Query Parameters bookingStatus = 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

Services

Supported

Support of Signing Baskets

Payment initiation timeout

15 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