Author
Guest author
Writes on payment systems and POS operations.
22 articles
Payment Systems
A shared POS is a bank or institution terminal that can host more than one application. This post covers the software, APN and authorization steps, and the key test scenarios to cover in a shared POS project.
Payment Systems
Offline transaction parameters are divided into two types: contact offline and contactless offline. These parameters can be managed separately through Terminal data and Chip data. Offline transactions can be reported to the HOST after an online transaction, after X occurrences, and more.
Merchant & POS
The most important part of issuer data definitions is that they are built around your own bank's or institution's developments and application flows. Missing BINs can break installments, rewards and routing on POS devices.
Merchant & POS
When POS devices given to merchants are replaced or taken back, they must be returned in working order. A device that cannot be repaired, or only at high cost, is classified as a scrap POS.
Merchant & POS
No. Besides the terminal data, contactless limits can also be managed from the chip data. A “Use Merchant Contactless Limits” field decides which set of limits the POS applies.
Payment Systems
Regularly reporting and tracking how many transactions fail at each merchant matters for both the merchant and the acquirer. BKM error codes tell us why POS transactions fail.
Payment Systems
A Lost POS is a situation in which a POS device provided to a merchant by a bank or institution cannot be retrieved for any reason. Since POS devices are recorded as fixed assets, tracking them closely is essential.
Payment Systems
No. Besides the POS and the host, permissions can also be kept in the issuer data. This lets banks, for example, allow installments only for a brand's BINs, or allow mail order for credit cards but not debit cards.
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.
Merchant & POS
Merchants can run the end-of-day process by triggering it from the POS device or app for transactions made there. Banks can also run it centrally on merchants' behalf. The end-of-day process sends the POS's transaction totals to the bank's host system.