Developer environment
Overview
Nexi provides two environments, the production and the sandbox.
Depending on the integrations analyzed in the following sections, the resources shared in test are the App, SDK and BE Endopoint fo the authentications if foreseen.
To have access to these resources in the sandbox environment, please refer to the sales team.
Below you will find the requirements for developer test environment.
SoftPOS requirements:
- Device equipped with NFC
- Android operating system >= 9
- No developer mode enabled
- No camera or recording screen app enabled during the payment
- Others App using NFC may affect the usage of the SoftPOS
- Nexi POS application installed both from Google Play Store and Huawei Gallery (according to the smartphone O.S.)
- User app credential and TID (only for User-Authentication mode)
- WebPortal access as Developer (only for cloud authentication)
MobilePOS requirements:
- Nexi POS application installed from Apple App Store, Google Play Store and Huawei Gallery (according to the smartphone O.S.)
- User app credential and TID (only for User-Authentication mode)
- Configured mPOS
Nexi POS App performs a security check of Device (i.e. device Developer Mode must be disabled, Version of the Operating systems, NFC and Bluetooth compatibility). If any of this check is not OK, the execution is stopped.
Do you get stuck with the integration?
Refer to the following GitHub space to download integrations example
- User Authentication: https://github.com/NexiPayments/softpos-android-app-standalone
- Cloud Authentication: https://github.com/NexiPayments/softpos-android-app
TermID: numerical identifier for a specific POS. A Merchant can request one or more POS. Each POS has a different TermID.
Store: a logical entity that generically corresponds to a physical store and is used to group multiple TermID from the same merchant. Each termID can belong to only one store.