Search
316 articles found
Merchant & POS
Transaction types that can be made with a card through a POS: Magnetic Sale, EMV (Chip) Sale, Fallback Sale, Offline EMV Sale, Mail Order, and Ecommerce Sale, each explained in detail below.
Merchant & POS
To upload a version to a POS, the software on the POS and the authorization system on the bank side must support it. Version upload to a POS can be done manually on the device itself, or via a remote upload request.
Merchant & POS
Many transactions are carried out with cards on a POS terminal. Sometimes a transaction must be reversed, and cancellation (void) is one such transaction. A Sale can only be cancelled on the POS before the batch (end of day) is closed; otherwise a refund is needed.
Merchant & POS
Loading parameters onto a POS transfers changes made in the POS Management system (authorization, limits, card BIN list, etc.) onto the POS. There are 3 ways to do it.
Merchant & POS
A POS is a functional device with its own dedicated software, customized according to the authorization system of the bank it is connected to, that accepts credit or debit cards. So, banks abroad launch dozens of new card products every day…
Merchant & POS
To accept a card brand such as Mastercard or Visa, a POS must be certified for that brand. Which brands a POS accepts is the bank's decision.
Merchant & POS
In chip transactions made with a credit card via POS, the transaction amount is approved by the card and POS based on parameters on the card and POS, without going to the card bank or POS bank. These are called offline transactions.
Merchant & POS
A POS batch close triggers reconciliation between the transactions under that batch number and the bank's records, and starts the transfer to the merchant's account.
Merchant & POS
Transactions made via POS are kept under a number called the batch number, which increases automatically and arithmetically. This number increases after each end-of-day (batch close) process.
Merchant & POS
MPV stands for Merkezi POS Veritabanı (Central POS Database), BKM's shared database of all POS terminals operated by its card-accepting members, used for support, statistics, fraud analysis and the Common POS Management System.
Payment Systems
Why do institutions track inefficient POS terminals and lines? This post looks at the costs they create, such as device purchases, field service and software fees, and how to deal with merchants that generate little turnover.
Payment Systems
When POS and HOST transactions don't match at end-of-day, the end-of-day falls into batch upload. This article covers how the POS sends transactions via the 320 message, how HOST responds with 330, and how to monitor and resolve recurring batch upload failures.