3.26 View Statement Details by Card Number (V2) – Function 070

View Statement Details by Card Number (V2) – Function 070

Function 070, View Statement Details by a PAN or ALT ID, gives you a summary or history of transactions over a given period. All transactions that occurred to that card number between the start and the end dates are returned. The results are returned using XML for this API call.

The biggest difference between function 070 and 010 is the effect of the currency format display. Function 010 defaults to two decimal places on the implied decimal value when returning. Function 070 takes the currency into account and displays the appropriate value for implied decimal conversions. Currencies with 3 decimal places and 0 decimal places will now return correctly formatted in regard to the cardholders currency.

By default, function 070 will suppress authorization transactions when there is a matching settlement.

Inputs	Description	Required	Data Type
FunctionID	070	Y
P1	PAN OR ALT ID	Y	(16,19) numeric
P2	Start Date	Y	date (i.e., 01/01/2001)
P3	End Date	Y	date (i.e., 01/01/2001)
P4	GMT	N	alpha (Z, T, Y)
P5	First Row	N	numeric (starting index of result set)
P6	Last Row	N	numeric (ending index of result set)
ViewAll=Y	Returns all transactions	N
ViewAll=N	Returns only settled transactions	N
Outputs	Description
XML	The data will be passed back in a well-formed XML document. The error code processing will be contained in the P1 node that contains two attributes errnumber and errdescription. Therefore, if the errnumber attribute is equal to “000” the document will contain a “cardholderstatementdetails” node; otherwise, it will not.

Response XML:

Element Name	Description
Date	Date/time of the transaction.
CardNumber	Card number associated with the transaction.
TransactionType	Transaction type code.
MTI	Message type identifier.
STN	System Trace Audit Number.
TermID	Unique identifier of the of a card acceptor terminal.
AuthNum	Authorization identification number.
RecType	Record Type. Private use field which varies by network.
TransactionOrigin	Identifies if this transaction comes from an ATM (‘A’) or POS (‘P’)
Description	A short description of what kind of transaction this is.
Amount	Implied decimal amount of the transaction.
fee	Implied decimal amount of any fee charged for this transaction.
atmfee	Fee applied to the cardholder by the ATM in an implied decimal amount.
availablebalance	Available balance on the card after the transaction was processed.
ledgerbalance	Ledger balance on the card after the transaction was processed.
clientid	Client ID.
termnamelocation	Location of the terminal.
termowner	Owner of the terminal.
termcity	City of the terminal.
termstate	State of the terminal.
termcountry	Country of the terminal.
mcc	Merchant category code of the transaction.
surcharge	Surcharge applied in the cardholder billing currency in an implied decimal amount.
rspcode	Response code. See section 10.2 for a detailed list of response codes.
processor	Identifies which system processed the transaction.
issuerfee	Issuer fee.
origtransamt	Local currency amount.
convrrate	Currency conversion rate used if this transaction required a currency conversion.
termcurrency	Terminal currency.
currency	Cardholder currency.
origholdamt	Original holding amount.
acqinst	Acquiring Institution Identification Code.
cardacceptoridcode	Identifying code of the card acceptor.
ancillaryfee	Contains the ancillary fee code and fee amount of non-ticket releated service charges applicable in the passenger transport industry.
cbconrateinf	Contains the ECB Foreign Exchange reference rates and the percentage difference in comparison to the MasterCard foreign exchange rate.
termzip	Identifying the postal code of the terminal.
termurl	Identifying the website of the terminal.
termphonetaxidpartnerid	Identifying additional information of the terminal. NOTE: When an element is not present the column will have a gap, such as: data1\|\|data3\|data4\|data5
servicelocation	Identifying service location of the terminal. NOTE: When an element is not present the column will have a gap, such as: data1\|data2\|\|data3\|data4

Example: Statement Details Request by PAN OR ALT ID by

https://api.m2fin.com:8443/AuthENGINAPI/AuthENGINAPI?CID=5&CUSR=myuseraccount&CPWD=passwor
dassignedtome&FUNC=070&MSGID=00001646767884116&P1= PAN OR
ALTID&P2=03/01/2004&P3=06/07/2004&P4=0

Example: Statement Details Response by PAN OR ALT ID

<cardholderstatementdetails

RecCnt=”360″>

<date>05/02/2008 11:42:27 AM</date>
<CardNumber>################</CardNumber>
<TransactionType>270J</TransactionType>
<MTI>0100</MTI>
<ARN>134227240000</ARN>
<STN>1342272400</STN>
<TermID />
<AuthNum>134227</AuthNum>
<RecType>2401</RecType>
<TransactionOrigin>P</TransactionOrigin>
<description>Deposit funds</description>
<amount>000002000</amount>
<fee>00000</fee>
<availablebalance>0000065080</availablebalan
ce>
<ledgerbalance>0000065080</ledgerbalance>
<clientid>GKBL</clientid>
<termnamelocation>00000</termnamelocation>
<termowner />
<termcity />
<termstate />
<termcountry />
<mcc/>**
<surcharge>00000</surcharge>

<processor>BINCLIENT</processor>**
<issuerfee>000000000</issuerfee>
<origtransamt>000002934</origtransamt>
<convrrate>1.000000</convrrate>
<termcurrency>978</termcurrency>
<currency>978</currency>
<origholdamt>000000000</origholdamt>
<acqinst>00000000000</acqinst>
<cardacceptoridcode>273141000156182</cardaccep
tor idcode>**

</transaction>
</transactionlist>

</cardaccount>
<cardaccount>

<date>05/02/2008 11:49:22 AM</date>
<CardNumber>################</CardNumber>
<TransactionType>27J</TransactionType>
<MTI>0100</MTI>
<ARN>134922788000</ARN>
<STN>1349227880</STN>
<TermID />
<AuthNum>134922</AuthNum>
< RecType>7801</RecType>
<TransactionOrigin>P</TransactionOrigin>
<description>Deposit funds</description>
<amount>000002000</amount>
<fee>00000</fee>
<availablebalance>0000067080</availablebala
nce>
<ledgerbalance>0000067080</ledgerbalance>
<clientid>GKBL</clientid>
<termnamelocation>00000</termnamelocation>
<termowner />
<termcity />
<termstate />
<termcountry />
<mcc/>
<surcharge>00000</surcharge>
<rspcode>001</rspcode>
<processor>BINCLIENT</processor>
<issuerfee>000000000</issuerfee>
<origtransamt>000002934</origtransamt>
<convrrate>1.000000</convrrate>
<termcurrency>978</termcurrency>
<currency>978</currency>
<origholdamt>000000000</origholdamt>
<acqinst>00000000000</acqinst>
<cardacceptoridcode>273141000156182</cardacce
ptor idcode>

</transaction>
</transactionlist>

</cardaccount>

</cardpan>

</cardholderstatementdetails>

</api>

Interpreting transaction history and details responses data:
1. The first two numeric’s in the transaction type identify the transaction (see below)
2. The ‘transaction origin’ identifies if the transaction is a “P”OS transaction, or “A”TM transaction Ifthe transaction type starts with a 15 it is a debit, if it starts with a 27 it is a credit.