Receipt Data - AEVI-AppFlow/pos-android-sdk GitHub Wiki

Applications may want to add data to a receipt during a flow process. This is particularly important for payment applications that may have very specific requirements for the data they are required to show on a receipt.

A typical example of the types of data shown on a receipt for a sale flow is shown in the diagram below.

The actual content and data shown on a receipt is ultimately likely to be defined by an acquirer/bank distributing the AEVI enabled device and is likely to vary from one flow type to another. The development of a receipt printing application can therefore be highly complicated. See this page here for details on some of the considerations for building a receipt printing application

The header and footer shown in the diagram above is usually merchant specific and therefore often under the control of the merchant via some configuration interface. This data may or may not include a logo or logos to be shown on the receipt. Usually the data will consist of address and contact details for the merchant.