Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 2 of 2

Thread: Authorize.net submitted date differ from order date in ASPDNSF

  1. 12-13-2010, 02:56 PM #1
    allstar is offline Member
    Join Date
    Apr 2009
    Posts
    90

    Default Authorize.net submitted date differ from order date in ASPDNSF

    I created a custom report to return daily orders that are settled via authorize.net. My settlement Transaction Cut-Off Time is set to 12:00 PM PST.

    According to Authorize.NET, orders placed after 12:00:00 PM is consider next day. I've noticed a difference in submitted time and order date between Authorize.Net and ASPDNSF.

    For example, there was an order submitted at 11:59:52 AM per Authorize.Net. However, ASPDNSF order date time is shown as 12:00:11.487. Therefore, when I query the orders to display in my report, the orders either get included or excluded.

    Why is Authorize.Net submitted date not recorded as the order date? How is the capturedon, authorizedon, and order date differ from the submitted date in Authorize.Net?
    Last edited by allstar; 12-15-2010 at 02:48 PM.
    ...AllStar
  2. 12-16-2010, 01:12 PM #2
    allstar is offline Member
    Join Date
    Apr 2009
    Posts
    90

    Default

    Submitted a ticket for support. ASPDNSF response:

    There's always going to be a slight difference in times between what Auth.net records and what the store uses. Auth.net is recording the time that the request hit their server, and the software records when the order completes on this end. A difference of 19 seconds really isn't that big of a deal, that one just happened to span that 12:00 time and cause a reporting problem.

    This shouldn't be something that happens all that often, it's only going to be an issue for orders that come in exact within that few second time frame. I'm afraid there's nothing we can do about it though, there's always going to be a few second discrepancy between the store and the gateway.
    ...AllStar