Accounts and Transactions
What is this use case?
In this use case, an Account represents a user’s financial account (including types such as Checking, Savings, Loans, and more).
Accounts have a Balance, which represents the current value of the account.
Accounts may have one or more Transaction records, which represent funds that have moved in or out of the financial account.
How have others used it?
Accounts, Balances, and Transactions are commonly useful for a variety of uses:
- Determining availability of funds
- Money movement
- PFM (Personal Financial Management)
- Wealth Management
How do I use it?
You may have multiple options to retrieve accounts, balances, and transactions, depending upon which Jack Henry products and services are being used at your financial institution.
These are your likely options:
- Banno
- jXchange
- SymXchange
Banno Digital Toolkit
If your institution has the Banno digital banking platform, then you might want to use the Banno Digital Toolkit.
The Consumer API, from the Digital Toolkit, is how you can access user data using the same API that powers Banno’s own Banno Online and Banno Mobile experiences.
Banno works with these core platforms offered by Jack Henry, which means the Consumer API also works with these core platforms:
Banking Core Platforms
- SilverLake
- CIF 20/20
- Core Director
Credit Union Core Platform
- Symitar
Keep in mind that the Consumer API–because it’s the same API used by Banno Online and Banno Mobile–has the same capabilities as the Banno Online and Banno Mobile apps.
This has the advantage that, if a user can ‘see it in Banno’, then it should work the same way with the Consumer API.
That’s how the major data aggregators are able to connect an account holder’s favorite fintech apps to their financial accounts at your institution.
However, Banno’s APIs should not be confused with a general way to connect to the core itself. For that kind of capability, you’ll need to look at either jXchange or SymXchange as potential options.
Example: accounts of the same type
Let’s say your solution requires you to differentiate between two different accounts, of the same type: a Checking account and a different Checking account.
The Consumer API is an ideal way to make that kind of determination, as Banno knows the accountId, balance, masked account numbers, and potentially an unmasked account number, for a given account.
Example: accounts of different types
Let’s say your solution requires you to differentiate between two different accounts, of different types: a Checking account and a Savings account.
The Consumer API is an ideal way to make that kind of determination, as Banno knows the accountType and accountSubType for a given account.
Example: accounts of the same type, different financial products
Let’s say your solution requires you to differentiate between two different accounts, of the same type: a ‘Super Duper Premium’ Checking account and a ‘Basic No-frills’ Checking account.
The Consumer is not ideal for this example, since Banno does not know that level of detail about the financial product offering from the financial institution.
If you need that level of detail about the financial products themselves (in this case, the ‘Super Duper Premium’ Checking account and the ‘Basic No-frills’ Checking account), then you need to go deeper into the tech stack with one of these two options:
- jXchange
- SymXchange
Example: transactions
Let’s say your solution requires you to retrieve the user’s transactions.
The Consumer API is an ideal way to retrieve transactions, and it supports both date filtering as well as pagination of transactions history.
jXchange
If your financial institution is a bank, then you might want to use jXchange.
jXchange connects to the core for these core platforms offered by Jack Henry:
Banking Core Platforms
- SilverLake
- CIF 20/20
- Core Director
jXchange offers both a Enterprise REST API and a Enterprise SOAP API for general connectivity to the core.
Example: accounts of the same type, different financial products
Let’s say your solution requires you to differentiate between two different accounts, of the same type: a ‘Super Duper Premium’ Checking account and a ‘Basic No-frills’ Checking account.
jXchange is ideal for this example, since it can access the core for that level of detail about the financial product offering from the financial institution.
Example: transactions
Let’s say your solution requires you to retrieve transactions from the core.
jXchange is an ideal way to retrieve transactions, and it can retrieve many detailed fields from the core itself.
SymXchange
If your financial institution is a credit union, then you might want to use SymXchange.
SymXchange connects to the core for these core platforms offered by Jack Henry:
Credit Union Core Platform
- Symitar
Example: accounts of the same type, different financial products
Let’s say your solution requires you to differentiate between two different accounts, of the same type: a ‘Super Duper Premium’ Checking account and a ‘Basic No-frills’ Checking account.
SymXchange is ideal for this example, since it can access the core for that level of detail about the financial product offering from the financial institution.
Example: transactions
Let’s say your solution requires you to retrieve transactions from the core.
SymXchange is an ideal way to retrieve transactions, and it can retrieve many detailed fields from the core itself.
Next steps
Read the developer docs for the API which makes the most sense for your solution: