Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Nik 1517 posts 6705 karma points MVP 5x c-trib
    Aug 06, 2021 @ 13:56
    Nik
    0

    Vendr Order Status 401

    Hi Matt,

    I'm currently getting quite a few orders with the Order Status Code value set to 401, but I can't seem to figure out what this means as there is no reference to the code in the VendrOrderStatus table.

    Looking at a sample of 2:

    The first order appears to have been paid for via the Opayo payment provider and I can see, looking in the [vendrActivityLog] table 3 entries (in time order):

    • vendr/order/payment/capture
    • vendr/order/new
    • vendr/order/status/change

    From what I can tell the payment capture was okay with no problems as the status change log entry happened 25 seconds after the "new" entry

    The second order appears to have been paid for via the default Invoice payment provider and it only has 2 entries in the [vendrActivityLog] table:

    • vendr/order/payment/authorize
    • vendr/order/new

    I can't see any reason or any log errors around the same time as these orders that indicate why they might be in the error state.

    The site is currently running version 1.5.3 of Vendr, although an upgrade to be latest version is scheduled. However, the client is trying to identify why they are getting alot of "error" orders reported/showing.

    Any advice/guidance would be great.

    Thanks

    Nik

  • Matt Brailsford 3685 posts 19396 karma points MVP 9x c-trib
    Aug 06, 2021 @ 15:05
    Matt Brailsford
    0

    Hi Nik,

    So an order status code of 401 is InconsistentOrderReference and so this potentially means that the callback URL that was notified received an order reference that didn't match the order that was looked up.

    An order reference is made up of the Order ID + Order Number.

    So you are likely to get this error if a) a callback URL was called for the wrong order or b) the order changed in a way that forced a new order number to be generated causing the callback to no longer match the order in the DB.

    The later can occur if you are modifying an order after it has gone to the payment gateway in such a way that forces it to be recalculated. I'd suggest double checking your code and make sure you haven't got anything that could be inadvertently modifying the order after it's been sent to the gateway that is forcing a new order number to be created.

    Hope this helps

    Matt

Please Sign in or register to post replies

Write your reply to:

Draft