Search
6 articles found
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
When a transaction is made through a POS, it is recorded both on the POS itself and in the acquiring bank's authorization system. At batch close, the POS sends all its transactions to the bank, which reconciles them against its own records.
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.
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
The batch number is kept on the POS, incremented by 1 at each end of day, used to transfer transactions to the merchant account and for reconciliation. It's tracked on both the POS and the bank's system.
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.