Configuration
The A920 supports a range of configuration options that affect connectivity, payment experience, receipt printing, and enabled features.
Need help?
Our team is here to support you. If you are unsure about any configuration step, please contact Nexi support.
Quick Links
Depending on the merchant setup, configuration tasks may be performed directly on the terminal, during onboarding, or with the support of Nexi or a service partner. Some settings are intended for everyday use, while others should only be changed with guidance from support.
Typical configuration areas include Wi-Fi and connectivity, mobile network usage, language and display settings, keypad and sound preferences, receipt and printer behavior, tip configuration, QR-based payment activation, and terminal initialization or refresh.
Wi-Fi Setup
The A920 can be connected to a Wi-Fi network directly from the terminal.
To connect the terminal:
- Open the Wi-Fi or connectivity settings from the terminal menu
- Select the desired network (SSID)
- Enter the network password
- Confirm the connection
Once connected, the terminal displays the active network information, such as:
- SSID
- IP address
- subnet mask
- gateway
If DHCP is used, the assigned IP address can be checked again afterwards in the terminal network settings.
Advanced Network Settings
Some environments may require additional configuration, such as:
- DHCP
- static IP
These settings should only be changed if required by the merchant environment or under guidance from support.
Mobile Network
The A920 can use mobile connectivity depending on the SIM configuration.
In most cases, no manual setup is required. If mobile connectivity is not working as expected, Nexi support should be contacted.
QR-Based Payments
QR-based payment methods such as TWINT require activation and configuration.
QR payment methods must be enabled
QR options only appear once the corresponding payment method has been activated for the merchant.
Once enabled, the payment flow may change:
- a QR code may be displayed automatically
- a QR option may appear during payment
- a payment method selection screen may be shown
The exact behavior depends on the terminal configuration and enabled services.
Tips
Tipping behavior can be configured on the A920. Because tipping directly affects the customer experience, it should be configured in line with the merchant's business model.
Available options may include:
- no tipping
- predefined tip percentages (e.g. 5%, 15%, 20%)
- manual tip entry
- combined mode (predefined + manual)
Tip settings are typically configured at terminal or merchant profile level, depending on the setup.
Receipt and Printer Settings
The A920 has an integrated printer. Receipt configuration may affect when paper receipts are printed and whether digital receipt options are offered.
Available receipt and printer options may include:
- merchant receipt printing
- customer receipt printing
- digital customer receipt options
- QR receipt display
- automatic customer receipt printing when no option is selected
Printer-related settings should be configured according to the merchant's operational needs. The terminal should also be kept supplied with suitable receipt paper for normal operation.
Language and Device Preferences
The A920 provides access to local device settings such as:
- terminal language
- display brightness and behavior
- keypad tones
- standby settings
These settings help align the terminal with the merchant's operational preferences.
Initialization and Configuration Refresh
The terminal may support operational actions such as:
- initialization
- configuration refresh
- profile updates
These actions are typically required when:
- the terminal configuration has changed
- a payment method has been added
- a profile needs to be synchronized
- support has requested a refresh
In practice, initialization is mainly used to establish or restore the terminal setup, while configuration refresh pulls the latest merchant, payment method, and device settings already assigned to the terminal.
Because these functions can affect terminal behavior, they should only be performed when required.