POS Payments & Card Machine
This page explains how payment methods work in POS, especially card machine payments. The goal is simple: help staff understand what to click, what to type, and what the app really does.
How card machine works today
Think of the card machine as a separate device. The customer inserts, taps, or swipes the card on that device first. When the machine says approved, the cashier comes back to the POS screen, chooses Card Machine, and records the safe payment proof.
So the machine does the card approval. The app does the sale record, receipt, audit trail, and safe payment evidence.
Even if the machine is physically attached to the same counter computer, the current build still treats it as a separate bank device unless a direct machine integration is built.
Card machine flow chart
What the popup asks for
- Auth or Slip Code: the approval number or machine slip reference.
- Card Number or Last 4: staff can type the last 4 only. The app keeps only safe masked details.
- Expiry: card expiry in simple form like
12/28. - Card Brand: Visa, Mastercard, UnionPay, and so on.
- Cardholder: useful if staff wants a cleaner record.
- Machine or Bank Note: example: Counter 2 machine, HBL terminal, lane 3.
- Extra Note: any short comment the branch wants to keep.
What the app stores and what it does not
- Payment method.
- Auth or slip code.
- Masked card number like
**** **** **** 1111. - Last 4 digits.
- Expiry.
- Card brand.
- Optional holder and machine note.
- Full raw card number for long-term storage.
- CVV.
- PIN.
- Track data from the card.
Difference between payment methods
Cash changes drawer cash and is part of drawer counting.
Real card approval happens outside the app on the machine. POS records safe proof after approval.
Use this only when the payment is already approved outside the app and staff needs to record it safely. It is not a place to store raw full card details.
POS asks for reference and simple proof before saving the sale.
Stripe, PayPal, JazzCash, and Easypaisa are different from Card Machine. Those methods are hosted payment flows. The app waits for gateway confirmation instead of asking the cashier to type machine details.
Why register session still matters
Even when the customer pays by card machine, the sale still belongs to a cashier shift. That is why an open register session is still required.
- The sale belongs to that cashier and terminal.
- The sale appears in sales history and end-of-day summary.
- Cash drawer cash does not increase from that card payment, but the sale still belongs to the shift.
What the receipt shows
The receipt can show a safe summary like: Card Machine | Visa | **** **** **** 1111 | Exp 12/28 | Auth ABC123.
That gives the branch enough proof to understand the payment without exposing sensitive card data.
How to demo this
- Login as
north.cashier@ovion.techoradmin@ovion.tech. - Open POS Terminal and add an item.
- Select Card Machine as payment method.
- Show the popup and explain that this represents the already-approved machine result.
- Enter a fake auth code, last 4 digits, expiry, and brand.
- Finish the sale and show the masked payment on the receipt or sales history.
What would change with real machine integration
A true hardware integration would mean POS sends the amount to the machine, waits for approval from the machine directly, and fills the payment proof automatically. The current build does not do that yet.