Issue with Transaction Details API (settledBatchListResponse)

[afail]

I am seeing an issue with pulling transaction detail api data from all of our sandbox accounts. The issue seems to affect only transactions captured on or after 9/1/15.

The XML response data I am receiving using the PHP SDK has strange numberical values. Please see the attached log file for more information. The first few transactions are from August and working correctly, but the September transactions are returning an odd response.

Batches before 9/1:

<?xml version="1.0" encoding="UTF-8"?>
<getSettledBatchListResponse xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<messages>
<resultCode>Ok</resultCode>
<message>
<code>I00001</code>
<text>Successful.</text>
</message>
</messages>
<batchList>
<batch>
<batchId>4602487</batchId>
<settlementTimeUTC>2015-09-01T01:34:40Z</settlementTimeUTC>
<settlementTimeLocal>2015-08-31T18:34:40</settlementTimeLocal>
<settlementState>settledSuccessfully</settlementState>
<paymentMethod>creditCard</paymentMethod>
<marketType>eCommerce</marketType>
<product>Card Not Present</product>
<statistics>
<statistic>
<accountType>Visa</accountType>
<chargeAmount>420.00</chargeAmount>
<chargeCount>3</chargeCount>
<refundAmount>0.00</refundAmount>
<refundCount>0</refundCount>
<voidCount>0</voidCount>
<declineCount>1</declineCount>
<errorCount>0</errorCount>
</statistic>
</statistics>
</batch>
</batchList>
</getSettledBatchListResponse>

Batches afer 9/1:

<?xml version="1.0" encoding="UTF-8"?>
<getSettledBatchListResponse xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<messages>
<resultCode>Ok</resultCode>
<message>
<code>I00001</code>
<text>Successful.</text>
</message>
</messages>
<batchList>
<batch>
<batchId>4612543</batchId>
<settlementTimeUTC>2015-09-03T02:52:14Z</settlementTimeUTC>
<settlementTimeLocal>2015-09-02T19:52:14</settlementTimeLocal>
<settlementState>settlementError</settlementState>
<paymentMethod>creditCard</paymentMethod>
<marketType>eCommerce</marketType>
<product>Card Not Present</product>
<statistics>
<statistic>
<chargeAmount>-79228162514264337593543950335</chargeAmount>
<chargeCount>-2147483648</chargeCount>
<refundAmount>-79228162514264337593543950335</refundAmount>
<refundCount>-2147483648</refundCount>
<voidCount>-2147483648</voidCount>
<declineCount>-2147483648</declineCount>
<errorCount>-2147483648</errorCount>
</statistic>
</statistics>
</batch>
<batch>
<batchId>4612544</batchId>
<settlementTimeUTC>2015-09-03T02:52:17Z</settlementTimeUTC>
<settlementTimeLocal>2015-09-02T19:52:17</settlementTimeLocal>
<settlementState>settledSuccessfully</settlementState>
<paymentMethod>creditCard</paymentMethod>
<marketType>eCommerce</marketType>
<product>Card Not Present</product>
<statistics>
<statistic>
<chargeAmount>-79228162514264337593543950335</chargeAmount>
<chargeCount>-2147483648</chargeCount>
<refundAmount>-79228162514264337593543950335</refundAmount>
<refundCount>-2147483648</refundCount>
<voidCount>-2147483648</voidCount>
<declineCount>-2147483648</declineCount>
<errorCount>-2147483648</errorCount>
</statistic>
</statistics>
</batch>
</batchList>
</getSettledBatchListResponse>

[RaynorC1emen7]

2147483648 - max int

79228162514264337593543950335 max decimal

look like A.net developer is working on something.

[RichardH]

Hello @afail

Could you try the same transaction using the live console in the API Reference and see if you see the same results?  This may help narrow down the problem.

http://developer.authorize.net/api/reference/#transaction-reporting-get-settled-batch-list

Richard

[afail]

I can reproduce it using the live module. 

Range of 2015-08-01 to 2015-08-31 returns valid results

Range of 2015-09-01 to 2015-09-30 returns invalid results

[RichardH · Accepted solution]

Hello @afail

We did some poking around and it appears the data was incorrectly written to the database due to an update which was subsequently rolled back.  My best suggestion is to wait a few days and see if the responses return to normal.

Thanks for reporting this, and we're sorry for any inconvenience this have have caused.

Richard

[afail]

Thanks so much!

[shr]

In sandbox mode of authorize .net

"http://developer.authorize.net/api/reference/#transaction-reporting-get-settled-batch-list" code works for me but In LIVE authorize mode I am getting this error "ERROR : Invalid response Response : E00003 The 'AnetApi/xml/v1/schema/AnetApiSchema.xsd:transactionKey' element is invalid - The value XXXXXXXXXXXXXXXXXXX is invalid according to its datatype 'String' - The actual length is greater than the MaxLength value. "