Payments (Littlepay): Consider ingesting `terminal device transactions`

[lauriemerrell]

As a Payments data user, I may want to analyze denied device transactions to better understand the entire Payments life cycle.

Littlepay has produced three different files related to device transactions:

• device transactions: this contains approved device transactions only. We currently bring this data into the warehouse for all agencies and this is the source for our device transactions data.
• denied device transactions: until 11/28/23, we received this file for some agencies. This contained only denied device transactions. We have never brought this data into the warehouse.
• terminal device transactions: until 11/28/23, we received this file for some agencies. Starting on 11/28/23, we receive it for all agencies. This contains both denied and approved device transactions. We have never brought this data into the warehouse.

We need to consider: Do we want to use terminal device transactions instead of device transactions? Or perhaps ingest it separately so that the denied transactions are at least available in the warehouse?

AC:

• [ ] Make a decision about whether we want to ingest terminal device transactions
• [ ] If yes, make a new ticket to document that work. Bringing this data into the warehouse would require updating the Littlepay data parsing job to include this table and the creation of a new external table, as well as any downstream dbt modeling updates to make the data available in the warehouse.