surfingnero.blogg.se - Transaction history

#Transaction history how to#
#Transaction history plus#

(Using this source for time frames larger than 30 days can place significant stress on the Galileo system.)

Program API - Endpoint calls that can retrieve all transactions or specific types only.

Events API - Live transaction notifications that you can subscribe to, comprising three event message types.

When building your own transaction history, you will need to decide among these options: Your data store should be your primary resource for building customer statements and analyzing transaction data, as well as providing your customers with transaction histories that include more than the past 30 days.

Galileo strongly recommends that its clients maintain their own transaction histories instead of relying exclusively on Galileo data sources. To display a list of transactions that extends past the previous 30 days-or for statements and data analysis-Galileo recommends that you use a transaction history that you create on your own, as described in Building a transaction history.

To display a list of transactions on your mobile app or website for the past 30 days or less, Galileo recommends that you use the Program API, as explained in the next section.

#Transaction history how to#

Which data source to access for transaction histories depends on the use case and the time frame. This short tutorial will walk you through how to access, sort, print, search and export your transaction history and details in Online and Mobile banking.

Analyze transaction data for various purposes, such as spending categorization.

Send account holders a monthly statement, summarizing all transactions during that period.

Present to account holders their transaction histories on your app or website.

Before a party is closed out, the report shows how much the party has. You will need to access your account holders' transaction histories for reasons such as these: The Customer Transaction History report lists sales, customer payments, and refunds.

Card Transaction Scenarios - Detailed examples of card transactions as they appear in the Auth API, Events API, Program API, and RDFs.

Card Transaction Examples - Different types of card transactions as returned by the Program API.

#Transaction history plus#

About Card Transactions - An explanation of how card transactions work, plus what transaction sequences are produced by different types of card transactions.About Transactions - A general explanation of how transactions are handled by the Galileo system.Along with this guide you might want to read these guides: According to your business use case, you may follow the examples presented here or you can devise other strategies. This guide presents some of the options that you have for keeping transaction histories.