Hello,
A client of ours is interested in using transaction data from Authorize.net (specifically "Settlement Amount" field) to retroactively update their database.
To clarify, we are saving an amount in our records for certain transactions based on the amount we expect and the success of the transaction, but certain events can effectively change these amounts, such as voiding a transaction.
There are a few ways we can think to accomplish this, the least desirable of which would include some manual work. What we'd really like to do is programmatically get a list of transactions that have been updated after a certain time frame (we still need to update the field if it changes whether the original transaction was a week ago or a month ago making the time of update the relevant factor here), and then update each relevant transaction in our database.
Looking through the API reference I cannot find any transaction list related endpoint that allows this kind of functionality. We'd be thrilled if there was a way to do this unbeknownst to us, but if there is not hopefully somebody can use their expertise to point us in the direction of an alternative approach to accomplish our goal, as we cannot think of a way to leverage the endpoints available in the way we need to.
Thanks,
Fivable
Solved! Go to Solution.
11-08-2018 05:54 AM
12-04-2018 04:21 AM
You can do this with 2 api calls in sequence. Once a transaction is settled the settlement amount will not change.
getSettledBatchList
https://developer.authorize.net/api/reference/#transaction-reporting-get-settled-batch-list
Get a list of batches, then use a single batch to retreive transaction information - which includes the settlement amount.
getTransactionListRequest
https://developer.authorize.net/api/reference/#transaction-reporting-get-transaction-list
11-09-2018 02:10 PM
Hi mmcguire,
I appreciate the response, and those are some of the endpoints I found when looking through your documentation. This might actually solve my problem, but with one caveat. I was under the impression that even once a transaction was "settled" the settlement amount could be changed in the event of a refund. If this isn't the case, could you explain to me what happens when a refund occurs to reflect this?
So the issue really remains whether or not I can retrieve transactions based on the time they were last updated. If they will never be updated after settlement (at all) then this may be a good option for us, but if the records might be further changed, it does us very little good.
Thanks again,
Fivable
11-27-2018 02:09 PM
12-04-2018 04:21 AM
Thanks Renaissance. Although I will have to do some additional things for retroactively updating some of our records, I believe webhooks would have been the way to correctly deal with this originally and ongoing.
12-17-2018 12:53 PM
12-18-2018 04:36 AM
We solely use PHP for the time being so I'm afraid I wouldn't have anything interesting to tell you about other languages.
01-04-2019 11:18 AM
01-08-2019 10:24 PM