Nautilus is the back-office for ATS service. While processing live transactions it is used to help monitor wallet’s performance and for in-depth investigation of transaction data. During development phase it is also used as transaction simulator and engine for test execution.

Near real-time transaction data and basic reports

Nautilus is receiving all the data that goes through ATS system (although with tiny, sub-second delay), so it is very useful tool to investigate wallet behavior in near real-time. It provides you with basic wallet health reports, such us, for example, wallet’s speed, ATS system speed, or most frequent rejection codes, and with more business-oriented reports such as volume of interchange fees processed, number of cards active on daily (or hourly) level and volume of transactions settled or authorized.

You can see many details about each transaction processed, including full communication history (what was sent to wallet, what wallet replied), detailed timing data (how much time was spent within ATS, how much time wallet took etc.), to which other transactions it is connected and many more.

Test environment

Using Nautilus you can run wallet in test mode, without need for real cards or real money. Nautilus allows you to perform all types of tests, including those that are, strictly speaking, in violation of card processing rules, but still happen in real life. Using this feature, you can even fully demo your product – Nautilus simply acts as external source of transaction data, same way real shop would act if in live mode.

Real time transaction data browsing and reporting

Nautilus provides some very basic reports about the wallet and business performance. Wallet health reports show authorization processing time, authorization and message processing performance, and most popular transaction rejection reasons. Normally, in production, your wallet should have few percents of rejected authorizations and zero percents of unprocessed messages. Authorization processing time should be under the time slice required by your payment processor (ATS on its own reduces response time to payment processor for transactions which do not need wallet approval).

Transactions which are not successfully processed on wallet side can be seen as highlighted in transaction list. In case they are “significant” like approved advice, reversals or settlements you should manually resend them to wallet (there is button resend transaction on transaction details page in Nautilus). The transaction details page also provides you with full details of what was sent to the wallet, what wallet’s reply was, and raw data as received from the payment processor.

Transaction simulator

With Nautilus you can create virtual banks, shops, online stores and fuel dispensers, and you can simulate card transactions on any of these virtual places. Each place can be configured to accept different currency, to utilize different security parameters and so on.

For each of virtual places created you can choose if you want to send regular authorization-settlement pair, or if you want to test some more exotic scenario (such as, for example, settlement without an authorization). This helps you test your wallet in conditions which are as close to reality as possible.

Test engine

Transaction simulator is convenient when developing functionality, but once you believe you finished development it is good idea to create automated test, which you can easily invoke, and which triggers big set of transactions that you expect to go through. Nautilus allows you to do that through creation of test cases and tests – this way with one click you can send many transactions to the wallet, and you can monitor wallet’s responses and performance.