order already exists in database

Im am doing testing on a site and Im getting this error.
This is after I have submitted multiple tests.

PROBLEM
I could understand getting this error if a transaction was actually logged - however I am getting this when no transaction has been logged on the gateway (not declined and not approved). Nor has anything been saved on my end in the database.

ADDITIONALLY
I have had this error reported on a different website with the same error report, but the gateway is auth.net. In the same conditions - the user got an error and went back and resubmitted thier info. However no transaction was logged and neither was anything saved to the database.

Any Ideas on how to get around this?

look in the authorize.net code on the confirm page to see what is being used for the x_invoice_num value, we usually use the session ID:


$AuthNet_required[0][$nextIndex] = "x_invoice_num";
$AuthNet_required[1][$nextIndex] = "".session_id() ."";


If you are using the session ID and having this problem, you should check that the host is properly set up to assign a unique ID for each browsing session.

the transaction will not be stored in the database unless it was successful.

for both websites i checked, both are on different hosting servers and both have the order id that is sent to the gateway set as the session id.

so both sites i have this issue with are on 2 different hosts and use 2 different gateways.
but both have the sessionid set as the order id sent to the gateway.

i know that others are having trouble with this (ie others using other carts etc).in my quest to solve this i found many message boards on this topic.

The issue is that somehow even if the transaction is not approved the order id that is sent to the gateway is logged. so when trying to run it again (ie user goes back to modify info) its using the same session id still. so thats when the error occurs that it says the order is already exists. it exists in the gateways database.

has ANYONE else found this issue? ways around it?

sam

try adding the following code on the failure page:
<?php session_regenerate_id(); ?>

this should create a new session id to use if the transaction fails.

found something that might help future users on this topic

inside linkpoint there is fraud controls that you can set the timing to.
so you can control how often a cc can be reused, etc.
by decreasing these numbers i was able to continue my site testing without getting the notice of the "order exists in database"