Skip to main content
Prime Data is Treasury Prime’s data warehouse solution. All API activity is stored in a Snowflake database, enabling banks to analyze and audit platform accounts, transactions, and actions. Banks connect to Prime Data using their preferred data tools to create reports and extract insights from platform activity.

​
Setup Steps

To connect your bank to Treasury Prime’s Snowflake Prime Data v2 instance, there are two options available:
  1. Snowflake Direct Share (Recommended):
    • If your bank already uses Snowflake, this is the most efficient approach.
    • Treasury Prime will use the bank’s Snowflake account locator to create a data share through a Snowflake listing or direct share.
    • The bank will gain read-only access within its Snowflake instance to Prime Data tables.
    • This method requires no additional setup on the bank’s end and minimizes costs, as data replication is handled within Snowflake.
  2. Snowflake Reader Account:
    • If the bank does not use Snowflake, Treasury Prime can create a dedicated Snowflake Reader Account.
    • Treasury Prime will act as the administrator of this account.
    • Access can be set up using one of two secure connection methods:
      • SSH Key-Based Access (preferred): The most secure method. The bank provides a public SSH key, which Treasury Prime applies to the bank’s user account. IP allowlisting is also supported for additional security.
      • User/Password-Based Access (with optional IP allowlisting): A straightforward option but less secure.

​
Prime Data Details

The current instance of Prime Data is an updated iteration of Prime Data. Changes have been made to improve the usability as well as the coverage of the available data.
  • Combined payment files with extended account information to reduce the frequency of necessary joins.
  • Tables designed for consolidated data streams to partners for ledger transaction monitoring.
  • FDIC tables that make reporting account ownership and balances by TIN easier.

​
Data Tables

Table NameTable Description
accountContains account object (acct_) details.
account_lockContains details about locked accounts, a reason for the lock, current locked status (true/false) and time of release, if applicable.
account_productContains account product object (apt_) details.
account_tagsContains an association of account objects (acct_) and the tags on those account objects.
achContains ACH payment object (ach_) details.
ach_combinedAn extended view of ACH payment details that includes information about the associated counterparty and account.
additional_personContains details of additional person applications to existing accounts.
addressContains address objects (addr_) that are associated with other persons, businesses, etc.
applicationContains account application object (aact_) details.
application_companyAn association table between account application objects (aact_) and business application objects (abus_).
application_personAn association table between account application objects (aact_) and person application objects (apsn_), including their account roles applied for.
assoc_txn_backing_bookAn association table between transaction objects (ttx_) and backing on-core book transfers (book_).
auditAn event log of changes made through the API with their user attribution.
billpayContains bill pay payment objects (bpp_) details.
bookContains book transfer payment object (book_) details.
book_combinedAn extended view of book transfer details that includes information about the associated accounts and accountholders.
business_account_streamDesigned for ledger transaction monitoring, this contains an extended view of business ledger accounts (acct_). Intended to be used with the ledger_transaction_stream, personal_account_stream, secondary_persons_stream, card_stream, and card_event_stream tables.
cardContains details of issued card objects (card_).
card_event_streamDesigned for ledger transaction monitoring, this contains an extended view of all card network activity corresponding to card event objects (cnm_). Intended to be used with the ledger_transaction_stream, personal_account_stream, business_account_stream, secondary_persons_stream, and card_stream tables.
card_network_messageDetails of card event activity returned through the network.
card_streamDesigned for ledger transaction monitoring, this contains an extended view of all issued cards objects (card_). Intended to be used with the ledger_transaction_stream, personal_account_stream, business_account_stream, secondary_persons_stream, and card_event_stream tables.
card_transactionDetails of transactions created from card activity (card_tx).
card_tx_combinedAn extended view of card transaction details that includes information about the associated account and cardholder.
cardcontrolContains card control object (cctl_) details.
cardholderContains details about the person who is the cardholder of issued cards.
cardproductContains card product objects (cdpt_) details.
check_issuedContains issued check object (ch_) details.
check_issued_combinedAn extended view of issued check details that includes information about the associated account.
checksContains check deposit object (chk_) details.
checks_combinedAn extended view of check deposit details that includes information about the associated account.
commentContains details of comments on API objects, most commonly account applications.
companyContains business application object (abus_) details.
company_personAssociation table of person application objects (apsn_), their relationship to business application objects (abus_), and related account application objects (aact_).
counterpartyContains counterparty object (cp_) details.
deposit_sweep_accountContains information about ledger account enrollment in deposit sweeps (dsa_).
deposit_sweep_report_deltaContains information about the change in swept funds (dsd_) as a part of automated deposit sweeps.
documentContains document object (doc_) details.
document_companyAssociation table of document objects (doc_) with business application objects (abus_).
document_personAssociation table of document objects (doc_) with person application objects (apsn_).
incoming_achContains incoming ACH object (ina_) details.
incoming_ach_combinedAn extended view of incoming ACH details that includes information about the associated account.
incoming_wireContains incoming wire object (inw_) details.
incoming_wire_combinedAn extended view of incoming wire details that includes information about the associated account.
ledger_accountContains Treasury Prime ledger account object (tacct_) details.
ledger_achContains ACH payment object (ach_) details specifically related to ledger account objects (tacct_).
ledger_ach_combinedAn extended view of ledger ACH details that includes information about the associated account.
ledger_businessContains business object (com_) details, specifically for those that relate to ledger account objects (tacct_).
ledger_personContains person object (com_) details, specifically for those that relate to ledger account objects (tacct_).
ledger_transactionContains a record of all immutable transaction objects (ttx_) on ledger accounts.
ledger_transaction_combinedAn extended view of ledger transaction details that includes information about the associated ledger account.
ledger_transaction_streamDesigned for ledger transaction monitoring, this contains an extended view of all ledger transactions (ttx_). Intended to be used with the personal_account_stream, business_account_stream, secondary_persons_stream, card_stream, and card_event_stream tables.
ledger_wireContains wire payment object (wire_) details specifically related to ledger account objects (tacct_).
ledger_wire_combinedAn extended view of ledger wire details that includes information about the associated account.
network_transferContains network transfer object (nt_) details. Note: this table is populated only for banks that use the network transfer feature.
network_transfer_businessContains business object (com_) details for businesses related to network transfer payments. Note: this table is populated only for banks that use the network transfer feature.
network_transfer_personContains person object (psn_) details for persons related to network transfer payments. Note: this table is populated only for banks that use the network transfer feature.
network_transfer_wiresContains wire object (wire_) details for balancing wires that move money as part of network transfer settlement. Note: this table is populated only for banks that use the network transfer feature.
network_transfer_wires_combinedAn extended view of network transfer balancing wire details that includes information about the associated account. Note: this table is populated only for banks that use the network transfer feature.
personContains person object (psn_) details.
personal_account_streamDesigned for ledger transaction monitoring, this contains an extended view of personal ledger accounts (acct_). Intended to be used with the ledger_transaction_stream, business_account_stream, secondary_persons_stream, card_stream, and card_event_stream tables.
progressContains events that log the progress of the account opening process for account applications.
reserveContains details of automatic reserve enrollment for accounts.
secondary_persons_streamDesigned for ledger transaction monitoring, this contains all non-owner person objects (psn_) associated with ledger accounts. Intended to be used with the ledger_transaction_stream, personal_account_stream, business_account_stream, card_stream, and card_event_stream tables.
tax_documentContains tax document object (taxdoc_) details, such as 1099s.
usersContains all users and their permissions of Treasury Prime frontend tools and for API keys.
wireContains wire payment object (wire_) details.
wire_combinedAn extended view of wire payment details that includes information about the associated counterparty and account.

​
FAQs

​
What if I have issues connecting to Prime Data?

First, check that your IP is whitelisted. Then, double-check your SSL encryption policy & firewall settings. If you are still experiencing issues, contact Treasury Prime support.

​
What reporting tool do you recommend?

Any business intelligence or reporting tool that can support live database connections can connect with Prime Data (Tableau, Looker, Looker Power BI, etc.). Treasury Prime does not have preferred tooling — you should choose whatever tool is best for the needs of your team. Treasury Prime does, however, offer a prebuilt reporting tool called Prime Analytics. It comes with useful out-of-the-box reporting for Embedded Finance activity along with Excel-like functionality to modify and create your own custom reports. It supports scheduling reports to send to your inbox in whichever format (PDF, Excel, csv) you’d like.

​
What can I do with Prime Data?

Create reports/analysis useful for your banking business needs, such as compliance, reconciliations, and troubleshooting payment transactions. Example reports may include:
  • ACH Return Rate
    • KYC Evaluation
      • Reconciliation
        • FDIC insurance reporting

​
Do Prime Data access credentials ever expire?

No, user credentials never expire.

​
How long is data retained within Prime Data?

Data does not expire and will be retained in Prime Data forever unless the bank requests otherwise.

​
How far back in time does Prime Data go?

As far back as the bank has been implemented with Treasury Prime.

​
What if I don’t see some data that I should be seeing?

Submit a support ticket to help@treasuryprime.com and give as many details as possible to facilitate a faster resolution.

​
Is Prime Data a web application that can be connected to over https?

No, Prime Data is not a web application but rather a database to be connected to by a database client or data analytics tool over SSL/TLS.

​
Does Treasury Prime have a schema map of the tables within Prime Data?

We currently do not have a full schema map available but are working on providing one for our Prime Data clients. You can see descriptions of each available table above.

​
Can a bank request that additional Treasury Prime data be added to Prime Data?

We strive to provide full coverage of data relevant to your bank, and we always welcome suggestions on how we can make Prime Data better or more complete. To facilitate bringing in additional fields or tables into Prime Data, please provide specifics on the data and the business case around why it’s useful for you to have in Prime Data.

​
Can I upload my own data to Prime Data?

No, it is not possible for banks to upload data directly to Prime Data today. However, any updates made to objects through the API will be reflected in Prime Data. Banks can import the data from Prime Data into its own data warehouse to link together with other data sources, however.