miaPOS Terminal — User Guide

Document version: W47 · Date: 20.11.2026

Overview

miaPOS is the payment acceptance app on the POS terminal you received from your bank. Through it you accept instant payments via the MIA system: the customer scans a QR code with their bank's app (or receives a payment link or a payment request directly in the app), and the money reaches the merchant's account within seconds.

The app comes pre-installed on the terminal — no additional installation is needed. On first launch, the terminal only needs to be activated (see Chapter 1).

This guide is intended for sellers — the people who work at the terminal every day. If you are using the terminal for the first time, start with Chapter 1. If the terminal is already set up, you can go straight to the chapter you need — each chapter is self-contained.

In short: three things a day

When What you do
Morning Open the working day (the shift).
All day Type in the amount → Generate QR → the customer scans → you see Payment received.
Evening Profile → Close shift (Z) and check the totals.

The rest of the guide explains what to do when something falls outside this routine.

Who does what

Role Responsibility
Acquiring bank Creates the merchant and the terminal, issues the Terminal ID and the seller accounts, activates/deactivates the terminal, configures the tips IBAN.
Merchant (administrator) Receives the enrollment data by email, hands out the accounts to the sellers, sets the terminal operating mode.
Seller (operator) Signs in on the terminal, opens the day, takes payments, makes refunds, closes the day with the Z report.
miaPOS (Finergy) The platform, technical support for the app, updates.

A terminal is not created from the app — a new terminal appears only through the bank. Hence the general rule: issues with money, passwords and activation are resolved with the bank, while strange app behaviour goes to miaPOS support (see Chapter 10).

How the app is organized

The app has three main sections, available from the navigation bar at the bottom of the screen:

the main Terminal screen with the day open — the QR/Link/RTP tabs, an amount entered, the numeric keypad and the bottom navigation bar with the three sections.

Image: img/introducere/01-ecran-terminal.png — large screenshot (full screen). the main Terminal screen with the day open — the QR/Link/RTP tabs, an amount entered, the numeric keypad and the bottom navigation bar with the three sections.

Basic concepts

Term What it means
Working day (shift) The period during which the terminal can take payments. It is opened at the start of the day and closed with a Z report.
Payment channel How the payment reaches the customer: QR (scanning), Link (payment link) or RTP (payment request sent to a phone number or IBAN).
QR code type Dynamic, Static or Hybrid — selected in QR settings; it changes how the terminal works (see Chapters 3 and 9).
Payer type (PF / PJ) The customer pays as an individual or as a company — see Chapter 6.
Tip An optional amount the customer can add to the payment, if the option is enabled for the terminal.
Z report / X report The day-closing report (final) / the intermediate report for the current day.

App language

The app is available in Romanian, Russian and English. The language is changed from Profile → Language and applies immediately (see Chapter 9). This guide uses the names from the English interface.

Setting up and activating the app

At first launch, the terminal must be linked to your company and activated. You need two pieces of information: the company IDNO (from the registration certificate) and the Terminal ID — the unique device code received by email at enrollment.

Activating the terminal

On the start screen, under the prompt Enter data about your terminal:

the activation screen with the "IDNO company" field filled in, the hint "Found on the registration certificate", the "Next" button at the bottom.

Image: img/configurarea/01-onboarding-idno.png — large screenshot (full screen). the activation screen with the "IDNO company" field filled in, the hint "Found on the registration certificate", the "Next" button at the bottom. the same screen with the second field, "Terminal ID", expanded, and the hint "Unique device code · received by email".

Image: img/configurarea/02-onboarding-terminal-id.png — large screenshot (full screen). the same screen with the second field, "Terminal ID", expanded, and the hint "Unique device code · received by email". If you tap Next without filling in a field, it turns red and the message This field is required appears — you cannot continue with the IDNO (or the Terminal ID) empty.

the "IDNO company" field empty, with a red border, and the message "This field is required" below it, after tapping "Next".

Image: img/configurarea/10-camp-obligatoriu.png — small screenshot (crop). the "IDNO company" field empty, with a red border, and the message "This field is required" below it, after tapping "Next". If the data is filled in but activation still cannot continue, the app shows one of the following messages (as a short notification — toast):

Situation Message shown
The entered data does not match Invalid credentials for terminal binding were specified. Please make sure you have entered the correct Terminal ID and IDNO and try again.
The terminal is not found in the system The specified terminal was not found in the system. Check that the information you entered is correct or contact your administrator for support.
The terminal type is not compatible The selected terminal type is not supported in the MiaPOS app
The terminal is inactive Your terminal is currently inactive. Please contact support to activate your terminal and try again.

In all these cases you can correct the data and retry the activation. On the same screen you will also find the Need help? block with the support phone number and email (one tap starts the call or opens the email app; the working hours — Mon–Fri, 8:00 AM – 8:00 PM — are shown under the phone) and the language switcher.

Entering the OTP code

For standard activation, the system sends a one-time password (OTP) by SMS to the phone number of the merchant's administrator. The OTP confirmation screen opens.

the "OTP confirmation" screen with the 6 empty boxes and the text "Enter the OTP code sent to" with the masked number.

Image: img/configurarea/03-otp.png — large screenshot (full screen). the "OTP confirmation" screen with the 6 empty boxes and the text "Enter the OTP code sent to" with the masked number.

the "OTP confirmation" screen with the 6 red, empty boxes, the red message "Entered wrong OTP. (Attempts left: 2)" and the timer "You can resend after 01:00".

Image: img/configurarea/07-otp-gresit.png — large screenshot (full screen). the "OTP confirmation" screen with the 6 red, empty boxes, the red message "Entered wrong OTP. (Attempts left: 2)" and the timer "You can resend after 01:00".

Simplified activation

Some terminals can be activated without an OTP code — if the bank has allowed this activation mode for that terminal. In this case, after you enter the data, the system checks the activation type automatically and continues on its own: no code is requested, and the activation confirmation appears directly on the screen. If the terminal requires standard activation, the app asks for the OTP code as usual.

Completing the activation

Once the activation is confirmed, the POS successfully activated screen appears, with the name of the point of sale, the IDNO and the company logo — the point of sale is ready to accept payments.

the screen with the green checkmark "POS successfully activated", the merchant card with the point of sale name and IDNO, the "Continue" button.

Image: img/configurarea/04-pos-activat.png — large screenshot (full screen). the screen with the green checkmark "POS successfully activated", the merchant card with the point of sale name and IDNO, the "Continue" button. Tap Continue to move on to signing in. The app remembers the bank and the terminal — activation is not requested again on later launches.

Signing in to your account

On the sign-in screen, above the form, you can see the name of the point of sale and the terminal number. Enter the Username and Password — the seller credentials set up by the merchant's administrator — and tap Sign in.

the sign-in form with the "Username" and "Password" fields, the badge with the point of sale and "Terminal #…" above it, the "Sign in" button; below it — "Forgot your login details? Send enrollment data to email" and "Forgot your password? Contact the bank — Support"; further down, next to the logos — "Use another terminal" and "Something not working right? Reset the app".

Image: img/configurarea/05-login.png — large screenshot (full screen). the sign-in form with the "Username" and "Password" fields, the badge with the point of sale and "Terminal #…" above it, the "Sign in" button; below it — "Forgot your login details? Send enrollment data to email" and "Forgot your password? Contact the bank — Support"; further down, next to the logos — "Use another terminal" and "Something not working right? Reset the app".

Login attempt limits

When you sign in, the app tracks failed attempts:

the sign-in form with the "Username" and "Password" fields with a red border and the red badge "Incorrect username or password. Attempts left: 2.".

Image: img/configurarea/08-login-gresit.png — large screenshot (full screen). the sign-in form with the "Username" and "Password" fields with a red border and the red badge "Incorrect username or password. Attempts left: 2.".

the same form, with the red badge "Maximum number of login attempts exceeded. Please try again after 15:30.".

Image: img/configurarea/09-login-blocat.png — large screenshot (full screen). the same form, with the red badge "Maximum number of login attempts exceeded. Please try again after 15:30.".

Automatic login

Some terminals work in "always ready" mode: at startup, the app signs in by itself (Logging in automatically... appears briefly on the screen), without a username or password. On these terminals there is no logout button, and the working day opens automatically. If the automatic login fails, the app shows the regular sign-in form.

On an "always ready" terminal, the Link tab on the Terminal screen is hidden — a terminal like this is a fixed kiosk with no apps to share a link through. The QR and RTP channels work as usual.

No account?

If your company is not yet enrolled in miaPOS — or you get stuck on the sign-in screen without your data handy — tap the Send enrollment data to email link on the activation screen (or Forgot your login details? on the sign-in screen, above — same window). Fill in the company IDNO (13 digits) and the email address; the window tells you that, if you agree, your onboarding data will be sent to the specified email address. Tap OK — the enrollment data will be sent to the address provided, and the bank will contact you.

The email you enter must belong to the company's registered administrator — it is not just any address you'd like the data sent to. If it does not match, the app shows No administrator found with this data. Check the IDNO and email and try again. — check both fields and retry.

the "Send enrollment data to email" window with the IDNO and Email fields, the "Back" / "OK" buttons.

Image: img/configurarea/06-enrolare-email.png — small screenshot (crop). the "Send enrollment data to email" window with the IDNO and Email fields, the "Back" / "OK" buttons.

Main screens and opening the day

After a successful sign-in, you are taken to the terminal screen. At the bottom of the screen are the Terminal, Transactions and Profile tabs — the current tab is highlighted.

the Terminal screen with the bottom navigation bar visible and the Terminal tab highlighted.

Image: img/ecrane-principale/01-taburi-navigare.png — large screenshot (full screen). the Terminal screen with the bottom navigation bar visible and the Terminal tab highlighted.

Opening the day

The terminal takes payments only within an open working day. If the day is not open, the Terminal screen shows The day is closed with the text To get started, open the day.

the Terminal screen with the day closed — the moon icon, "The day is closed", the "Open the day" button.

Image: img/ecrane-principale/02-ziua-inchisa.png — large screenshot (full screen). the Terminal screen with the day closed — the moon icon, "The day is closed", the "Open the day" button.

the open-day confirmation window with the Back and Confirm buttons.

Image: img/ecrane-principale/04-deschide-ziua.png — small screenshot (crop). the open-day confirmation window with the Back and Confirm buttons. Under the same conditions, the open-day button also appears on the Transactions screen, and in Profile — the Open button on the shift card. If another user has already opened a day on this terminal, the app tells you who opened it: the current day must be closed before a new one can be opened. On terminals with automatic login, the day opens by itself when the app starts.

Closing the day (the Z report) is done from Profile — see Chapter 9.

The Terminal screen

At the top of the screen you can see the terminal number (id) and the name of the point of sale — useful when there are several terminals at the location. The centre of the header always shows the configured QR code type (Static QR / Dynamic QR / Hybrid QR — Chapter 9), and on the right — the SCAN&PAY button (see below). While the terminal has an active QR code, a button with a QR icon and a green dot appears next to SCAN&PAY — it reopens the active code's screen (Chapter 3). Underneath — the payment channel tabs, the amount field and the numeric keypad.

Payment channels — above the amount there are three tabs:

Each tab keeps the amount you entered — if you switch from QR to Link and back, the amount is not lost.

The PF / PJ switch — to the right of the tabs is the payer type switch: PF (Individual) or PJ (Legal entity). Choose PJ when a company is paying — the full details and rules are in Chapter 6.

Entering the amount — under the Enter amount prompt, the digits appear large, with a blinking cursor: you can tap between digits to move the cursor, and the cross on the right clears the whole amount. The keypad has digits, a decimal point and a delete key; the big button at the bottom right is the main action — Generate QR, Send link or Send RTP, depending on the selected tab.

the Terminal screen with an amount entered (e.g. 125.50), the cursor between digits, the dark numeric keypad and the "Generate QR" button.

Image: img/ecrane-principale/03-introdu-suma.png — large screenshot (full screen). the Terminal screen with an amount entered (e.g. 125.50), the cursor between digits, the dark numeric keypad and the "Generate QR" button.

Scan & Pay — paying a supplier (feature coming soon)

The SCAN&PAY button in the Terminal screen's header is reserved for a B2B payment flow to a supplier: scanning the supplier's QR code, verifying the bank-validated payment details, and sending the payment document for execution — unlike a regular sale, this would not be an instant payment, but a document that goes to signatures I and II in the merchant's online banking.

In the current version of the app, the button is inactive — the feature cannot be used yet.

Generating the payment QR code

How the QR payment is formed depends on the QR code type selected in QR settings (see Chapter 9): dynamic, static or hybrid. After opening the working day, enter the amount (if the QR type requires one) and tap Generate QR — the message Generating QR code... appears briefly, and then the QR code fills the screen.

the QR code screen — "Amount payable" with the amount, the QR code, the text "Pay via MIA with your bank app", the buttons at the bottom.

Image: img/generarea-qr/01-ecran-qr.png — large screenshot (full screen). the QR code screen — "Amount payable" with the amount, the QR code, the text "Pay via MIA with your bank app", the buttons at the bottom. On the QR code screen you have:

the "Share QR-code" window — the "Copy link" and "Download QR-code" buttons.

Image: img/generarea-qr/06-partajare.png — small screenshot (crop). the "Share QR-code" window — the "Copy link" and "Download QR-code" buttons. A dynamic QR code can be cancelled right from the QR screen: the Cancel button (at the bottom) asks for confirmation (Are you sure you want to cancel this QR code?) and cancels the code — for example, when you entered the wrong amount; then generate a new code with the correct amount. For static and hybrid codes the bottom button is Back and it only hides the screen — the code stays active until it's paid or expires (Time of action, below).

the dynamic-QR cancellation confirmation window — "Confirm the cancellation", the Back / Confirm buttons.

Image: img/generarea-qr/05-anulare-dinamic.png — small screenshot (crop). the dynamic-QR cancellation confirmation window — "Confirm the cancellation", the Back / Confirm buttons. The lifetime of the QR code is governed by the Time of action setting (Chapter 9). Once it expires, the code can no longer be paid.

The dynamic QR code

The static QR code

Amount type How it works
Fixed amount Enter the amount, then Generate QR; the amount can be changed later with Edit amount.
Controlled amount Enter the From / To range; the customer chooses an amount within this range. The minimum amount must be less than the maximum.
Not specified amount No keypad — the customer enters the amount when paying. The screen shows Static QR and the explanation, with the Generate QR button at the bottom.

the Terminal screen on a static QR with a not specified amount — the illustration, "Static QR", the explanation "The customer enters the amount when paying — just generate the QR." and the "Generate QR" button.

Image: img/generarea-qr/02-static-nespecificat.png — large screenshot (full screen). the Terminal screen on a static QR with a not specified amount — the illustration, "Static QR", the explanation "The customer enters the amount when paying — just generate the QR." and the "Generate QR" button. the "From" / "To" fields filled in, on the controlled amount entry screen.

Image: img/generarea-qr/03-suma-controlata.png — small screenshot (crop). the "From" / "To" fields filled in, on the controlled amount entry screen.

The hybrid QR code

Tips

If the tips option is enabled for the terminal (QR settings → Enable tips, dynamic QR only), on the QR code screen the customer sees the purchase amount and the row of buttons None · +5% · +10% · +15%.

the QR screen with tips enabled — the "Purchase amount" and "Tips" rows, the None / +5% / +10% / +15% chips.

Image: img/generarea-qr/04-qr-bacsis.png — large screenshot (full screen). the QR screen with tips enabled — the "Purchase amount" and "Tips" rows, the None / +5% / +10% / +15% chips. The customer picks the percentage they want before scanning — the terminal automatically regenerates the QR code with the total amount (purchase + tip). Rules to remember:

In the transaction details and in the reports, the tip appears on a separate line: Purchase amount and Tips.

Paying with the QR code

Once the QR code is displayed, turn the terminal towards the customer. The customer opens their bank's app, scans the code and confirms the payment via MIA. The terminal checks the payment status by itself every few seconds — you do not need to tap anything.

A delay of up to five seconds between the customer's confirmation and the green screen is normal. If the customer says they have paid but the screen has not changed, wait a few seconds, then check the transaction list (Chapter 7) — a confirmed payment appears there.

Successful payment

When the payment is confirmed, the green Payment received screen appears: the amount received, the time and date, the transaction number. For legal-entity payers, the payer's name and IDNO are shown as well.

the green "Payment received" screen with the amount, the "Paid · #id · time · date" row and the "Receipt" / "OK" buttons.

Image: img/plata-qr/01-plata-primita.png — large screenshot (full screen). the green "Payment received" screen with the amount, the "Paid · #id · time · date" row and the "Receipt" / "OK" buttons. At the bottom there are two buttons:

Payment errors

If the payment did not complete, the Payment error screen appears, with the red icon, the amount and a description of the situation. The two descriptions you see most often:

the "Payment error" screen with the "QR code expired" description — the red icon, the amount and the "OK" button.

Image: img/plata-qr/02-eroare.png — large screenshot (full screen). the "Payment error" screen with the "QR code expired" description — the red icon, the amount and the "OK" button. the same "Payment error" screen, this time with the description "Unfortunately, the payment did not go through. The QR code has been cancelled." and the "OK (…)" button with a timer at the bottom.

Image: img/plata-qr/03-qr-anulat.png — large screenshot (full screen). the same "Payment error" screen, this time with the description "Unfortunately, the payment did not go through. The QR code has been cancelled." and the "OK (…)" button with a timer at the bottom. In both cases the QR code is consumed — for a new payment, enter the amount and generate a new code. The OK button has a timer: when the countdown runs out, the screen closes by itself and returns to the keypad. If the bank declines the payment for another reason, the text sent by the bank appears on the same screen instead of the two above — proceed the same way: tap OK and, if needed, generate a new code.

Error when generating the QR code

Sometimes the code is not even created — the bank or the system responds with an error during generation. In this case the Error when generating QR code screen appears with the text Something went wrong. Try again or go back to the terminal.

the "Error when generating QR code" screen — the red icon, the text "Something went wrong. Try again or go back to the terminal.", the "Retry" button and, below it, "Back".

Image: img/plata-qr/05-generare-esuata.png — large screenshot (full screen). the "Error when generating QR code" screen — the red icon, the text "Something went wrong. Try again or go back to the terminal.", the "Retry" button and, below it, "Back".

The terminal has no connection

While the QR code is on the screen, the app checks the payment status every few seconds. If these checks do not reach the server (internet down, Wi-Fi lost), the app does not declare the payment failed — losing the connection at the terminal says nothing about the customer's payment, which goes through their bank's app. The code stays scannable, and the app resumes the checks automatically when the connection returns; a payment confirmed in the meantime then appears normally. On terminals without a connection you will also see a short "no connection" notification (toast). If you are left without internet for a longer time, restore the connection and then check the transaction list (Chapter 7) to confirm whether the payment went through.

Payment link and the RTP request

Besides the QR code, the terminal can take payments remotely: through a payment link sent to the customer or through a payment request (RTP) delivered straight into the customer's banking app. Both start from the Terminal screen, on the Link and RTP tabs.

Use the Link channel when the customer is not next to the terminal — for example, for phone orders. On terminals with automatic login ("always ready", Chapter 1), the Link tab is hidden — use RTP for remote payments instead.

the payment link screen — the amount, the card with the QR, the shortened link, the "Description (optional)" field, the three "Copy" / "Share" / "Save QR" buttons, the "Close" button at the bottom.

Image: img/link-rtp/01-link-creat.png — large screenshot (full screen). the payment link screen — the amount, the card with the QR, the shortened link, the "Description (optional)" field, the three "Copy" / "Share" / "Save QR" buttons, the "Close" button at the bottom.

the "Description (optional)" field with text typed in and the check-mark button active — before applying.

Image: img/link-rtp/03-link-descriere.png — small screenshot (crop). the "Description (optional)" field with text typed in and the check-mark button active — before applying.

You can always find the links you have sent and their status in Transactions → the Requests tab (Chapter 7).

The RTP request

RTP (Request to Pay) sends the payment request straight into the customer's banking app, using their phone number or IBAN.

the "RTP request" screen — the amount to pay, the "Client phone or IBAN" field with a number typed in with no mask (no automatic +373 prefix), the info panel, the "Send request" button.

Image: img/link-rtp/02-rtp-formular.png — large screenshot (full screen). the "RTP request" screen — the amount to pay, the "Client phone or IBAN" field with a number typed in with no mask (no automatic +373 prefix), the info panel, the "Send request" button. the recipient field with a red border and the error message with both examples, after tapping "Send request" with an incomplete number.

Image: img/link-rtp/04-rtp-eroare-validare.png — small screenshot (crop). the recipient field with a red border and the error message with both examples, after tapping "Send request" with an incomplete number. Empty field. If you tap Send request without entering anything, the app does not send the request: the field turns red with the same message Invalid phone number (e.g. 079123456 or +37379123456). In other words, a recipient is mandatory — there is no "numberless" RTP request. Enter the customer's phone (or IBAN) and send again. The same happens with an incomplete or wrongly formatted value: validation runs when you tap the button, not while you type, which is why the message appears only after tapping.

the "Client phone or IBAN" field empty, with a red border, and the message "Invalid phone number (e.g. 079123456 or +37379123456)" below it, after tapping "Send request" without entering anything.

Image: img/link-rtp/05-rtp-camp-gol.png — small screenshot (crop). the "Client phone or IBAN" field empty, with a red border, and the message "Invalid phone number (e.g. 079123456 or +37379123456)" below it, after tapping "Send request" without entering anything. Another case: if the number is valid in format but the customer has no account in the MIA system, the message is different — This number is not registered in the MIA payment system. Check the number with the customer or ask them to use another channel (payment link, QR).

Individual (PF) or legal entity (PJ) payer

The PF / PJ switch to the right of the tabs on the Terminal screen tells the app who you are expecting: an individual (the default) or a company. Choosing correctly starts the payment on the right flow (the customer's bank business app when a company pays) and marks the operation in your list. The money side does not depend directly on this switch: the payment type (TTC) is set by the payer's bank according to who actually pays, and the TTC decides both the tariff and which side the bank charges the fee to — on a PF payment the fee is withheld from the amount the merchant receives, on a PJ payment it is charged to the payer's account.

the Terminal screen on a dynamic QR with the PJ switch selected, the rest of the screen as usual.

Image: img/pf-pj/01-comutator-pj.png — large screenshot (full screen). the Terminal screen on a dynamic QR with the PJ switch selected, the rest of the screen as usual.

How the switch works

Aspect Behaviour
When it is active On the QR channel — only for the dynamic QR code type — and on the RTP channel, regardless of what's already typed into the recipient field.
When it is locked On Link and static/hybrid QR the switch stays visible but inactive; when tapped, the app explains: Available only for a dynamic QR or RTP.
What it changes Opens the B2B flow in the customer's banking app (asks them to confirm the payment from the business app) and marks the operation in your list with the company name and the payer's IDNO. On RTP, choosing PJ also restricts the recipient field to IBAN — see Chapter 5.
Reset Moving to Link, or changing the QR code to a static/hybrid type, returns the selection to PF. Switching between dynamic QR and RTP keeps a selected PJ — it only doesn't "travel" to Link or to a static/hybrid QR.

the "RTP request" screen with the PJ switch selected and the field label reading "Client IBAN" (not "Client phone or IBAN").

Image: img/pf-pj/02-rtp-pj-iban.png — small screenshot (crop). the "RTP request" screen with the PJ switch selected and the field label reading "Client IBAN" (not "Client phone or IBAN").

What you see on a PJ payment

Practical recommendations

The transactions screen and refunds

The Transactions tab opens the screen with the list of operations for the current working day, in reverse chronological order, plus the Requests tab — the payment links and requests you have sent. If the day is closed, the screen shows The day is closed with the Open the day button instead of the list.

The transaction list

the transaction list with the "Shift: +… MDL" bar, the filter chips (All / QR / Link / RTP / Refunds, PF / PJ), the printer and "?" buttons on the tab bar, and a few rows with amounts and statuses.

Image: img/tranzactii/01-lista.png — large screenshot (full screen). the transaction list with the "Shift: +… MDL" bar, the filter chips (All / QR / Link / RTP / Refunds, PF / PJ), the printer and "?" buttons on the tab bar, and a few rows with amounts and statuses.

By default the list shows only the current shift. If you turn on All transactions in Profile → QR settings (Chapter 9), the list expands to every one of your shifts, grouped: each shift opens with a header row showing its time frame and total — Shift open for the current one, or Shift of and the date for closed ones. Closed shifts have a printer button next to the total — it downloads that specific shift's Z report (Chapter 8); the open shift has no final Z report yet, only the X report from the tab bar (above).

the "How do customers pay?" window opened from the "?" button — three short lines about QR, Link and RTP.

Image: img/tranzactii/06-info-canale.png — small screenshot (crop). the "How do customers pay?" window opened from the "?" button — three short lines about QR, Link and RTP. Transaction statuses:

Status What it means
Paid Successful payment.
Partial Refunded Part of the amount has been returned to the customer.
Full Refunded The whole amount has been returned to the customer.

The Requests tab

The Requests tab (next to Transactions, with the counter of active requests) lists the payment links and RTP requests sent from the terminal.

the "Requests" tab with the All / Active / Link / RTP chips and a few rows — a pending link with the copy/share buttons, an expired request.

Image: img/tranzactii/02-cereri.png — large screenshot (full screen). the "Requests" tab with the All / Active / Link / RTP chips and a few rows — a pending link with the copy/share buttons, an expired request.

Transaction details

Tapping a transaction opens the Transaction details screen: the signed amount and the status, then the card with the payment data:

Field What it contains
Date The date and time of the payment.
Payer / Payer IDNO The name and IDNO of the paying company — PJ payments only (Chapter 6).
Channel The payment's collection channel. In the current version this field can always show "Dynamic QR", regardless of the actual channel — if it looks wrong for a Link or RTP payment, check the actual channel with the filter chips in the list (above).
Purchase amount / Tips The breakdown of the amount, when there is a tip.
Transaction ID The transaction number in the system — quote it to support whenever there is an issue with the payment.
RRN, Approval code The technical identifiers of the payment — the bank uses them when investigating disputes.
SWIFT message type / ID, Payer's bank SWIFT code The ISO 20022 payment message data — needed by the bank for reconciliation.
Transaction type code (TTC) The tariff code of the operation — the bank uses it to apply the correct fee (Chapter 6).

You do not need to understand the technical fields — it is enough to know where they are, so you can read them out to the bank over the phone.

the "Transaction details" screen of a successful payment — the green amount with "+", the status pill, the card with the data rows, the "Receipt" and "Return" buttons at the bottom.

Image: img/tranzactii/03-detalii.png — large screenshot (full screen). the "Transaction details" screen of a successful payment — the green amount with "+", the status pill, the card with the data rows, the "Receipt" and "Return" buttons at the bottom. For paid transactions, there are two actions at the bottom:

The arrow in the top left corner returns to the transaction list.

Refunds

A refund returns the money of a paid transaction to the customer — in full or in part. The refund is irreversible and will appear in the Z report of the shift in which you make it (not the shift in which the sale happened); it can be done only while the working day is open.

From Transaction details, tap Return. On the refund screen:

the refund screen — the "Amount" card with the transaction amount, the "Reason" selector, the "Reason description" field, the "Partial refund" switch off, the red "Refund amount" button.

Image: img/tranzactii/04-rambursare.png — large screenshot (full screen). the refund screen — the "Amount" card with the transaction amount, the "Reason" selector, the "Reason description" field, the "Partial refund" switch off, the red "Refund amount" button.

Partial refund: turn on the Partial refund switch and enter the amount in the Partial refund amount field. The amount must be greater than zero and cannot exceed the transaction amount — otherwise the app shows the corresponding error. After a partial refund, the transaction status becomes Partial Refunded.

only the area with the "Partial refund" switch turned on and the "Partial refund amount" field filled in.

Image: img/tranzactii/05-partiala.png — small screenshot (crop). only the area with the "Partial refund" switch turned on and the "Partial refund amount" field filled in. The result: after you tap the button, the request goes off for processing — the Waiting for a refund decision block with a progress bar appears on the screen. Wait on this screen; the check usually takes a few seconds.

the return screen with the yellow "Waiting for a refund decision" card — spinner and progress bar.

Image: img/tranzactii/07-rambursare-asteptare.png — large screenshot (full screen). the return screen with the yellow "Waiting for a refund decision" card — spinner and progress bar.

Printing receipts and reports

The app can print receipts and reports on the terminal's printer (if the device has one) and can save any document as a PDF file.

The print screen

Receipts and reports open in the same preview screen: the document on a dark background, with the actions at the bottom.

the preview screen of a report — the document image, the print/save buttons at the bottom and the short/full report switch.

Image: img/imprimarea/01-print.png — large screenshot (full screen). the preview screen of a report — the document image, the print/save buttons at the bottom and the short/full report switch.

Error generating the document

Before it can be printed or saved, the document must be generated on the server. If generation fails, instead of the preview the Generation error screen appears with the text An error occurred while generating the report. Will you repeat the request?

the "Generation error" screen — the grey warning icon, the text "An error occurred while generating the report. Will you repeat the request?", the "Retry generation?" button and, below it, the "Go back" link.

Image: img/imprimarea/02-eroare-generare.png — large screenshot (full screen). the "Generation error" screen — the grey warning icon, the text "An error occurred while generating the report. Will you repeat the request?", the "Retry generation?" button and, below it, the "Go back" link.

Automatic receipt printing

After a successful payment, the terminal automatically prints the transaction receipt — no extra action from the seller is needed. The feature works on terminals with a printer; the receipt includes the transaction details: the amount, the date and time, the merchant information.

At points of sale where the till software is integrated with miaPOS (for example SmartOne/PAX terminals), the amount may already arrive filled in on the Terminal screen, without you typing it — the till sends the payment request directly to miaPOS. In this case, after payment the app may automatically return to the previous screen or close itself, and control goes back to the till app — this is not an error.

Manual receipt printing

Besides automatic printing, you can open the receipt at any time:

The receipt opens in the preview screen, from which you can print or save it — useful when the customer needs an extra copy.

The X report

The X report shows the current day's totals without closing the day — useful for mid-shift checks, without affecting the shift.

You open it from the Transactions screen: the printer icon button, top right on the tab bar (visible on the Transactions tab). The report opens in the preview screen, with the short/full option, just like the other documents.

The Z report

The Z report is generated when the working day is closed and locks in the shift's totals for good (see Chapter 9 — Closing the day). After closing, the report opens automatically in the preview screen for printing or saving.

A closed shift's Z report can be reopened at any time — the printer button on that shift's header row, in the Transactions list with All transactions turned on (Chapter 7). The open shift has no such button — it has no final Z report yet.

The profile screen

The Profile tab gathers the user and terminal information, working day management, the settings and support.

the Profile screen — the card with the point of sale and the seller, the shift card with "Shift open / since …" and the "Close shift (Z)" button, the QR settings / Language / Change password / Support / Reset the app rows, the red "Log out" button.

Image: img/profil/01-profil.png — large screenshot (full screen). the Profile screen — the card with the point of sale and the seller, the shift card with "Shift open / since …" and the "Close shift (Z)" button, the QR settings / Language / Change password / Support / Reset the app rows, the red "Log out" button.

QR code settings

Profile → QR settings determines how the terminal works on the QR channel. The changes affect payment acceptance — change them only if you know which mode you need (as a rule, the administrator decides this).

the "QR code settings" screen — the Static/Dynamic/Hybrid selector, the amount type, the "Enable tips" card with the toggle, the "Time of action" field, the "Apply" button.

Image: img/profil/02-setari-qr.png — large screenshot (full screen). the "QR code settings" screen — the Static/Dynamic/Hybrid selector, the amount type, the "Enable tips" card with the toggle, the "Time of action" field, the "Apply" button.

The Apply button becomes active only after a change. When you tap it, the app asks for confirmation: New QR code settings will be applied, and the current QR code will be canceled. Are you sure you want to proceed? If the terminal has an active QR code with an amount set, the window also shows the details of the code about to be cancelled (its type, amount type and amount). On a successful save, a green notification appears. If you leave the screen with unapplied changes, the app warns you (Unsaved changes).

the changes-confirmation window — the text about cancelling the current QR code and the table with the active code's details (type, amount type, amount).

Image: img/profil/07-confirmare-setari.png — small screenshot (crop). the changes-confirmation window — the text about cancelling the current QR code and the table with the active code's details (type, amount type, amount). the "Unsaved changes" warning when leaving the screen with unapplied changes.

Image: img/profil/08-modificari-nesalvate.png — small screenshot (crop). the "Unsaved changes" warning when leaving the screen with unapplied changes. If the administrator has forbidden changing the settings from the administration panel, the Apply button is not shown and the options are inactive; in place of the button, this text appears: To change the terminal operation mode, please contact the administrator.

Changing the language

Profile → Language opens the Language settings screen: Română, Русский, English. The language applies immediately, with no saving — tap the language you want and go back with the back arrow.

the "Language settings" screen with the three languages, the active one checked with a turquoise accent.

Image: img/profil/03-limba.png — small screenshot (crop). the "Language settings" screen with the three languages, the active one checked with a turquoise accent.

Changing the password

Profile → Change password opens the password change screen for the signed-in seller.

the "Change password" screen — the Current password / New password / Confirm new password fields, the hint with the requirements, the "Save" button.

Image: img/profil/06-schimbare-parola.png — large screenshot (full screen). the "Change password" screen — the Current password / New password / Confirm new password fields, the hint with the requirements, the "Save" button.

If you have forgotten the current password, it cannot be changed from the app — contact the bank. On terminals with automatic login ("always ready"), the Change password row is not shown.

Contacting support

Profile → Support opens the screen with the support contacts:

the "Support" screen — the bank card with the logo and "your acquiring bank", the Bank phone / Email rows, the "miaPOS support" block with phone and email.

Image: img/profil/04-suport.png — large screenshot (full screen). the "Support" screen — the bank card with the logo and "your acquiring bank", the Bank phone / Email rows, the "miaPOS support" block with phone and email.

The Support screen also holds the User guide row, which opens this guide right on the terminal.

The same contacts are shown on the activation screen too (the Need help? block, where the support phone also shows the working hours — Mon–Fri, 8:00 AM – 8:00 PM), so you can reach them even before signing in. When you call support, have ready: the terminal number (the id in the corner of the screen), the name of the point of sale and, for issues with a payment, the Transaction ID from Transaction details. Who resolves what — see Chapter 10.

Resetting the app

Profile → Reset the app is the last resort when the terminal gets stuck for no clear reason — a local flag left in a bad state, for example. The row is available on any terminal, including "always ready" ones (where Log out is not shown) — see Chapter 10 for the context.

the "Reset the app?" window — the explanatory text, the "Cancel" / "Reset" buttons (red, with the reload icon).

Image: img/profil/09-resetare.png — small screenshot (crop). the "Reset the app?" window — the explanatory text, the "Cancel" / "Reset" buttons (red, with the reload icon). Tapping it asks for confirmation. Nothing about your work is actually lost — the shift, transactions and other data stay on the server — but the terminal has to be activated again, from scratch (Chapter 1) and signed in again. The same window also opens from the sign-in screen, below the form (Chapter 1) — useful if the app got stuck right before signing in, without going through Profile. Use this button only if the app is stuck due to a glitch; for a routine sign-out use Log out (below).

Closing the day — the Z report

Closing is done from Profile → Close shift (Z). The Close the shift? screen opens with the day's totals:

the "Close the shift?" screen — the Opened / Closing / Transactions / Total collected / of which tips rows, the panel about the Z report, the red "Close shift · Report Z" button.

Image: img/profil/05-inchidere.png — large screenshot (full screen). the "Close the shift?" screen — the Opened / Closing / Transactions / Total collected / of which tips rows, the panel about the Z report, the red "Close shift · Report Z" button.

Check the totals against the cash register before confirming. The Z report is irreversible: the current shift closes and the totals are fixed fiscally. Tap Close shift · Report Z to confirm or Cancel to go back. After closing, the app shows The day is successfully closed. and automatically opens the Z report for printing or saving (Chapter 8).

Logging out

Tap Log out and confirm (Are you sure you want to log out?). If the working day is open, logging out first closes the shift — Z report included. After logging out, you return to the sign-in screen.

Important: on the Z report shown when logging out, printing and saving are not available (the app shows You are logged out. To print reports, please log in.). If you need the Z report printed or saved, close the shift from Close shift (Z) (above) before logging out, not the other way around.

On terminals with automatic login ("always ready" mode), the logout button is not shown.

Common issues and support

This chapter gathers the situations that come up most often at the checkout, each with a short solution, and the rules for contacting support.

What to do when something goes wrong

Situation What you do
The customer says they paid, the screen shows nothing Wait a few seconds — the confirmation arrives with a small delay. Then check the transaction list (Chapter 7).
The terminal has no internet ("no connection" appears) The QR code stays scannable — the customer can still pay from their bank's app. Restore the connection; the app resumes the check on its own. Confirm the payment in the transaction list (Chapter 7).
The "Payment error" screen The code expired or was cancelled — no money was taken. Tap OK, then enter the amount and generate a new code (Chapter 4). If the text is from the bank (another decline reason), try again or ask the customer to retry.
The "Error when generating QR code" screen Tap Retry; usually the second attempt succeeds. If it recurs, check the connection and call support (Chapter 4).
The QR code has expired Generate a new one. No money was taken from the customer.
You already have an active QR A previously generated code is still active — reopen it from the link on the keypad or with the green-dot button in the header; it closes on its own once it's paid or expires.
You cannot type the amount The working day is closed — open it (Chapter 2).
Tips cannot be enabled The tips IBAN is not configured for the terminal — contact the bank.
The PF / PJ switch does not respond It works only for the dynamic QR and for RTP (Chapter 6).
Wrong amount, QR code not yet paid For a dynamic code: open the code (the green-dot button in the header), tap Cancel and confirm, then generate a new one with the correct amount (Chapter 3). For static and hybrid codes with an amount: Edit amount, without generating another code.
Wrong amount, the payment came through Refund (Chapter 7).
A link or RTP request sent by mistake They cannot be cancelled — let them expire and send new ones (Chapter 5).
A row in Requests does not open This is the app's current behaviour — the request status is visible in the list, and a confirmed payment appears in the transaction list.
The app asks you to sign in again The session has expired — sign in again; work continues where it left off.
The Terminal deactivated message The terminal was deactivated by the bank — contact the bank.
You forgot your password Contact the bank — the password cannot be reset from the app (changing the password from Profile requires the current password).
The printer does not print Read the message shown — it names the cause: no paper, cover open, Bluetooth turned off, printer busy or overheated. Fix the cause and tap Print again (Chapter 8).
"Generation error" on a report/receipt Tap Retry generation?. If it recurs, check the connection; meanwhile you can save the PDF (Chapter 8).
Wrong OTP code at activation The boxes turn red and clear — enter the correct code again. After too many wrong tries, restart the activation for a new code (Chapter 1).
The OTP code does not arrive / has expired Wait a few seconds (the SMS is delayed). After the timer, tap Send again. On "sending limit exceeded", retry later (Chapter 1).
Sign-in blocked ("after the time…") You got the password wrong too many times — wait until the time shown, then sign in again. A forgotten password is resolved only through the bank (Chapter 1).
A required field left empty (activation/login/RTP) Fill in the field marked red — without it the action does not continue. For RTP, a recipient (phone or IBAN) is mandatory (Chapters 1, 5).
The app behaves strangely (blank screen, stale data), a flag seems stuck Log out and sign in again. If that doesn't help, use Reset the app from Profile or from the sign-in screen (Chapter 9) — it reactivates the terminal from scratch, with nothing lost server-side. If it still doesn't help, call miaPOS support.
The amount appeared on screen by itself, or the app closed itself after payment This point of sale has its till integrated with miaPOS (Chapter 8) — normal behaviour, not an error.

Who to call

The contacts are in Profile → Support (Chapter 9).

Problem Who to contact
Password, blocked or deactivated terminal, money, account details, fees, terminal activation Your acquiring bank — the phone number and email at the top of the Support screen.
The app behaves strangely, a screen does not open, an error you have not seen before miaPOS support — the phone number and email in the miaPOS support block, available around the clock.

When you call, have ready: the terminal number (the id in the corner of the screen) and, for issues with a payment, the transaction number (from Transaction details).

Short rules to remember

Statuses and glossary

A reference chapter: all the statuses the app displays and the terms used in this guide, with their Romanian and Russian equivalents.

Transaction statuses

Status What it means Example
Paid The payment has been received. It can be refunded in full or in part. The customer scanned the QR and confirmed 125.50 MDL — the green "Payment received" screen appears, and in the list the row "#1041 · Paid".
Partial Refunded Part of the amount has been returned to the customer. The rest can still be refunded. Out of 120 MDL you returned 50 — the transaction keeps 70 MDL refundable.
Full Refunded The whole amount has been returned. No further action is possible. You returned all 45 MDL — the row shows as a refund, with no refund button.
Status What it means Example
Pending The request is active — waiting for the customer's payment. You sent a 150 MDL link for a phone order; it stays "Pending" in the Requests tab until the customer pays it.
Expired Time ran out and no payment arrived — applies to RTP requests (a payment link has no expiry). Create a new request if it is still needed. You sent an RTP to a wrong number; once the customer does not confirm, the request moves to "Expired" — send another.
Declined The customer or bank declined the request, or a technical failure occurred during processing — the app shows the same label for both. If it keeps happening, contact support. The customer tapped "Decline" in their bank's app — the RTP request shows "Declined".

QR code statuses

Status What it means
Active The code can be paid.
Paid The code has been consumed (a dynamic QR accepts a single payment).
Cancelled The code was interrupted before payment — for example, automatically, when the tip is changed on the QR screen, or via Cancel. On the payment screen "Payment error" appears with the text "The QR code has been cancelled" (Chapter 4).
Expired The Time of action from the settings has passed — the "Payment error" screen appears with "The QR code has expired"; generate a new code (Chapter 4).

Error screens — where to find them

The chapters with details and screenshots for each error situation:

Screen / message Where Chapter
Payment error (QR expired / cancelled / declined by the bank) after generating the QR, at payment 4 (Paying with the QR code)
Error when generating QR code when tapping "Generate QR" 4
Terminal without connection (QR stays scannable) on the QR screen 4
Invalid number/IBAN, required RTP field on the RTP form 5 (Link and RTP)
Required field, wrong OTP code, wrong/blocked sign-in at activation and sign-in 1 (Setting up and activating)
Generation error (report/receipt) in the preview screen 8 (Printing)

Working day statuses

Status What it means
Day open The terminal takes payments; the totals flow into the day's Z report.
Day closed Payments are blocked until a new day is opened.
Opened by another seller The terminal already has a day opened by another user — it must be closed first.

Glossary RO / RU / EN

RO RU EN
Terminal de plată Платёжный терминал Payment terminal
Ziua de lucru (schimbul) Рабочий день (смена) Working day (shift)
Închide schimbul (Z) Закрыть смену (Z) Close shift (Z)
Raport X Отчёт X X report
Bacșiș Чаевые Tip
Suma cumpărăturii Сумма покупки Purchase amount
Cerere Заявка Request
Link de plată Ссылка на оплату Payment link
Cerere RTP Запрос на оплату (RTP) Request-to-Pay
Rambursare Возврат Refund
Bon de plată Чек Receipt
Plătitor Плательщик Payer
Persoană fizică (PF) Физическое лицо Individual
Persoană juridică (PJ) Юридическое лицо Legal entity
Timp de acțiune Время действия Lifetime
Banca acceptatoare Банк-эквайер Acquiring bank