Skip to main content

GetAccountTransactionHistory

GetAccountTransactionHistory(GetAccountTransactionHistoryRequest)​

Required? No

Overview: GetAccountTransactionHistory method is used to retrieve the transaction history of the End-User based on the Account Holder Number passed within the StartSession method. To pull images for specific deposits, a subsequent request is used (see GetAccountTransactionCheckImage)

If a Financial Institution (FI) has multiple products with Ensenta and the Account Holder Number is the same across the products, the FI may optionally have had Ensenta enable shared history across products. While this mobile integration is only for supporting a single check per transaction, it is recommended that you build out your UI to support displaying transactions that contain multiple checks.

History can be called any time after StartSession. It is important to note that for credit unions leveraging the Shared Branching network, each StartSession from Ensenta requires a call out to the Shared Branching network for a member inquiry. The credit union is charged a fee for every single member inquiry. For these credit unions, the mobile application should only call history when the End-User intentionally selects the deposit history menu (if offered). Some mobile applications display Ensenta’s deposit history when the End-User immediately accesses the deposit menu, which is acceptable for banks and credit unions not on the Shared Branching network.

While there is an API call that will allows a mobile application to call for data and images in the same method, this is not available to mobile partners at this time due to performance reasons. The mobile application must first call for deposit data, then call for the images only when the End-User selects a check. See supported sequence History

Sequence Requirements: The GetAccountTransactionHistory request may be sent anypoint after the StartSession step

Attention: GetAccountTransactionHistory should** only** be used within the normal Mobile RDC portion of your mobile app for users actively using Mobile RDC. If your app has a history screen that bundles history across third-party vendors, history from Ensenta should be excluded and instead rely on the history pulled directly from the core. Depending on specific functionality that the Financial Institution is leveraging with Ensenta, each StartSession request may initiate a process with a third-party vendor that invokes a fee to the Financial Institution. Failure to follow these details could result in thousands of dollars being charged to the Financial Institution by the third-party vendor(s).

note

Do not send fields as Null. All fields must be passed with a value or empty. Use basicHttpBinding, and don’t use message security, but only transport level security (SSL).

Parameters

TYPENAMEDESCRIPTION
GetAccountTransactionHistoryRequestrequest

Returns

TYPEDESCRIPTION
GetAccountTransactionHistoryResponse