Exporting transaction logs

The 20 most recent transactions are visible from within the transaction panel of the admin.

We'll soon be adding a means to export full transaction spreadsheets from within the admin, though in the meantime you may use scripts on the server to email these to you.

Note: Some email services may reject these as spam before they reach your inbox. In these cases, you may download logs directly from the server.

Installing the log scripts

You may download and install the log scripts with the following command:

curl https://raw.githubusercontent.com/naconner/lamascripts/master/logs/download.sh | bash

You'll only need to run this once.

Exporting logs

In your server, run the command for the log you wish to export, followed by your email address.

If it's the command for an encrypted log, you'll need to import a PGP key and use the email address associated with your PGP key. (See the importing section below.)

• cash-in-log – All cash-in transactions. Encrypted.
• cash-out-log – All cash-out transactions (if a two-way machine). Encrypted.
• cash-out-actions – All cash-out dispense and refill events. Encrypted.
• bills-log – Each individual bill inserted and their denomination. Encrypted.
• customers-log – Table of customers and their scanned ID information. Encrypted.
• cash-in-unencrypted
• cash-out-unencrypted
• out-actions-unencrypted
• bills-log-unencrypted
• send-server-log - Emails lamassu-server logs for research. Unencrypted.

If the email doesn't appear, check your spam folder. Some email services may block such emails entirely, so if not in spam, try an email address with a different provider.

Importing a PGP key

This is optional, though will allow you to export spreadsheets so that they are encrypted in transit, and thus not expose you or your customers' data.

Instructions for creating a PGP keypair and uploading to a public keyserver:

– Linux
– Mac
– Windows (creating, uploading)

Once uploaded to a keyserver, import your key to your Lamassu server by running:

gpg --search-keys --keyserver <keyserver> <key ID or email address>