Details Documentation Request Live Demo
Real Time or Near Real Time Log payments messages
Switch transactions and save to SQL, raw ISO8583 messages, flat files
Make real-time statistics, or just save data for later
Easily save transactions to CSV, import to Excel and create graphs
Transaction logging for testing phase and test reports. Analyse what has been tested!
Authorization messages logging for errors analysis. Check what your system is processing.
Payments logging for in-depth business analysis and reporting
Be informed before taking important management decisions
Have automatic statistics be available every week, month and year!
The ISO8583 Logger will listen to your connection, parse and log
ISO8583 messages so you can extract reports.
You can easily
then view you transactions in a text file, or import them from a CSV
file to Excel, so you can process them and extract reports.
With this kind of answers you can plan better, optimize your
configuration, use it to assess granulation for performance testing,
and many other things for business presentations and statistics.
no installation
unpack and run
platform independent
very simple User Interface
server mode with no-UI
move to local, test mode
high TPS, low impact
small footprint
all memory run
no database required
console output
log to files as any message
generate XML, HTML logs
superb HTML reports, graphs
version control configuration
several configuration streams possible
in-house business logic updates
no delivery dependency
files, any encoding, even binary
TCP , Web Services, HTTP
CSV files storage
databases
API, PSD2
XML, JSON, ISO8583, ISO20022, SWIFT, TLV, CSV, SQL in the box
fully configurable
crazy flexible: insert ISO8583 in XML
crazy powerful: send ISO8583 to file
crazy conversion: ISO8583-XML-SQL
EMV, PIN, MAC, in the box
several cryptogram methods
several PIN block methods
any encryption standard
On the felt side we have transactions coming in
The connection type is defined in .js files
Each connection is configurable independently
The script engine asks the connection to read data into a message
The connection reads information into a message
Message structures are defined independently from connections
Messages are also defined in .js files
The message is returned to the script engine
The script engine calls scripts to validate, alter information
Additional business logic can be applied via the scritps
We can then convert this information and create an output message
We take the way back and the script engine can send the new message to a connection
The connection will actually send the message out
All components work independently
Ready to start your next project with us? Give us a call or send us an email and we will get back to you as soon as possible!