MIA Merchant Portal — User Guide
Document version: W47 · Date: 20.11.2026
Introduction
What is MIA Merchant Portal
MIA Merchant Portal is the merchant's web admin panel within the miaPOS ecosystem (Finergy Group). Through this portal, the merchant monitors and manages their payment activity: transactions, POS terminals, stores, sellers, and users with portal access.
The portal covers:
- Dashboard — statistics and charts about transactions, for selectable periods.
- Transactions — the list of payments processed across all channels (POS, E-COMM, RTP), with filtering, details, and refunds.
- Online Operations — payment links and payment requests (Request to Pay).
- Disputes — the correspondence and status of disputes between the merchant and their bank.
- Reports — downloadable reports (e.g., the B2B Payments report).
- Administration — stores, terminals, sellers, users with portal access, and the merchant profile.
Access is through a web browser, by signing in with your phone number and a confirmation code (OTP) — see the Authentication chapter. No app installation is required.
Roles and permissions
Each user with portal access has one or more of the following 4 roles, assigned from the Users section (see the Administration chapter); role rights are cumulative. In the interface, roles appear under their technical names: admin, manager, reporter, seller.
- admin — full control over the portal, including user management and the merchant settings.
- manager — day-to-day management: everything except user management and the merchant settings.
- reporter — a read-only role: viewing, exports, and reports, without the right to change anything.
- seller — an operational role for the point of sale: transactions, refunds, payment links, and payment requests.
The role determines which sections of the portal are accessible:
| Section | Admin | Manager | Reporter | Seller |
|---|---|---|---|---|
| Dashboard | ✓ | ✓ | ✓ | — |
| Transactions | ✓ | ✓ | ✓ | ✓ |
| Online Operations (links, RTP) | ✓ | ✓ | ✓ | ✓ |
| Disputes | ✓ | ✓ | ✓ | — |
| Reports | ✓ | ✓ | ✓ | — |
| Administration — stores, terminals, sellers, merchant profile | ✓ | ✓ | ✓ | — |
| Administration — users | ✓ | — | — | — |
| User guide | ✓ | ✓ | ✓ | ✓ |
Within an accessible section, some actions are further restricted by role:
| Action | Admin | Manager | Reporter | Seller |
|---|---|---|---|---|
| Export transactions to CSV and download the tips report | ✓ | ✓ | ✓ | — |
| Refund a transaction | ✓ | ✓ | — | ✓ |
| Create a payment link | ✓ | ✓ | — | ✓ |
| Create or import payment requests (RTP) | ✓ | ✓ | — | ✓ |
| Reply in a dispute and assign it to the bank | ✓ | ✓ | — | — |
| Create and edit stores, assign terminals, manage sellers | ✓ | ✓ | — | — |
| Open a seller's card | ✓ | ✓ | — | — |
| Manage portal users | ✓ | — | — | — |
| Edit the merchant settings | ✓ | — | — | — |
The reporter role sees the same lists and details as admin and manager, but strictly for reading: the create, edit, and delete buttons are hidden, records are viewed in the side panel of each list, and the editing pages are not reachable. The only detail hidden from the reporter is the seller's card — it contains the seller's sign-in credentials, so it stays restricted to admin and manager.
The seller role works only with Transactions and Online Operations. The other sections don't appear in the sidebar menu at all for this role, and the export buttons and reports are hidden. The quick actions for creating a payment link or a payment request stay available right in the sidebar.

Image:
img/introducere/01-meniu-rol-seller.png— small screenshot (crop). the sidebar as the seller role sees it — only Transactions and Online Operations, with the Link and RTP quick actions above them. Global search only looks through the sections available to your role — for example, the seller role searches transactions and payment requests only, and searching portal users is available to administrators only.
If a page outside your rights is opened by a direct link, the portal shows the message "You do not have access to this page" and returns you to the first available section.

Image:
img/introducere/02-panou-doar-citire-reporter.png— large screenshot (full screen). the Stores list as the reporter role sees it — the details open in the side panel in read-only mode, with no New store, Edit, or Delete buttons. Merchant profile: within the Administration → Merchant Profile section, editing the data (logo, tips report email, enabling e-comm support) is available to the admin role only. The other roles see the same information in read-only mode.
Authentication
Signing in to MIA Merchant Portal takes two steps: your phone number, then a confirmation code (OTP) sent via SMS. The portal does not use a password to sign in.
Step 1 — phone number
On the start screen, enter your phone number registered in the portal (the number you were added with as a user — see the Administration chapter, Users section), in the format (+373) 00-000-000.

Image:
img/autentificare/01-ecran-login.png— large screenshot (full screen). the full sign-in screen, empty phone field, inactive (grey) "Sign In" button. The Sign In button stays inactive until the number is filled in. Once a valid number is entered, the button becomes active:

Image:
img/autentificare/02-telefon-completat.png— large screenshot (full screen). the same screen, with the phone number filled in and the "Sign In" button active (solid color). If the entered number is not registered in the system, the portal displays an error message — the merchant for that number was not found — and stays on this screen.
Step 2 — confirmation code (OTP)
After pressing the Sign In button, the portal sends a 6-digit code via SMS to the entered number and opens the confirmation screen.

Image:
img/autentificare/03-ecran-otp.png— large screenshot (full screen). the OTP confirmation screen, the 6 empty fields, the masked phone number shown above. Enter the code you received via SMS. The Confirm button becomes active once all 6 digits are filled in:

Image:
img/autentificare/04-otp-completat.png— large screenshot (full screen). the 6 fields filled in, the "Confirm" button active. If you didn't receive the code:
- Press Send again, below the code fields, to request a new code — the option becomes available once the displayed timer expires ("Resend code in…"). When resending, the digits already entered are cleared and the timer starts again.
- Press Call us, below the confirmation box, to contact support by phone.
If you enter an incorrect code, the portal displays an error message, clears the 6 fields, and lets you try again. The fields accept digits only.
The Back to sign in button returns to step 1 — use it if you entered the wrong phone number.
For security reasons, the number of code resends and entry attempts is limited. If the limit is exceeded, the portal displays a corresponding message and returns to the phone number step — try again later.
Successful sign-in
Pressing Confirm with a valid code signs you in and takes you directly to the Transactions section of the portal.

Image:
img/autentificare/05-conectat-cu-succes.png— large screenshot (full screen). the portal right after signing in, on the Transactions page (sidebar + header + start of the table, not necessarily the whole table).
Portal language
The display language is chosen from the menu in the top-right corner, available even from the sign-in screen. The portal is available in 5 languages: Romanian, Russian, English, German, and French.

Image:
img/autentificare/06-selector-limba.png— small screenshot (crop). just the top-right area, with the language menu open and all 5 options visible — not the entire screen. The selected language is kept after signing in too — it can be changed at any time from the account settings (see the Platform Features chapter).
Dashboard
The Dashboard page provides an overview of payment activity: volume, number of transactions, commissions, channel distribution, and recent transactions. It's visible to the admin, manager, and reporter roles — the seller role does not have access to this section.

Image:
img/tablou-de-bord/01-vedere-generala.png— large screenshot (full screen). the full page, with the 3 KPI cards, the volume chart, and the recent activity list.
Displayed period
At the top of the page, choose the period for which all the data is calculated. 4 quick presets are available — Last 7 days, Last 14 days, Last 30 days, Last 90 days — or a custom range from the calendar, confirmed with the Confirm button. When the page opens, the Last 14 days period is selected by default.

Image:
img/tablou-de-bord/02-selector-perioada.png— small screenshot (crop). the period selection menu open, with the 4 presets and the custom range option. The refresh button (the circular-arrows icon) manually reloads the data for the current period.
The Export button is disabled — the export feature on the Dashboard is not yet available.
Key indicators (KPI)
Three cards display the main indicators for the selected period, each with the change compared to the previous period (an interval of the same length, immediately before it; if it contains no data, the change is shown as "—"):
- Total volume — the sum of all transactions.
- Transactions — the total number of transactions.
- Commissions — the sum of commissions withheld.

Image:
img/tablou-de-bord/03-carduri-kpi.png— large screenshot (full screen). the 3 KPI cards (Total volume, Transactions, Commissions), each with its value and the change vs. the previous period.
Volume chart
The "Volume over time" card shows payments and returns by day, for the selected period: payments rise above the zero line, returns drop below it (the Payments / Returns legend is shown next to the title). Hovering over a day shows a tooltip with that day's details: the number of transactions, the payment amount, and the number and amount of returns.

Image:
img/tablou-de-bord/04-grafic-volum.png— large screenshot (full screen). the volume chart with bars going up/down (payments/returns), the Payments/Returns legend, and the tooltip with a day's details on hover.
Channel distribution
A radial chart shows how the number of transactions is split across payment channels: POS, E-COMM, and RTP. The total number is displayed in the center of the chart.

Image:
img/tablou-de-bord/05-distributie-canale.png— small screenshot (crop). the radial chart with the channel distribution and the legend with percentages.
Top terminals
The top 4 terminals by number of transactions in the selected period. The All button opens the Terminals section. If there is no data, the message "No terminals available" is displayed.

Image:
img/tablou-de-bord/06-top-terminale.png— small screenshot (crop). the Top terminals list with a few rows.
Recent activity
The last 7 transactions from the selected period, shown in a list: the channel, the store, the TX ID, the date, the amount, and the status. The "See all transactions" button leads directly to the Transactions section.
Clicking a transaction in the list opens its details panel. For a refund, the Refund button in the panel opens that transaction in the Transactions section, where the operation is completed.

Image:
img/tablou-de-bord/07-activitate-recenta.png— large screenshot (full screen). the recent activity list, with a transaction selected and the details panel open over the content.
Transactions
The Transactions section shows all payments processed by the merchant, across all payment channels: POS, E-COMM, and RTP. The section is visible to all roles — admin, manager, reporter, and seller. Two actions inside it depend on the role: refunds are available to admin, manager, and seller, while the CSV export and the tips report are available to admin, manager, and reporter.

Image:
img/tranzactii/01-lista-tranzactii.png— large screenshot (full screen). the full page with the transactions table, the search bar, the period filter, and the Channel / Status filter rows.
Viewing and filtering
The table shows one row per transaction, with the following columns:
- ID — the transaction identifier (e.g., TX-1024).
- Channel — the payment channel: POS, E-COMM, or RTP (older transactions may also show LINK or BOT).
- Date — the date and time of the transaction.
- Store — the store where the payment was made.
- Description — the payment description.
- Amount — the total transaction amount, with the currency.
- Payment amount — the base amount, without the tip.
- Tip — the tip, if any.
- Commission — the commission withheld.
- Status — the transaction status, shown as a label: Paid, Refunded, or Partial.
The ID, Date, Store, Amount, and Commission columns can be sorted by clicking the column header.
Above the table are the search and filter tools:
- Search bar — searches by ID, description, or amount. Results update automatically shortly after you type.
- Period filter — the button with the date range opens a menu with 5 presets (Today, Yesterday, Last 7 days, Last 30 days, This quarter) and a calendar for a custom range. For a custom range, select the start date and end date in the calendar, then press Confirm.
- Channel filter — All, POS, E-COMM, RTP.
- Status filter — All, Completed, Full Refunded, Partial Refunded (corresponding to the Paid, Refunded, and Partial labels in the table).
When the section opens, the list shows the current quarter's transactions by default, up to today.

Image:
img/tranzactii/02-filtru-perioada.png— small screenshot (crop). the period filter menu open, with the presets on the left and the calendar with the Confirm button on the right.
Image:
img/tranzactii/03-filtre-canal-status.png— small screenshot (crop). the Channel (All/POS/E-COMM/RTP) and Status (All/Completed/Full Refunded/Partial Refunded) filter rows, each with one active option. The list is paginated: at the bottom of the table, choose the number of rows shown per page — 10, 25, 50, or 100 — and navigate between pages.
Refunding a transaction
A completed transaction can be refunded in full or in part, directly from the details panel (see the Transaction details subsection). Refunds are available to the admin, manager, and seller roles — for the reporter role, the Refund button is not shown.
Open the transaction details and press the Refund button at the bottom of the panel. The button is active only for paid transactions that can still be refunded; for a transaction that has already been refunded, or for which the bank does not allow a refund, the button stays inactive. If a refund request still isn't possible, the portal displays the message "Refunds are not possible for this transaction."

Image:
img/tranzactii/04-buton-rambursare.png— small screenshot (crop). the details panel with the active Refund button, at the bottom. The Revert summ window opens, with a reason preselected and the description filled in automatically — both can be changed:
- Reason — the reason for the refund, chosen from the dropdown list (required).
- Reason description — the refund description, freely editable (required).
For a partial refund, turn on the Partial refund toggle and enter the amount in the Partial refund amount field. The amount entered cannot exceed the transaction value — otherwise an error message is shown, and the refund cannot be confirmed.

Image:
img/tranzactii/05-fereastra-rambursare.png— large screenshot (full screen). the Revert summ window, with the reason selected, the description filled in, and the Partial refund toggle on, with the amount field visible. Press OK to confirm. The window displays the message "Waiting for a refund decision" and a progress bar until a response is received; the window can be closed in the meantime — the request continues in the background. After confirmation, the transaction's status updates in the list (Refunded or Partial). If the request is declined or the waiting time expires, the portal displays a corresponding message — check the transaction's status in the list.

Image:
img/tranzactii/06-asteptare-rambursare.png— small screenshot (crop). the refund window in the waiting state, with the progress bar.
Exporting transactions to CSV
The Export as CSV button, located above the table, downloads a .csv file with all the transactions matching the applied filters — search, period, and status — not just the displayed page. The Channel filter does not apply to the exported file. The button is inactive while the list is loading, during export, or when the list contains no transactions. The export buttons are available to the admin, manager, and reporter roles — for the seller role, neither Export as CSV nor Tips Report is shown.
The downloaded file can be opened in external applications (e.g., Excel) for reporting and bookkeeping.

Image:
img/tranzactii/07-export-csv.png— small screenshot (crop). the Tips Report and Export as CSV buttons above the table. The Tips Report button downloads a separate CSV report, containing only the tips collected. In the window that opens, choose:
- Period — Yesterday, Day before yesterday, Last week, or Custom period (with a start date and end date).
- All Stores — keep all stores, or choose a specific store from the list.
Press Export as CSV to download the report. If there are no tips in the chosen period, the message "No data" is displayed.

Image:
img/tranzactii/08-raport-bacsisuri.png— small screenshot (crop). the Tips Report window, with the period selector and the store selector.
Transaction details
Clicking a transaction in the list opens the details panel — a side panel that slides in from the right, over the page content.

Image:
img/tranzactii/09-detalii-tranzactie.png— large screenshot (full screen). the details panel open over the list: the amount, the status, the information card, and the amount breakdown. The panel shows:
- The header — the payment channel and the transaction ID.
- The transaction amount and its status.
- The information card — Store, Description, Date, Channel, and, where available, Ref. number and Terminal ID.
- The amount breakdown — Payment amount, Tip, and Total amount (when the portal receives the payment components) or Gross amount; then Commission (with the applied percentage, when available) and Merchant net — the net amount received by the merchant.
The More details link expands the panel with additional information, shown only if available for that transaction: Terminal ID, POS ID, Seller, MCC, Approval code, the address of the store where the payment was made, the SWIFT data (message type, message ID, payer's SWIFT code), Payment system, Client name, Client fiscal code, and Transaction type code.

Image:
img/tranzactii/10-mai-multe-detalii.png— small screenshot (crop). the More details section expanded, with the additional fields visible. The Refund button at the bottom of the panel starts the refund process (see the Refunding a transaction subsection).
Online Operations
The Online Operations section brings together remotely initiated payments: payment links and payment requests (Request to Pay). The section is visible to all roles — admin, manager, reporter, and seller. Creating links and payment requests, and importing requests from a file, are available to admin, manager, and seller; the reporter role views the lists and details only, without the creation buttons or the sidebar quick actions.
At the top of the page are two tabs: Payment Links and Request to Pay; the open tab shows, next to it, the number of records found with the current filters. The sidebar menu also contains the quick buttons Link and RTP, which open the creation forms directly — New payment link and Create RTP, respectively — without going through the lists.

Image:
img/operatiuni-online/01-linkuri-lista.png— large screenshot (full screen). the Payment Links tab: the two tabs at the top, the search bar, the Create Link button, the status filters, and the links table.
Payment Links
The Payment Links tab shows all the payment links created by the merchant. The table contains the columns:
- ID — the link identifier (e.g., LK-204).
- Date added — the date and time it was created.
- Amount — the payment value, with the currency.
- Description — the order ID or the store name.
- Client phone — the client's phone number, if available.
- Payment type — the method used (e.g., QR, RTP).
- Status — the payment status.
Above the table are the search bar, the period filter (the same presets and calendar as on the Transactions page), and the status filter: All, Completed, Created, Payment pending, Expired, Declined, Failed. The ID, Date added, and Amount columns can be sorted by clicking the column header. The list is paginated (10/25/50/100 rows per page).

Image:
img/operatiuni-online/02-linkuri-filtre.png— small screenshot (crop). the status filter row for the links list, with one option active. To create a new link, press the Create Link button (available to the admin, manager, and seller roles). The New payment link page opens, where you fill in the required fields:
- Amount request — the payment value.
- Select terminal — the terminal associated with the payment.
- Payment Description — the purpose of the payment, visible to the client.

Image:
img/operatiuni-online/03-link-nou.png— large screenshot (full screen). the New payment link page with the 3 fields and the Cancel / Create Link buttons. After pressing the Create Link button, the page displays the Payment link created block with the address of the payment page. Press Copy to copy the link and send it to the client. The Back to Payment Links button returns to the list. The Create another link button clears the screen and opens an empty form for the next link.

Image:
img/operatiuni-online/04-link-creat.png— small screenshot (crop). the Payment link created block, with the link shown and the Copy button. Clicking a link in the list opens the details panel (LK followed by the ID), with the amount, status, and payment information: Date added, Store name, Amount, Order ID on the store side, Payment type, Terminal ID, and Client phone. A second card shows Payment ID and Payment link (both with a copy button), Pay description, Client name, and Client email, followed by the technical integration addresses (Callback url, Success url, Fail URL — all with a copy button) and the payment verification information (Checkout count, Last checked, Redirected to merchant). The Error description row shows the error details for failed payments.

Image:
img/operatiuni-online/05-link-detalii.png— large screenshot (full screen). the details panel for a payment link, with the amount, status, and information cards.
Request to Pay (RTP)
The Request to Pay tab manages the payment requests sent to clients via Request to Pay. The tab has two sub-tabs: Requests and Import history. Next to them is the Import button (see the Importing requests from a file subsection) and, on the Requests sub-tab, the Create RTP button.
The requests table contains the columns:
- ID — the request identifier (e.g., RTP-317).
- Client identifier — the recipient's phone number or IBAN, with a type label (MOBILE or IBAN).
- Destination — the request description.
- Date — the date and time it was created.
- Amount — the request value, with the currency.
- Request Expiry Date — the deadline by which the request can be paid.
- Status — the request status: Created, Payment pending, Paid, Expired, Canceled, Denied, or Error.
Above the table are the search bar, the period filter (the same presets and calendar as on the Transactions page), and the status filter: All, Payment pending, Paid, Expired, Canceled (requests with the Created, Denied, and Error statuses are found under All). The ID, Date, and Amount columns can be sorted by clicking the column header; the list is paginated (10/25/50/100 rows per page).

Image:
img/operatiuni-online/06-rtp-lista.png— large screenshot (full screen). the Requests sub-tab: the Requests / Import history sub-tabs, the Import and Create RTP buttons, the search bar with the period filter next to it, the status filters, and the requests table. To send a new request, press the Create RTP button (available to the admin, manager, and seller roles). The creation page opens, where you fill in:
- Client Name (required).
- Client Phone Number (required) — the +373 prefix is filled in automatically.
- Amount request (required).
- Order ID — the order identifier; it is generated automatically and can be changed.
- Select terminal (required) — the terminal the request is sent from.
- Payment Description (required).
Press Send to dispatch the request — it appears in the requests table. The Cancel button returns to the list without sending.

Image:
img/operatiuni-online/07-rtp-nou.png— large screenshot (full screen). the Create RTP page with the form and the Cancel / Send buttons. Clicking a request in the list opens the details panel (RTP followed by the ID), with the amount, status, and request information: Destination, Client identifier, Date, RTP source (the platform the request was generated from — e.g., ecomm or mportal), and Request Expiry Date. A second card shows, where available, Terminal ID, External Request ID, Transaction ID (the transaction resulting from the payment), Error Code and Error Message (for failed requests), and Last Update Date.

Image:
img/operatiuni-online/08-rtp-detalii.png— small screenshot (crop). the details panel for an RTP request, with the client identifier and the information cards.
Importing requests from a file
The Import button lets you send multiple payment requests from a single file; like creating requests, it is available to the admin, manager, and seller roles, while the Import history sub-tab can be viewed by every role. Pressing the button opens the Import file window, where you fill in:
- Select terminal (required) — the terminal the requests are sent from.
- Select file (required) — drag the file into the marked area, or click it to choose one. Only *.csv and *.xlsx files are accepted.

Image:
img/operatiuni-online/09-import-fisier.png— small screenshot (crop). the Import file window, with the terminal selector and the file upload area. Press Import to send the file. Once the file is accepted, the window closes, a confirmation message appears, and the portal automatically switches to the Import history sub-tab, where you can track the processing. If the document contains invalid rows, the window stays open and shows the "Incorrect records in the document" block with the error details — these can be copied with the dedicated button, to correct the file or request support.
The Import history table shows: File name, Imported by, Date, Total (the number of records in the file), Successful, Errors, and Status (In progress, Completed, or Failed). Clicking a row opens the import's details panel; for imports with issues, it also includes the Error details block.

Image:
img/operatiuni-online/10-istoric-importuri.png— large screenshot (full screen). the Import history sub-tab with the imports table and the details panel open for an import with errors.
Disputes
The Disputes section shows the disputes between the merchant and their bank, related to processed payments. Here you track the status of each dispute, communicate with the bank, and submit supporting documents. The section is available to the admin, manager, and reporter roles. Replying in a dispute, attaching documents, and assigning the dispute back to the bank are available to admin and manager only — the reporter role reads the conversation and downloads the attachments, without the message field.
In the sidebar menu, the Disputes item shows a red badge with the number of disputes assigned to the merchant. The number updates automatically (within one minute at most) and disappears when there are no more disputes assigned to the merchant.

Image:
img/dispute/01-lista-dispute.png— large screenshot (full screen). the Disputes page with the table, the status filters, and the badge with the number of disputes in the sidebar menu.
Disputes list
The table shows one row per dispute, with the following columns:
- ID — the dispute identifier (e.g., DSP-45).
- Transactions — the dispute's external reference in the MIA system (TX-…).
- Category — the dispute category.
- Reason — the dispute title.
- Assigned on — who needs to respond at this moment: BANK or Merchant.
- Date — the date and time it was created.
- Status — the dispute status: ON DISCUSSION, APPROVED, Canceled, or Closed.
Above the table is the status filter with the options On Discussion, All, and Closed. The Closed filter shows only disputes with the Closed status; those with the Approved or Canceled status are found under All. When there are On Discussion disputes on the current page, a warning label with their number appears next to the filters ("needs response").
Next to the search bar is the period filter — the button with the date range opens a menu with 5 presets (Today, Yesterday, Last 7 days, Last 14 days, Last 30 days) and a calendar for a custom range. For a custom range, select the start date and end date in the calendar, then press Confirm. By default, the list shows the disputes from the current quarter. The chosen period is saved in the page address, so it is kept after reloading the page. Changing the period returns the list to the first page and closes the open details panel.
The list is paginated (10/25/50/100 rows per page). The ID, Category, Reason, and Date columns can be sorted by clicking the column header.

Image:
img/dispute/02-filtre-status.png— small screenshot (crop). the On Discussion / All / Closed filters and the "needs response" label. Clicking a dispute in the list opens the details panel — a side panel that slides in from the right, over the page content.
Dispute details
The details panel has two tabs: BANK — the conversation with the bank (the tab open by default) — and Details — the dispute information.
The Details tab shows the disputed amount, the status, and the dispute data: Dispute ID, Title, Category, Reason, Description, Assigned on, MIA dispute ID, and Date. The Payment info block contains the data for the payment involved: Swift message ID, Swift message type, Amount, CCY (optional), and MIA POS tx ID.

Image:
img/dispute/03-detalii-disputa.png— large screenshot (full screen). the details panel on the Details tab, with the amount, status, and the Payment info block.
Communicating with the bank
The BANK tab shows the conversation with the bank in chronological order: the bank's messages on the left, the merchant's messages on the right. New messages appear automatically, without reloading the page. Files attached to messages are downloaded by clicking their name.
While the dispute has the On Discussion status, the message field is available at the bottom of the tab (for the admin and manager roles):
- Write your message and press the send button (or the Enter key).
- The paperclip icon attaches a file to the message (one file per message). Only images (JPG, PNG, WebP, SVG) up to 10 MB are accepted. The file is sent together with a text message — it cannot be sent on its own.
For disputes with the Approved, Canceled, or Closed status, the conversation stays read-only.

Image:
img/dispute/04-chat-banca.png— large screenshot (full screen). the BANK tab with a few messages from both sides, an attachment, and the active message field. When the dispute is assigned to the merchant and is On Discussion, the Assign to bank button is shown above the conversation (for the admin and manager roles) — use it after you've replied, to transfer the dispute back to the bank for review. Pressing it asks for confirmation ("Are you sure you want to assign the dispute to the bank?"); after confirming, the message "Dispute assigned to bank" appears, and the dispute moves to the bank's review.

Image:
img/dispute/05-atribuie-bancii.png— small screenshot (crop). the Assign to bank confirmation window.
Reports
The Reports section brings together the portal's downloadable reports. The section is visible to the admin, manager, and reporter roles — the seller role does not have access.
Currently, only one report is available: B2B Payments Report — download data on B2B payments for a selected period. The tips report is downloaded from the Transactions section (see the Exporting transactions to CSV subsection).

Image:
img/rapoarte/01-pagina-rapoarte.png— large screenshot (full screen). the Reports page with the B2B Payments Report card.
B2B Payments Report
Press the B2B Payments Report card. A window opens where you choose:
- Period — Yesterday (default), Day before yesterday, Last week, or Custom period. For the custom period, the Start date and End date fields appear, with selection from the calendar.
- Store — All stores, or a specific store.

Image:
img/rapoarte/02-raport-b2b.png— small screenshot (crop). the B2B Payments Report window, with the period selector and the store selector. Press Export as CSV. The portal displays the message "Generating the report…", and once done, the browser downloads the .csv file (which opens directly in Excel or another spreadsheet program), the "Report downloaded" confirmation appears, and the window closes automatically. If there is no data for the chosen period, the message "No data" is displayed, and the window stays open so you can choose another period.
Administration
The Administration section brings together the management of the merchant's structure: stores, terminals, sellers, users and the company profile. The section is visible to the admin, manager and reporter roles. Changes made here — creating and editing records, attaching terminals, managing sellers — belong to the admin and manager roles; the reporter role sees the same lists and details in read-only mode. The Users tab is an exception on both counts: it is visible to administrators only.
At the top of the page there are five tabs: Stores, Terminals, Sellers, Users and Profile (the Users tab is shown to administrators only, so the other roles see four). The open tab shows, next to its name, the number of records found (except for the Profile tab). When there are terminals not attached to a store, an attention dot appears on the Terminals tab ("There are terminals without a store").

Image:
img/administrare/01-file-administrare.png— small screenshot (crop). the tab bar of the Administration section, with the record count on the active tab and the attention dot on the Terminals tab. The first four tabs (Stores, Terminals, Sellers, Users) work the same way: the search bar filters the records, the lists are paginated (10/25/50/100 rows per page, with page navigation at the bottom right), clicking a row opens the details panel — a side panel on the right — and right-clicking a row opens the context menu with the available actions. From the details panel you go to the edit page via the Edit button. On the edit pages, the Save button becomes active after the first change, and Reset returns the data to the saved state. After each successful save or delete, the portal shows a confirmation message (toast).
When the search finds no records, the table shows the empty state — a box icon and the text "Empty / No data yet, try visiting this section later." Clear the text in the search bar to return to the list (see the examples in each tab below).
For the reporter role, the same tabs are read-only: details open in the side panel without the Edit button, the context menu and edit pages are not available, and a seller's card does not open at all — it contains the seller's login credentials, which remain reserved for the admin and manager roles.
Stores
The Stores tab shows the merchant's stores, with the columns: Store ID, Store name, Address, Payment purpose and Registration date. The search bar above filters by ID, name or address.

Image:
img/administrare/02-magazine-lista.png— large screenshot (full screen). the Stores tab with the table, the search bar, the New store button and the pagination. If the search finds no store, the table shows the empty state.

Image:
img/administrare/03-magazine-gol.png— large screenshot (full screen). the empty state of the Stores list (the box icon and the text "Empty") after a search with no results. To add a store, press the New store button (available to the admin and manager roles, like any change in this section). The creation page opens, where you fill in:
- Store name — required.
- Address — required.
- Payment purpose — optional, between 2 and 32 characters.
- Comment — optional.

Image:
img/administrare/04-magazin-nou.png— large screenshot (full screen). the New store page with the form and the Cancel / Save buttons. If you press Save without filling in the required fields, the form is not submitted: the message "This is a required field" appears under the Store name and Address fields, and for an incorrectly filled Payment purpose the message "The field value must be between 2 and 32 characters" appears. The field in error is highlighted in red.

Image:
img/administrare/05-magazin-validare.png— large screenshot (full screen). the creation page with the validation errors under the empty required fields. After filling in the form correctly and pressing Save, the store appears in the list, and the portal shows the confirmation "Store successfully created" and a second message suggesting the next step: "Next step: add a seller so the store can take payments." — with a New seller button that opens the new seller form directly, with the store preselected, and a Close button.

Image:
img/administrare/08-magazin-creat.png— large screenshot (full screen). the Stores list with the confirmation messages after creating a store (the success toast and the next-step suggestion). To edit, open the store details (click the row) and press Edit. On the edit page, the Store ID is not shown as a separate field — it appears only in the page URL (/app/stores/{id}) — while the other fields can be changed; the Save button becomes active after the first change, and Reset returns the saved values.

Image:
img/administrare/06-magazin-editare.png— large screenshot (full screen). the store edit page with Store ID read-only and the Delete / Reset / Save buttons. The Delete button removes the store — the portal asks for confirmation in a dialog, with the title "Confirm store delete?" and the text "Are you sure you want to remove the store #", before deleting. After deletion, the confirmation message "Store successfully deleted" appears.

Image:
img/administrare/07-magazin-stergere.png— small screenshot (crop). the store deletion confirmation dialog, with the Cancel and Delete buttons.
Terminals
The Terminals tab shows the terminals assigned to the merchant. Terminals are registered by the bank — they cannot be created or deleted from the portal; here they are attached to stores and configured.
The table columns: POS ID, Terminal ID, Terminal type (Mia POS, Ecomm, RTP, API), Store name, MCC, Condition and Registration date. The possible states: Attached, Activated, Unattached and others. Terminals without a store are marked with the red "No store" label and show the Assign to store button directly in the row; such a terminal cannot accept payments.

Image:
img/administrare/09-terminale-lista.png— large screenshot (full screen). the Terminals tab with the table, a terminal without a store (the red "No store" label and the Assign to store button) and the attention dot on the tab. Clicking a row opens the terminal details panel, which shows its data (Date, POS ID, Terminal ID, type, state, Merchant ID, Merchant IDNO, MCC, comment, TIPS IBAN), the associated store (with a link to the store card) and the current QR settings (QR type, Amount type, QR code validity period, Enable tips, POS lock). At the bottom, the panel offers the Assign to store / Unassign to store and Edit buttons.

Image:
img/administrare/10-terminal-detalii.png— large screenshot (full screen). the details panel of a terminal with the data, the Store block, the QR settings and the Assign/Unassign and Edit buttons. Attaching to a store: press the Assign to store button (from the row of unattached terminals or from the details panel). A dialog opens with the list of stores — choose the store (#id / name) and confirm. The same button is also used to move an already attached terminal to another store.

Image:
img/administrare/11-atasare-terminal.png— small screenshot (crop). the terminal assignment dialog, with the store selector. To detach a terminal from a store, use Unassign to store in the details panel and confirm in the dialog that appears; after detaching, the quick Assign to store button reappears in the terminal's row.

Image:
img/administrare/13-terminal-detasare.png— small screenshot (crop). the confirmation dialog for detaching the terminal from the store. The Edit button opens the terminal page. The left side presents the terminal data in read-only mode (the Terminal details block) — including the Data for terminal activation block (IDNO Merchant and Terminal ID, used to activate the terminal) — while the right side, Terminal operation mode, is the only editable area:
- QR type — the QR code type: Dynamic QR (accepts only a fixed amount, one transaction per QR), Static QR (fixed, controlled and unspecified amounts, unlimited transactions) or Hybrid QR (fixed and controlled amounts, at most one transaction at a time). Each option has a short description below it.
- Amount type — the amount type: Fixed, Controlled or Not specified. For Dynamic QR the field is not shown — the amount is always fixed.
- QR code validity period — the QR validity duration, in seconds, between 15 and 5184000 (60 days); default 300. For Static QR the field is not shown — a static code does not expire. A value outside the range produces the message "Value must be between 15 and 5184000 seconds".
- Enable tips — lets customers add a tip to the payment.
- Show all transactions grouped by shifts — groups transactions by shifts.
- POS lock — prevents changing the settings from the miaPos app on the terminal.
If the terminal does not yet have saved settings, the form shows the default values: Dynamic QR, Fixed amount, 300 seconds, tips and POS lock disabled. The Save button becomes active only after a change; after saving, the portal returns to the terminals list.

Image:
img/administrare/12-terminal-setari.png— large screenshot (full screen). the terminal page with the data in read-only mode on the left (Terminal details, Data for terminal activation) and the Terminal operation mode block on the right.
Sellers
The Sellers tab manages the people who collect payments at the terminals. The table columns: Seller ID, Seller name, Store name, Condition and Registration date. The possible states: Online, Offline and Suspended. Above the table is the status filter (All, Online, Offline, Suspended). Sellers without a store are marked with the red "No store" label — such a seller cannot log in to the POS.

Image:
img/administrare/14-vanzatori-lista.png— large screenshot (full screen). the Sellers tab with the table, the status filters and the New seller button. If the filter or the search returns no seller, the table shows the empty state.

Image:
img/administrare/15-vanzatori-gol.png— large screenshot (full screen). the empty state of the Sellers list after a search with no results. To add a seller, press the New seller button. On the creation page you fill in, in the General block:
- Seller name — required.
- Store — required, the store where the seller works. If there is a single store, it is preselected; if no store exists yet, the portal first suggests creating one.
- Phone — required.
- Email — required.
- Comment — optional.
In the Credentials block you set the login credentials for the POS app:
- Login — required, 3–30 characters: Latin letters, digits, dot, dash and underscore, no spaces. Or check "Use phone number" to use the phone as the login.
- Password — required, can be entered manually or generated with the Generate button (uppercase and lowercase Latin letters and digits); the icons next to it show or copy the password.

Image:
img/administrare/16-vanzator-nou.png— large screenshot (full screen). the New seller page with the General and Credentials blocks. If you press Save with required fields empty, the form is not submitted and the validation messages appear under those fields ("This is a required field" and, for Login, the format rule).

Image:
img/administrare/17-vanzator-validare.png— large screenshot (full screen). the seller creation page with the validation errors on the required fields. After filling in the form and pressing Save, the seller appears in the list and can log in to the POS app with the credentials that were set.
Clicking a row opens the seller details panel, with the Details, Contact and Credentials (login) blocks. At the bottom, the panel offers the actions: Reassign (reassign to another store), Suspend / Restore (suspend or reactivate access), Delete and Edit.

Image:
img/administrare/18-vanzator-panou.png— large screenshot (full screen). the seller details panel with the Reassign / Suspend / Delete / Edit buttons. The same actions are available from the context menu — right-click the seller row. The context menu works the same way on all the lists in the Administration section, with the actions appropriate for each record type (on the Stores and Users lists it contains only Edit).

Image:
img/administrare/20-meniu-contextual.png— small screenshot (crop). the context menu opened with a right-click on a seller row, with the Edit / Reassign / Suspend / Delete actions. Actions that change data ask for confirmation in a separate dialog. Suspend temporarily blocks the seller's access:

Image:
img/administrare/21-vanzator-suspendare.png— small screenshot (crop). the confirmation dialog for suspending the seller. Reassign transfers the seller to another store, with the store selected from the list:

Image:
img/administrare/23-vanzator-reatribuire.png— small screenshot (crop). the seller reassignment dialog, with the store selector. Delete removes the seller, also with confirmation:

Image:
img/administrare/22-vanzator-stergere.png— small screenshot (crop). the confirmation dialog for deleting the seller. The Edit button (from the panel or the context menu) opens the edit page: the ID is read-only, the fields are the same as on creation, and changing the password requires a separate confirmation. The page also offers the Suspend/Restore and Delete buttons.

Image:
img/administrare/19-vanzator-editare.png— large screenshot (full screen). the seller edit page with the ID read-only and the Suspend / Delete / Reset / Save actions.
Users
The Users tab manages company employees' access to the Merchant Portal. The tab is visible to administrators only — the other roles do not see it at all. The table columns: ID, Full name, Email, Phone, Roles, Registration date and Store access.

Image:
img/administrare/24-utilizatori-lista.png— large screenshot (full screen). the Users tab with the table and the New user button. If the search finds no user, the table shows the empty state.

Image:
img/administrare/25-utilizatori-gol.png— large screenshot (full screen). the empty state of the Users list after a search with no results. To add a user, press the New user button. On the creation page you fill in the required fields:
- Full name.
- Email.
- Phone.
- IDNP — 13 digits.
- Roles — one or more roles, shown as checkable options; next to each, the ⓘ icon shows the role description. The role descriptions are in the Introduction chapter. The form offers only the seller, manager and reporter roles — the admin role is intentionally absent here: the merchant administrator account is created by the bank via SAP when the merchant is registered.
When roles that do not have full access are chosen, the Stores selector additionally appears: check "All stores" or select the stores the user has access to.

Image:
img/administrare/26-utilizator-nou.png— large screenshot (full screen). the New user page with the form and the roles block (one role checked, with the ⓘ icon). If you press Save with required fields empty, the validation messages appear under them ("This is a required field"), including the requirement to check at least one role.

Image:
img/administrare/27-utilizator-validare.png— large screenshot (full screen). the user creation page with the validation errors on the required fields. After Save, the portal opens the page of the newly created user, who can then log in to the portal with their phone number. To edit, open the user details and press Edit; on the edit page the ID is read-only, and Reset and Delete (with confirmation) are also available.

Image:
img/administrare/28-utilizator-editare.png— large screenshot (full screen). the user edit page with the ID read-only and the Delete / Reset / Save buttons.
Image:
img/administrare/29-utilizator-stergere.png— small screenshot (crop). the confirmation dialog for deleting the user.
Merchant Profile
The Profile tab shows the company data, in read-only mode:
- Merchant information — Merchant ID, Created at, Legal name, Trade name, IDNO Merchant, LEI code, Recipient account IBAN and TIPS IBAN.
- Administrator information — Admin ID, Full name, Administrator IDNP, Phone and Email.
The Merchant settings block is visible to the admin role only (the other roles see the profile information in read-only mode, without this block) and allows you to:
- Merchant logo — upload (Upload logo), change (Change logo) or remove (Remove logo) the logo shown at the top of the sidebar menu. Accepted formats: JPG, PNG, WebP, SVG, up to 10 MB.
- Tips report recipient email — the address the tip reports are sent to.
- Enable e-commerce support — turns on the e-comm functionality for the merchant.
Press Save to apply the changes — the confirmation "Merchant settings successfully updated" appears.

Image:
img/administrare/30-profil-comerciant.png— large screenshot (full screen). the Profile tab with the Merchant information, Administrator information and Merchant settings blocks (logo, tips email, e-commerce support).
Platform Features
This chapter describes the features available in every section of the portal: global search, keyboard shortcuts, language and theme settings, and signing out.
Global search
The search bar at the top of the screen ("Search transactions, stores, sellers...") searches the entire portal at once: transactions, stores, sellers, terminals, payment requests (RTP), and users. Transactions are searched over the last 3 years. The search respects your role: it only looks through the categories your role can open — the seller role searches transactions and payment requests only, and the Users category appears for administrators only.
Enter at least 2 characters — the results appear immediately below the search bar, grouped by category (Transactions, Stores, Sellers, Terminals, Request to Pay, Users), each result with its title, details, and, where applicable, its status. Each category shows at most 5 results — for a complete search, open that section and use its own search.
Selecting a result opens the corresponding section, with that record preselected and its details panel open.

Image:
img/functionalitati-transversale/01-cautare-globala.png— large screenshot (full screen). global search open, with results from multiple categories. On narrow screens, the bar is collapsed to a search icon — tap it to open the field to full width.
Keyboard shortcuts
- Ctrl+K (⌘K on Mac; the hint in the search field always shows the ⌘K symbol) — activates global search, from any section.
- ↓ / ↑ — navigate through the search results.
- Enter — opens the selected result.
- Esc — closes the results list; it also closes open modal windows and details panels.
Language and theme
Press the gear icon at the bottom of the sidebar menu (on narrow screens, first open the menu from the button in the top-left corner) — the Settings window opens:
- Language — the portal is available in 5 languages: Română (default), Русский, English, Deutsch, Français. The language can also be chosen from the sign-in screen.
- Theme — the portal's appearance: Light, Dark, or Dusk.
Both changes apply immediately, without a confirmation button, are kept on the current device, and remain active on the next sign-ins.

Image:
img/functionalitati-transversale/02-setari-limba-tema.png— small screenshot (crop). the Settings window with the language selector and the Light / Dark / Dusk themes.
Signing out
In the same Settings window, at the bottom, is the red Logout button. Pressing it closes the session immediately, and the portal returns to the sign-in screen.

Image:
img/functionalitati-transversale/03-deconectare.png— small screenshot (crop). the Settings window with the Logout button highlighted.
Support
For questions and issues related to the portal or to payments, use the Support menu in the top bar of the screen (the headset icon). The menu contains the contact channels:
- Your bank's support phone number (if the bank has set it up).
- Your bank's support email (if the bank has set it up).
- Telegram — the miaPOS support bot (@miaPOSLineBot), always available.
Selecting a channel automatically copies the contact details and opens the corresponding app (phone call, email, or Telegram).

Image:
img/asistenta/01-meniu-asistenta.png— small screenshot (crop). the Support menu open from the top bar, with the phone, email, and Telegram option. The phone number and email shown belong to the bank that services the merchant, so they may differ from one merchant to another. Your bank is shown by its logo, at the top of the sidebar menu.
Before signing in, the sign-in screen shows the general miaPOS contacts: phone +373 60 665 335 and email [email protected].

