---

End-of-Day link

As an Integrator, it is necessary to ensure that the integration includes a way to manage Captures at the end of each day. This is an essential step in processing the transactions performed throughout the day and prevent discrepancies between the ECR and the Terminal.

How does it work? link

When a capture is called, the terminal will gather up all the transactions performed during the day. This includes all sales, refunds, reversals and any other transaction types that were conducted. These transactions are bundled up into a batch and sent to the backend The terminal responds with a result and card totals divided into different groups.

Once a day all captured transactions are sent for clearing and settlement, this means that if you don’t perform regular captures the merchants payments might be delayed.

The terminal will require a Capture if it has been more than 24 hours since the ongoing session was opened. A session is only opened when the first transaction is made, so if the merchant is closed over the weekend you do not need make a capture.

Implementation link

It is common practice to either hook the Capture to when the merchant performs an end-of-day in the ECR so that the process is semi-automatic, or schedule it to be automatic for a time when the merchant is closed for the day.

It is our experience that this is a big pain point for merchants when it’s a manual process.

The integration should handle the response from the terminal that includes information such as:

• The total number of transactions
• What card schemes that has been used
• The overall sales amount that has been processed by the ECR during the day.

All of this information is included in the receipt object from the Capture response.

It is important to validate the received response to ensure that it aligns with the transaction records. Any discrepancies or irregularities should be addressed and investigated to make sure everything is working as intended.

Differences between terminal platforms link

The Tetra generation of terminals using API v1 will require a capture every 24 hours after opening of a session. The Axium generation of terminals using API v2 does not have this requirement, however performing regular captures is still recommended to avoid bookkeeping discrepancies from transactions flowing into next days sales.