Point-of-sale payment
What are point-of-sale payments?
Point-of-sale (POS) payments are transactions where a cardholder pays for goods or services at the physical location where the sale occurs. The point of sale is a retail counter, checkout terminal, or any location equipped with a payment terminal, and the methods accepted there include credit and debit cards, , and .
Because both the card and the cardholder are physically present, POS payments are classified as . That classification follows the payment all the way through: the terminal reads the chip or NFC antenna directly rather than relying on typed card data, the issuer receives cryptographic proof that the real card was used, and the transaction lands in a different category than the same purchase made online.
Key facts
- Also known as: POS payments, in-person payments, in-store payments, card-present payments
- Transaction type: , as opposed to a
- Methods accepted: chip and PIN, contactless taps, from a phone or watch, magnetic stripe, QR-code scans, and cash
- Hardware: countertop terminals, mobile card readers, self-service kiosks, and registers with an integrated payment module
- Cost drivers: interchange, card network scheme fees, and the acquirer's markup, all of which vary by market, card type, and
- Applies to: retail stores, restaurants, hospitality, transit, and any business where the sale is completed face to face
How POS payments work
- Card presented. The cardholder taps, inserts, or swipes at the terminal. The terminal reads the EMV chip, the contactless antenna, or the magnetic stripe.
- Data captured and protected. The terminal encrypts the card data at the read head. Most deployments also apply , so the card number itself never sits in the merchant's environment.
- Authorization request sent. The terminal passes the request through the to the , which routes it to the relevant card network and on to the . This is the step.
- Issuer decides. The issuer checks the available balance, the account status, and its own risk rules, then returns an approval or a decline with a response code. The terminal shows the result and prints or emails a receipt.
- Batch submitted. Approved authorizations are held and sent to the acquirer as a group, usually at the close of business. This is , and it converts each authorization into a capture.
- Funds settled. The acquirer collects from the issuers through the networks and pays the merchant the transaction value minus interchange, scheme fees, and its own markup. That final movement of money is .
Why it matters
- Card-present transactions fall into lower interchange categories than equivalent card-not-present transactions, because the chip cryptogram proves the physical card was at the counter. The same basket costs a merchant less to accept in store than online.
- A terminal that can't reach the acquirer stops the sale where it stands. There's no retry queue and no abandoned-cart email, so every minute of connectivity loss is revenue that doesn't get recovered later.
- In markets that have implemented the EMV liability shift, counterfeit-fraud losses land on whichever party supported the weaker technology. A merchant still running stripe-only terminals absorbs that a chip-capable merchant would not.
- Contactless removes the PIN entry step for amounts under the local contactless limit, which cuts the time each cardholder occupies the terminal and raises how many transactions a single lane can clear per hour.
- POS acceptance data feeds the same reporting as online channels, so a store with a misconfigured terminal or an outdated software version shows up as a measurable gap against other locations.
Common issues
- Issuer declines at the counter. The terminal shows a short generic message rather than the issuer's actual reason. Diagnosing whether it was insufficient funds, a risk rule, or an expired card requires the response code from the 's records.
- Chip read failures. A damaged or dirty chip forces a fallback to magnetic stripe. Fallback transactions carry weaker authentication data and are declined more often by issuers that flag them as a fraud signal.
- Offline and store-and-forward approvals. When connectivity drops, some terminals approve under a floor limit and forward the transaction once the link returns. The merchant carries the risk if the issuer declines it after the fact.
- Unclosed batches. If the day's batch is never submitted, the authorizations sit uncaptured and eventually expire, which delays settlement and can void the approval entirely.
- Duplicate charges. A cardholder re-tapping after an ambiguous terminal message produces two authorizations on the same account, and the second one usually surfaces later as a chargeback.
- Terminal software drift. Payment terminals need periodic firmware and configuration updates to stay aligned with network mandates. A location running an outdated build declines transaction types the rest of the estate accepts.
