The point of sale (POS) is the place or digital checkout step where a merchant records a sale and the customer pays for goods or services. A POS system is the hardware and software used to calculate the amount due, accept or record payment, issue a receipt, and update sales records.
The POS and the payment system overlap, but they are not identical. A POS can record cash, card, wallet, gift-card, invoice, or split-tender sales. The payment terminal, gateway, processor, acquirer, and issuer perform separate parts of an electronic payment.
Key Takeaways
- POS can mean the checkout event, checkout location, or merchant sales system.
- The POS records the sale; a payment terminal or gateway captures and sends an electronic payment request.
- Authorization does not mean the merchant has received settled funds.
- Sales, taxes, tips, discounts, refunds, inventory, payment batches, and deposits need separate reconciliation.
- Security scope depends on which systems store, process, transmit, or can affect payment account data.
What a POS System Does
| Function | Typical POS record | Control question |
|---|
| Product or service entry | Item, quantity, price, and employee | Was the correct item and price used? |
| Pricing | Discount, promotion, tax, tip, and total | Who can change prices or override rules? |
| Payment | Tender type, amount, status, and transaction ID | Was payment approved, captured, or only attempted? |
| Receipt | Time, location, line items, tax, and payment reference | Can the customer and merchant identify the sale? |
| Inventory | Units sold, returned, transferred, or adjusted | Does physical stock reconcile to system records? |
| Accounting | Revenue, tax payable, cash, card receivable, and fees | Do POS totals reconcile to the ledger and deposits? |
Some POS systems also manage staff schedules, customer loyalty, reservations, kitchen orders, or e-commerce inventory. Those features are operational modules, not part of the core definition of payment processing.
POS, Terminal, Gateway, and Processor
| Component | Primary job | Evidence it creates |
|---|
| POS system | Records what was sold and the amount due | Sales ticket, receipt, refund, tax, and inventory records |
| POS terminal | Captures a card or wallet credential and transaction data | Entry mode, terminal ID, verification result, and authorization response |
| Payment gateway | Protects, formats, and transmits payment requests between systems | Gateway transaction ID, token, response, and webhook or callback |
| Payment processor | Handles transaction messages for merchants, acquirers, issuers, or other parties | Processor logs, batches, clearing files, and settlement reports |
| Acquirer | Provides the merchant’s card-acceptance and settlement relationship | Merchant agreement, funding, fee, reserve, and chargeback records |
One provider may bundle several roles. The contract and transaction records, not the brand name, show which entity performed each function.
Worked Example: Sale, Refund, and Deposit
A retailer records a $75 sale plus $9.75 in sales tax, for a total of $84.75. The customer pays by card. The terminal returns an approval, and the POS marks the ticket paid.
The next day, the customer returns a $20 item. A useful record trail should distinguish:
- the original $75 merchandise sale and $9.75 tax;
- the $84.75 card authorization and capture;
- the processor batch containing the original transaction;
- the merchant deposit, net of fees or adjustments under its agreement;
- the $20 return and related tax reversal;
- the refund message sent to the processor; and
- the later refund posting to the cardholder account.
The POS report, processor report, bank deposit, and general ledger may show different timing and presentation. A net bank deposit should not be recorded as gross sales without separating fees, refunds, taxes, and other adjustments.
How to Evaluate a POS System
- Map each store, register, terminal, user, merchant ID, gateway, processor, and bank account.
- Confirm price, discount, refund, void, no-sale, and tax permissions by role.
- Separate payment attempt, authorization, capture, batch close, clearing, settlement, and refund statuses.
- Reconcile daily sales by tender to cash counts, processor batches, deposits, fees, and the ledger.
- Review offline transactions, duplicate attempts, manual entry, fallback, and declined payments.
- Control product, tax, employee, and bank-account master-data changes.
- Maintain terminal inventories and inspect devices for tampering or substitution.
- Restrict administrative access and monitor software, integration, and configuration changes.
- Retain receipts and transaction evidence according to applicable business, tax, payment, and privacy rules.
Risks and Common Mistakes
- Treating an approval response as final settlement.
- Calling the terminal, gateway, processor, and acquirer the same entity.
- Letting staff share accounts or use unrestricted manager overrides.
- Recording only net processor deposits and losing gross sales, fees, taxes, and refunds.
- Retrying after a timeout without checking for a prior approval.
- Leaving default credentials, unused services, or unpatched integrations active.
- Storing more cardholder or customer data than the business needs.
- Assuming cloud hosting transfers all security and compliance responsibility to the vendor.
Official Resources
Payment acceptance, tax, receipt, privacy, and recordkeeping requirements vary by transaction and jurisdiction. A merchant should apply its current agreements and applicable rules.
FAQs
Is a POS the same as a payment terminal?
No. The POS records the sale and amount due. A payment terminal is the endpoint that captures payment credentials and communicates transaction data. They may be integrated in one device.
Can a POS system accept cash?
Yes. A POS can record cash and other tenders even when no electronic payment processor is involved.
Does a completed POS sale mean the merchant was paid?
Not necessarily. A card sale may still require capture, batch submission, clearing, and settlement, and it may later be refunded or disputed.
- POS Terminal: Payment endpoint used to capture card or wallet transaction data.
- Mobile Point of Sale (mPOS): Portable POS deployment using a phone, tablet, reader, or mobile terminal.
- Payment Gateway: Interface that protects and transmits payment requests between systems.
- Payment Processor: Service provider that processes or routes payment transactions.
- Merchant Account: Commercial acquiring arrangement through which a merchant accepts card payments and receives settlement.
- Credit Card Processing: Authorization, capture, clearing, settlement, and dispute lifecycle for card payments.
Educational Use
This article provides general financial education. It is not merchant, accounting, payment-security, tax, legal, or compliance advice.