miaPOS.eu
Contact sales
Use cases

How merchants run
instant payment acceptance on miaPOS.

Same platform, six paypoints, one ISO 20022 API — recombined to fit the workflow each business actually runs. Pick a case below or scroll through all four.

01 · HoReCa

Restaurants, cafes, bars, hotels

Tap-to-pay at the table, pay-by-link for delivery, tips and split bills built in.

See the case
02 · Retail

Single store to nationwide chains

Hardware POS or SoftPOS at every checkout, role-based cashiers, accounting exports.

See the case
03 · E-commerce

Online checkout in 10 minutes

Ready-made plugins for WordPress, WooCommerce, OpenCart, Magento and more — or REST API.

See the case
04 · Services

Freelancers and recurring invoicing

Payment Links, Request to Pay, and conversational acceptance for repeat clients.

See the case
miaPOS · Use case 01

Restaurants, cafes, bars, hotels.

Speed at the table, lower cost per cover, and the receipts your accountant actually needs — without a tablet stand or a printed QR menu.

Why HoReCa

  • →Tap-to-pay at the table with SoftPOS — waitstaff carry no extra hardware.
  • →Pay-by-link for delivery, phone orders, and room service.
  • →Funds land in your bank account in seconds — not T+3 like cards.
  • →Tip handling and bill splitting in the app — no calculator at the table.
  • →Per-cover acceptance cost drops vs cards. The saving compounds across thousands of covers a month.
miaPOS · Use case 02

Single store to nationwide chains.

Instant acceptance at every register without ripping out the POS stack your store already trusts.

Why Retail

  • →Dedicated hardware POS where there's a cash register — SoftPOS on Android where there isn't. Phase your hardware refresh on your own schedule.
  • →Multi-cashier support with role-based permissions per terminal.
  • →Daily reconciliation, CSV exports, and integrations with the accounting suite already in use.
  • →Loyalty hook and returning-customer recognition (pilot) — payment data, repurposed.
  • →One merchant account covers in-store, click-and-collect, returns, and online — same dashboard, same payouts.
miaPOS · Use case 03

Online checkout that ships in 10 minutes.

Ready-made plugins for the platforms developers already run — and a REST API when the cart is custom.

Why E-commerce

  • →10+ platform plugins — WordPress, WooCommerce, OpenCart, Magento, PrestaShop, Shopify and more. Integration measured in minutes, not sprints.
  • →REST API for custom carts, headless storefronts, and marketplace platforms.
  • →Instant settlement reduces chargeback exposure and cash-flow lag vs card rails.
  • →Request to Pay flow for high-value items, pre-orders, and B2B invoices.
  • →Same dashboard as in-person volume — one P&L per merchant, not one per channel.
miaPOS · Use case 04

Freelancers, professionals, recurring invoicing.

Send a link, get paid in seconds. No card terminal to carry. No IBAN to dictate over the phone.

Why Services

  • →Payment Links for one-off invoices — clients pay from any banking app, no signup, no card details.
  • →Request to Pay for repeat customers — single tap to approve, no link to chase.
  • →Conversational acceptance in Telegram DMs — where the conversation already happens.
  • →ISO 20022 remittance info attached to every transfer — no manual matching of inbound payments.
  • →Same account, same dashboard — whether billing one client or a hundred.

Don't see the case that fits?

The six paypoints recombine into anything from kiosks to subscription billing. Tell us the workflow — we'll map it.

Talk to sales