So we ran our first production check of expiring credit cards earlier this week, and got back 10 results instead of the much larger number we expected.
The problem appears to be that the production
auth.net function getCustomerPaymentProfileListResponse doesn't work as advertised. While you can specify a paging limit between 1 and 1000, the production gateway appears to always use a paging limit of 10 in the response.
Calling this (sensitive data censored out):
<getCustomerPaymentProfileListRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
<clientId>sdk-java-1.9.0</clientId>
<searchType>cardsExpiringInMonth</searchType>
<month>2017-04</month>
<sorting>
<orderBy>id</orderBy>
<orderDescending>false</orderDescending>
</sorting>
<paging>
<limit>1000</limit>
<offset>1</offset>
</paging>
</getCustomerPaymentProfileListRequest>Returns this (sensitive data censored out):
<getCustomerPaymentProfileListResponse
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
<messages>
<resultCode>Ok</resultCode>
<message>
<code>I00001</code>
<text>Successful.</text>
</message>
</messages>
<totalNumInResultSet>79</totalNumInResultSet>
<paymentProfiles>
[Only 10 PaymentProfile records]
</paymentProfiles>
</getCustomerPaymentProfileListResponse>I was able to work around the problem by continuing to fetch data with ever-increasing paging-offsets until I got a response back with no payment profiles.
