topic Re: Transactions Details API: getUnsettledTransactionListRequest delay? in Integration and Testing

Transactions Details API: getUnsettledTransactionListRequest delay?

jakea — Tue, 21 Apr 2015 13:31:33 GMT

I'm writing some unit tests to test getUnsettledTransactionListRequest. I'm submitting a test AuthorizationRequest then querying for it using getUnsettledTransactionListRequest. If I immeditally use getUnsettledTransactionListRequest the test transaction isn't listed. If I wait 15-30 seconds its there. The delay seems to be inconsistent.

Is there a delay in the live system and what is the minimum I should way before checking the transaction?

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

RichardH — Thu, 23 Apr 2015 15:06:30 GMT

Hello @jakea

We're unable to duplicate the problem you reported. We ran a transaction and then immediately used getUnsettledTransactionListRequest and the transaction appears as expected.

Richard

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

jakea — Thu, 23 Apr 2015 18:54:26 GMT

@RichardH thanks for taking a look. It has consistently reproduced for me using the sdk for .net. I've uploaded my test for this, would it possible for you take a look and let me know if my test (TransactionDetailsDelayTest.cs) is passing for you?

You can find a copy of my test solution (its your .net sdk with my additional test) at:

https://www.dropbox.com/s/zitvv7q8fr3rpv1/sdk-dotnet-master-transaction%20details%20delay%20test.zip?dl=0

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

jakea — Wed, 29 Apr 2015 20:23:53 GMT

@RichardH did the attached tests not reproduce the issue for you?

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

RichardH — Wed, 29 Apr 2015 20:37:13 GMT

Hello @jakea

Sorry, I overlooked your response. May I suggest you submit an issue/pull request with the issue/solution in GitHub? This will notify the developer assigned to this language.

Richard

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

jakea — Thu, 30 Apr 2015 14:17:29 GMT

I don't see any sign that this is an issue with the .net sdk. I can reproduce the same delay using curl also:

Post transaction:

curl --data "x_delim_data=TRUE&x_delim_char=%7c&x_relay_response=FALSE&x_method=CC&x_version=3.1&x_type=AUTH_CAPTURE&x_card_num=4111111111111111&x_exp_date=0224&x_amount=5&x_description=&x_invoice_num=TEST_INVOICE_001&x_login=LOGIN ID HERE&x_tran_key=TRANSACTION KEY HERE" -H "Content-Type: application/x-www-form-urlencoded" https://test.authorize.net/gateway/transact.dll

Request unsettled list:

curl --data "<?xml version=\"1.0\" encoding=\"utf-8\"?><getUnsettledTransactionListRequest xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns=\"AnetApi/xml/v1/schema/AnetApiSchema.xsd\"><merchantAuthentication><name>LOGIN ID HERE</name><transactionKey>TRANSACTION KEY HERE</transactionKey></merchantAuthentication></getUnsettledTransactionListRequest>" -H "Content-Type: text/xml" https://apitest.authorize.net/xml/v1/request.api

If you put these in the same script and they run immediatly after each other you won't find the expected invoice number. Wait 5-10 seconds and run the "Request unsettled list" and it will show u

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

RichardH — Thu, 30 Apr 2015 21:23:03 GMT

Hello @jakea

I spoke with our lead database engineer. When you create transactions they are inserted into one database, and your subsequent getUnsettledTransactionListRequest is returned from a separate database using replicated data. This would explain why there is a short delay.

Richard

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

jakea — Thu, 30 Apr 2015 19:29:16 GMT

Thanks for checking, that makes sense. It would be helpful to have some guidance on what types of delay we can expect in production. Should I be expecting a similar 15-30 seconds like I'm seeing in the sandbox or an even larger delay?

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

RaynorC1emen7 — Thu, 30 Apr 2015 20:12:16 GMT

Can you do the GetTransactionDetails with the transactionID instead? I would expected that would be on the same database

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

RichardH — Fri, 01 May 2015 01:08:16 GMT

New transactions will insert as Authorized/Pending Capture or Authorized/Pending Settlement. Settlement only occurs once a day and begins sometime after the transaction cut-off time specified in the merchant interface. You should see similar performance in production.

Richard

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

jakea — Fri, 01 May 2015 12:16:04 GMT

The scenario we're trying to use getUnsettledTransactionListRequest for is getting the status of transactions that had some type of networking issue (we send a post but network fails and we don't get a response). These are rare but its something we'd like to automate handling of. In these cases we don't have a transactionId and must rely on the invoice number we generated.

The other two payment gateways we support allow referencing transaction details directly by invoice number, unfortunately with Authorize we need to getUnsettledTransactionListRequest to get the transactionId we lost and then get the rest of the transaction details using that.

Thanks for your help guys, we're going to just make sure we don't check getUnsettledTransactionListRequest for at least 5 minutes after a failure and assume that enough time for replication to reliably finish.

Re: Transactions Details API: getUnsettledTransactionListRequest delay?

knightcode — Wed, 14 Mar 2018 16:30:32 GMT

I'm having this same issue, but between the inperson-ios-sdk and the node-sdk. The POS conducts a transaction, coughs up a transaction id, which we send to our server. The server must verify the transaction isn't bogus data from unsavory actors, so it calls getTransactionDetails, which promptly returns a "Record not Found" error. If the POS then retries the submission, it then usually then finds the transaction.

I'd prefer not to, but I'll begrudgingly pummel your server with repeated requests until one succeeds.

Every milliseconds counts when there's a line of people waiting at the POS.

P.S. Can we get some kind of opaque but unique identifier for each card from the inperson SDKs? Anything to know its a returning customer? Something to make you competitive with Square???