Remove 1,000 transaction limit on unsettled transactions API

[rshandel]

There seems to be many companies that have more than a 1,000 unsettled transactions they need to review on a daily basis. Being able to pull this down programmatically is an important feature for us to evaluate/validate unsettled transactions each day. Removing the limit on the Get Unsettled Transactions API function would be a great help! Thanks,

[RichardH]

We have delivered this capability with an update to the reporting API methods:

Element	Description
sorting	Contains sorting information
orderBy	Order of transactions in response:          id          submitTimeUTC
orderDescending	true, false, 1 or 0
Paging
limit	1-1000. The number of transactions per page.
offset	1-100000. The number of the page.

Unsettled Transactions

The example request below will retrieve the last 100 unsettled transactions by time submitted.  With this release, sorting can be on either transaction ID or transaction submit time.

<getUnsettledTransactionListRequest>
    <merchantAuthentication>
        <name>API_LOGIN_ID</name>
        <transactionKey>TRANSACTION_KEY</transactionKey>
    </merchantAuthentication>
    <sorting>
      <orderBy>submitTimeUTC</orderBy>
      <orderDescending>true</orderDescending>
    </sorting>
    <paging>
      <limit>100</limit>
      <offset>1</offset>
    </paging>
</getUnsettledTransactionListRequest>

The resulting GetTransactionList response is unchanged apart from one new field, totalNumInResultSet.

Settled Transactions

Pagination works exactly the same way for settled transactions. Use the paging elements to page through a settled batch of transactions 100 at a time. 

<getTransactionListRequest> 
  <merchantAuthentication> 
    <name>API_LOGIN_ID</name> 
    <transactionKey>TRANSACTION_KEY</transactionKey> 
  </merchantAuthentication> 
  <batchId>6416551</batchId> 
  <paging> 
    <limit>300</limit> 
    <offset>1</offset> 
  </paging> 
</getTransactionListRequest>

The resulting GetTransactionList response is unchanged apart from one new field, totalNumInResultSet.