Skip to main content

Glossary

Technical terms​

qvik EAM (Unified Data Entry Solutions)​

A service built on the Instant Payment System (AFR), enabling QR code, NFC and Deeplink-based payments. These appear under the "qvik" brand name introduced by the MNB.

API documentation: EAM API | AFR 2.0

qvik​

The brand name introduced by the MNB (Hungarian National Bank) for services built on the Instant Payment System (AFR). Technical name: EAM.

Important: qvik = EAM (same technology)

Brand elements: The MNB requires the display of the qvik logo. Details on the MNB website

A declaration of consent provided by the Approver User, pursuant to which the Bank shall treat transfers submitted by the Customer via the API channel and associated with a consent belonging to the Approver, as transfers duly signed by the Approver in accordance with banking requirements.

Transfers submitted through the API channel do not need to be reviewed and approved by the Approver at the time of submission, as this requirement is replaced by a valid consent, which serves as a form of pre-authorized signature.

A single consent may be associated with one Approver and one or more account numbers. The consent is transmitted by the Customer from its own IT system to the Bank's system via an API call through the API channel or by logging into the Raiffeisen Pay Portal from the user interface. The consent created with the signer appears as a request on the Raiffeisen Pay Portal for the pre-designated Approver, while the consent created without the signer appears as a request for every person with approver rights.

The validity of a consent is determined, on the one hand, by the Bank, which verifies the validity of the consent and the account authorization specified therein for each transfer, and, on the other hand, by the Approver, who approves (accepts) on the Raiffeisen Pay Portal the Customer's right to use the consent for signing transfers. This approval may be revoked by the Approver at any time (24/7) through the same interface.

Warning!

A consent is valid for a maximum period of three months. It can be renewed if it has not yet expired. After expiration, a new consent must be created. The Bank does not notify the Customer of consent expirations. It is the Customer's responsibility to ensure the creation of a new consent and consent ID and the acceptance thereof by the Approver

Usage: Only for Payment API

The identification number associated with the consent. The consent ID must be attached to the message in the client-side system submitting the transfer or order. The consent ID determines which consent the bank considers as the signature (approval) of the Approving User. Two consent IDs must be attached to each order.

Statuses:

  • IN_PROGRESS
  • APPROVED
  • DECLINED
  • REVOKED

Raiffeisen Pay Portal (RPP)​

A web interface for performing administrative tasks related to the API.

Available at: https://payportal.raiffeisen.hu

Functions:

  • System administrator management
  • Creating API users
  • Uploading and managing certificates
  • Consent creation, approval, extension, revocation (in case of Payment API)
  • Managing approver persons

Access:

  • System administrator: Direct ID + password + SMS activation code
  • Approver: Direct ID + password + SMS OTP code

Transaction Reference​

The client-provided unique identifier (e.g. order number, invoice number) for a transaction.

Format: Freely chosen

Example: ORDER-12345, INV-2025-001

Usage: Reconciliation, identification

Payment Reference​

The unique identifier created by the backend systems.

Format: Alphanumeric string

Example: TXN-98765

Usage: Status inquiry

API Key​

Authentication key for API calls.

Header name: X-API-KEY Important:

  • Different API keys for test and production environments
  • Test API key does not work in production environment (INVALID_APIKEY error)
  • Must be stored securely (environment variables, secrets manager)

Base URL​

EnvironmentURLAvailability
Testhttps://premium-api-int.raiffeisen.huWeekdays 7:00-20:00
Productionhttps://premium-api.raiffeisen.hu24/7

Endpoint​

The URL of a specific API operation.

Examples:

  • POST /eam/init - QR code generation
  • POST /payment/init - Initiating a transfer
  • POST /payment/consent/create - Creating a consent

Abbreviations​

AbbreviationFull nameMeaning
AFRAzonnali Fizetési RendszerMNB-operated 24/7 instant payment infrastructure. Processed within 5 seconds up to 20M HUF.
EAMEgységes Adatbeviteli MegoldásokQR/NFC/Deeplink-based payment solutions (qvik brand name)
RTPRequest to PayPayment request - electronic payment demand
OFOOnline Fizető OldalEmbeddable payment widget for webshops
RPPRaiffeisen Pay PortalAdministrative portal for managing API users
SEPASingle Euro Payments AreaUnified euro payment zone (EU + EEA + some additional countries)
CSRCertificate Signing RequestCertificate signing request (part of public key infrastructure)
JWTJSON Web TokenAuthentication token format for API calls
KIDKey IDKey identifier in the JWT header
HMACHash-based Message Authentication CodeMessage authentication code (used by OFO)