AEVI (https://www.aevi.com) works with merchant acquirers to provide merchants maximum flexibility with regards to payment devices, value added services and payment solutions.

AEVI does this via providing a Marketplace that allows acquirers and merchants to browse and install third party applications onto their payment devices that have been sourced from third party developers and are managed via AEVI's Device Management System. The acquirers typically build and provide one or multiple payment services/applications that go onto these devices to facilitate transaction processing.

This project describes the SDK that enables third party developers to build various types of applications that interact with merchants and customers at different stages of the point-of-sale flow. Note that we will be referring to this solution as AppFlow throughout this documentation, but to be precise we are referring to AppFlow POS Implementation, which is the POS/Payment domain implementation of AppFlow.

For those of you who have existing integrations with the AEVI Public SDK Simple Payment API to initiate payments on a device, please see Legacy API support for information on compatibility and migration.

Please continue with the Overview for more information.

Below are some terms and acronyms that will be used throughout the documentation.

• POS : Point of Sale
• Flow Service : An application that integrates with Payment Flow Service API and gets called from a flow
• VAA : Value Added Application (3rd party application) - one type of flow service
• VAS : Value Added Service (Essentially same as VAA)
• Payment App : Processes payments, typically via a bank host/gateway. A type of flow service
• DMS : Device Management Service
• SDK : Software Development Kit

Overview