What Is Virtual POS? Difference From Physical POS and ÖKC

What is virtual POS?

Virtual POS is bank or payment-institution infrastructure that lets you take credit or debit card payments over the internet or mobile channels without a physical terminal. The classic example is checkout on an e-commerce site; in restaurants and cafes it covers marketplace prepayment, your own web orders, table payment via QR link, and collecting payment upfront instead of by card at the door.

Virtual POS does not replace the ÖKC used at the table. For on-premise dining, fiscal recording still runs on a physical payment recorder (ÖKC); virtual POS moves money from digital channels into your business account. Both channels can run the same day: a platform order is collected via virtual POS, and the remaining table bill closes on the physical device.

This guide focuses on restaurant, cafe, takeaway and delivery operations rather than generic e-commerce, and clarifies differences from physical POS and ÖKC in tables and steps.

Where is virtual POS used in a restaurant?

Marketplace payments: On channels such as Yemeksepeti, Getir and Trendyol Yemek, the guest often pays inside the app. The platform transfers your payout; virtual POS or platform payment rails run in the background. In Ritapos the order source is marked as the platform; when you close payment manually in Ritapos, the provider report shows platform or user.

Your own online channel: Card payment on your website or WhatsApp order line needs a virtual POS definition from your bank. When the order lands in Ritapos, write the payment reference in the order note or integration field so kitchen and takeaway screens see that payment was taken.

Pay-by-link at the table: When closing the bill you can send a short payment link by SMS or QR. The guest enters the card on their phone; you collect without carrying a terminal. It shortens queues on busy terraces or festival sites; still clarify fiscal recording duties with your accountant.

Delivery and upfront payment: Venues that accept only prepaid orders instead of cash at the door reduce fraud risk with virtual POS. The courier only verifies delivery; card data is not carried.

Physical POS, ÖKC and virtual POS compared

For physical POS practice see how to use a POS device. For ÖKC and cash register integration see what cash register integration is and cash register integrations.

Virtual POS commission comes per transaction or as a monthly package from the bank; on marketplace orders commission is often bundled in the platform contract. On your own virtual POS, read 3D Secure requirements and chargeback processes in the contract.

Security: 3D Secure and fraud

For card-not-present (CNP) transactions, 3D Secure verification lowers chargeback risk. When you send pay-by-link, match amount and order number in the link description so the guest does not pay the wrong total.

Track repeat cancellations and suspicious card attempts by comparing Ritapos order logs with the bank panel. High card-not-present volume in campaigns can raise fraud scores; banks may ask for extra verification. Share SMS OTP timing with staff without slowing service. Train staff not to take card details by phone; use secure links only.

With bank virtual POS, PCI DSS scope usually keeps card data off your servers via tokenization; using the bank hosted payment page instead of embedding a card form on your site simplifies obligations.

Operations flow: from online order to kitchen

1. The guest confirms the basket on web or app and pays via virtual POS.
2. The payment approval code is written on the order; Ritapos sends it to kitchen and takeaway screens.
3. The kitchen prepares the order; the takeaway channel runs courier or pickup delivery.
4. At day end, match the virtual POS reconciliation report with Ritapos platform/online sales reports.

For marketplace orders, reconciliation runs in the platform panel; Ritapos sales reports check order count and totals. With your own virtual POS, compare the bank day-end report with Ritapos close on the same calendar day.

For partial refunds and cancellations, run the virtual POS refund at the bank and stock corrections in Ritapos. A clear refund policy on menu and website reduces chargeback disputes.

QR at the table and link payment

Offering a payment link with the QR menu improves hygiene and speed. The guest can pay without asking for the bill; if integration is set up, Ritapos table status updates to paid.

On tables with weak Wi-Fi the guest uses mobile data; 3D Secure SMS delay can extend the end of service. Train staff on a backup flow with the server's handheld terminal (physical ÖKC).

To include tip in link payment, add the tip line in Ritapos and reflect the total on the link; otherwise the server takes tip in cash and reports split.

Accounting and VAT

Virtual POS movements appear on the bank statement; fiscal document duties depend on business type and may be completed with e-archive, e-invoice or retail slips. Online sales VAT rates should match dine-in; delivery discount campaigns affect the VAT base.

Platform invoices and commission deductions are separate accounting lines; do not treat Ritapos gross sales and platform net payout as the same number. In dark kitchens and multi-brand kitchens, virtual POS movements should be reported by brand; brand tags in Ritapos simplify bank reconciliation. Build a monthly reconciliation template with your accountant. Online payments after midnight can shift calendar day; align bank value date with Ritapos transaction date at monthly close.

Questions when choosing virtual POS

• What is commission per transaction and the monthly fixed fee?
• Is 3D Secure mandatory; is link payment supported?
• Do refund and installment options fit your restaurant model?
• Is there API integration with Ritapos or your web stack?
• How do chargeback notice timing and evidence upload work?

Continue in the Academy

To see the topic step by step on screen, browse the related lessons in Ritapos Academy.

• Paycell integration
• Taking split payments

For dine-in collection see Inpos integrated POS and the general list on cash register integrations.