Major Updates to Payments.iQ NG Functionality in Version 1.14

The BS/2 development team presents a new version of the platform for managing payment terminals and kiosks — Payments.iQ NG 1.14. This release focuses on improving operational efficiency, simplifying administration, and enhancing system security. New capabilities make working with payment infrastructure more transparent, manageable, and reliable. 

Unified Transaction Status Model

Problem Solved by This Update 

In previous versions of Payments.iQ NG, different system components used various transaction status designations. This created confusion during data analysis and complicated support: the same status could be displayed differently in transaction logs, reports, and logs. 

What Changed? 

Version 1.14 implements a unified status model (Unified Statuses) for all system components. 

Benefits of unification: 

Simplified analysis 

Transaction status is now displayed identically across all system sections: in transaction logs, reports, API, and exported data. 

Easier support 

Technical specialists can diagnose problems faster, as there’s no need to “translate” statuses from one designation system to another. 

Transparency for integrations 

External systems integrating with Payments.iQ NG via API receive predictable and consistent statuses. 

Standard statuses now include: 

• Completed — transaction completed successfully

• Failed — transaction completed with an error

• Pending — transaction in progress

• Waiting for Resolution — operator intervention required (new status)

• Retracted — operation cancelled (e.g., customer retrieved card)

• Timeout — response wait time exceeded

Enhanced Payment Retry Capabilities

Bulk Transaction Retry 

One of the most requested improvements in version 1.14 is the ability to retry payment for multiple transactions simultaneously. 

Use cases: 

Recovery after failure 

If the bank’s processing center was unavailable for a certain period and dozens of transactions failed with errors, the operator can select them all and initiate reprocessing with a single action. 

Maintenance work 

After scheduled maintenance on the payment gateway side, it may be necessary to retry all unsuccessful transactions for a period — now this can be done in a few clicks. 

Testing 

When debugging integrations, the ability to bulk retry significantly speeds up the testing process. 

Clarification of Retry Button Display Conditions 

The Retry Payment button is now displayed only for transactions that can actually be retried. The system automatically checks: 

• Whether the session has expired 

• Whether the device is in online status 

• Whether the transaction has already been successfully retried 

• Whether the transaction status meets retry conditions 

This eliminates situations where an operator attempts to retry a transaction that cannot be reprocessed. 

Transaction Log Improvements

Correct Display of Retract Operations 

What is Retract? 

Retract is a transaction cancellation operation when a customer retrieves their card before the operation completes or when the system cancels the transaction due to an error. 

Problem in previous versions: 

The Retract operation amount was not displayed in the Dispensed column, creating confusion during data analysis. 

Solution: 

Now during Retract operations, the amount is correctly displayed in the corresponding column, ensuring complete transparency of fund movement. 

New Status: Waiting for Resolution 

A special Waiting for Resolution status has been added to the transaction log for situations requiring operator intervention. 

When this status is applied: 

• Mismatch between dispensed and requested amount 

• Loss of connection with payment gateway at critical moment 

• Technical errors requiring manual verification 

• Suspicious transactions flagged by fraud monitoring system 

Benefits: 

Operators can easily find all problematic transactions using a filter for this status and process them with priority. 

Service Name Display 

The main transaction log table now displays the service name, simplifying analysis: 

Why is this needed? 

• Quick identification of operation type without needing to open transaction details 

• Convenient grouping and filtering by service types 

• Simplified analysis for business analysts

Log Export via Loki API

What is Loki? 

Loki is a modern logging system from the creators of Grafana, optimized for working with large volumes of logs. 

New Capability: Log Export via Admin Console 

Version 1.14 implements direct log export from Loki through the administrative console without the need to access Grafana. 

Functionality includes: 

Export parameter form 

• Time range selection 

• Filtering by devices 

• Log detail level selection 

• Export format (JSON, TXT, CSV) 

Download button 

With one click, all filtered logs are downloaded to a file. 

Retention policy configuration 

Administrators can define through the UI how long to keep logs: 

• Short-term logs (7-30 days) — for operational diagnostics 

• Long-term logs (up to 1 year) — for audit and investigations 

Retrieving Session Logs via Loki API 

A mechanism has been developed for retrieving logs of a specific session through the Loki API. 

Application: 

When an operator opens transaction details, the system automatically requests all related logs from Loki and displays them in a unified interface. There’s no longer a need to manually search for logs in Grafana — everything is available directly in the transaction log. 

Transferring Agent Logs to Server 

Transfer of PaymentsNG Agent logs to the server via technical agent has been implemented. 

How it works: 

• PaymentsNG Agent on the terminal collects logs locally 

• Technical agent periodically sends accumulated logs to the server 

• Logs are automatically indexed in Loki 

• Administrators get access to complete device operation history 

Benefits: 

• Centralized log storage even from devices in remote locations 

• Ability to analyze device behavior over the entire operation period 

• Log preservation even when reinstalling software on the terminal 

Removal of Legacy Error Logger 

As part of the migration to Loki/Grafana, the legacy Error Logger has been removed from the system, including: 

• Component code 

• Database tables 

• Access rights 

This simplifies the system architecture and reduces operational costs.

Grafana Alerts Integration

Proactive Monitoring 

Version 1.14 includes integration of Grafana alerts with the Payments.iQ NG notification service. 

What does this provide? 

Automatic problem notifications 

When Grafana detects an anomaly (e.g., sharp increase in errors on a specific device), the system automatically sends notifications to operators via: 

• Email 

• Telegram 

• SMS (when integration available) 

• Push notifications in mobile app 

Alert examples: 

• Transaction error threshold exceeded (>5% in the last hour) 

• Critical device unavailability for more than 15 minutes 

• Server disk space filling beyond 85% 

• Abnormal terminal activity (possible hack attempt) 

Configurable conditions 

Administrators can define: 

• Threshold values for various metrics 

• Who receives notifications depending on alert type 

• Alert activity times (e.g., critical — 24/7, informational — business hours only) 

Payments.iQ NG Agent Version Monitoring

PaymentsNG Agent Version Display 

The Pulse tab in the monitoring section now displays the PaymentsNG Agent version with commit hash indication. 

Why is this important? 

Update control 

Administrators can see which devices haven’t yet updated to the latest agent version. 

Problem diagnostics 

When contacting technical support, specifying the exact agent version (including commit hash) speeds up diagnostics — specialists immediately understand which fixes are already included and which aren’t. 

Migration planning 

Before rolling out a new version, you can assess how many devices require updates. 

Improved Polling Error Handling 

Terminal network polling error handling and exception logging have been improved. 

What changed: 

• More detailed logging of device unavailability causes 

• Differentiation of error types (network, timeout, protocol error) 

• Automatic retry polling with exponential backoff 

Result: fewer false alerts about device unavailability and more accurate diagnosis of real problems. 

Security and Notifications

User Logout Logging 

The Audit Trail now records user logout events. 

Why is this needed? 

Security compliance requirements 

Many standards (PCI DSS, ISO 27001) require complete logging of user actions, including system login and logout. 

Incident investigation 

When analyzing security incidents, it’s important to know when the user completed work with the system. 

Activity monitoring 

Administrators can track system usage patterns: who works outside business hours, how long sessions last, etc. 

Security Event Notifications 

Email and Telegram notifications have been implemented for security events. 

Examples of events generating notifications: 

• Multiple failed system login attempts 

• System access from new IP address 

• Critical security settings changes 

• Access attempt to functions without appropriate rights 

• Suspicious activity on terminals 

Configuration: 

Administrators define: 

• Which events are considered critical 

• Who receives notifications 

• Notification format (brief or detailed) 

Benefits: 

Rapid response to potential security threats — from detection to action can take minutes, not hours.

AI Assistant for Log Analysis

Intelligent Diagnostics 

One of the most innovative features of version 1.14 is the ability to connect an AI Assistant model for processing Payments.iQ NG logs. 

How does it work? 

AI Assistant analyzes system logs and: 

Automatically identifies problem patterns 

Instead of manually reviewing thousands of log lines, AI finds recurring errors and groups them by type. 

Suggests probable causes 

Based on analysis, AI can suggest what caused the problem: configuration error, network issue, banking system integration failure, etc. 

Recommends solutions 

AI suggests specific steps to resolve the problem based on a knowledge base of typical incidents. 

Application examples: 

Scenario 1: Mass transaction errors 

AI analyzes logs and determines: “All errors started after 14:32, affect only one payment gateway, error code indicates certificate problems. Recommend checking gateway SSL certificate validity.” 

Scenario 2: Specific device problems 

“Terminal #125 generates card reading errors in 30% of transactions. Error pattern indicates card reader contamination. Scheduled cleaning recommended.” 

Scenario 3: Performance 

“Transaction processing time increased by 40% over the last 3 days. AI detected increased database query delays. Index optimization or DB server scaling recommended.”

Device Identification Improvements

Cloned Device Handling 

A scenario for handling cloned devices — situations where multiple terminals have identical terminalId or H/W ID — has been developed. 

Why does this happen? 

• Incorrect system image cloning during mass deployment 

• Errors during new device configuration 

• Fraud attempts with terminal replacement 

How the system handles such cases: 

• Duplicate detection when device connects 

• Automatic assignment of temporary unique identifier 

• Administrator notification of the problem 

• Blocking duplicate device operation until conflict resolution 

Unique H/W ID Formation 

Unique Hardware ID formation based on network adapter MAC addresses has been implemented. 

Algorithm: 

• System reads MAC addresses of all device network interfaces 

• Forms hash based on MAC address combination 

• Uses this hash as part of unique H/W ID 

Benefits: 

• Practically impossible to get two devices with identical H/W ID 

• Identifier persists even after OS reinstallation 

• Ability to track device when IP address changes

UI/UX Improvements 

Scenario Display Improvement 

Work has been done to improve the display and localization of terminal operation scenarios. 

What changed: 

Human-readable names 

Instead of technical designations (SCENARIO_PAYMENT_01) — understandable names (“Utility Payment”). 

Scenario descriptions 

Each scenario now has a brief description explaining its purpose. 

Consistent display 

Scenario names are displayed identically across all system sections: in settings, reports, transaction log. 

Export Button in Logs Section 

An Export button has been added to the Logs tab for quick data download. 

Export formats: 

• CSV — for Excel analysis 

• JSON — for programmatic processing 

• TXT — for viewing in text editors 

Hardware Monitoring Filter Changes 

Filters in the hardware monitoring section have been changed from checkbox to combo (dropdown list with multiple selection). 

Benefits: 

• Takes less screen space 

• More convenient with many options 

• Selected filters preserved between sessions 

Terminal ID Sorting Limitation 

Table sorting by Terminal ID has been limited to improve readability. 

Reason for change: 

With a large number of devices (1000+), sorting by Terminal ID could lead to unpredictable results if identifiers contained both numbers and letters. 

Solution: 

Now Terminal ID is sorted by specific logic (e.g., first by region, then by number), making results more predictable and useful. 

Release Summary

Version 1.14 represents a mature enterprise release focused on: 

• Operational efficiency — bulk operations, improved transaction log 

• Transparency and observability — deep Loki/Grafana integration 

• Proactive monitoring — real-time alerts and notifications 

• Security — detailed audit, security event notifications 

• Innovation — AI Assistant for intelligent problem analysis 

• Ease of use — UI/UX improvements, localization

These improvements make Payments.iQ NG a powerful platform for managing distributed networks of payment terminals and self-service kiosks.
Want to Learn More About Payments.iQ NG Capabilities for Your Organization?
BS/2 specialists are ready to present the system and discuss how Payments.iQ NG can optimize your payment infrastructure management. Get a free consultation and capabilities demonstration!