CiviCRM Community Forums (archive)

We've been using authorize.net for several years to process payments through civicrm.

Today for some unknown reason, two of the payments made through authorize.net came back with transaction ids similar to test00000002.

Looking at the authorize.net backend, the transactions were not processed.

Looking at the civicrm backend, the transactions were processed as ordinary transactions and civicrm seems to have assumed that these were normal, live transactions.

Neither of these people would have had access to the testing URL.  Also the civicrm receipts do not indicate that the testing URL was used--ie, they are the regular, non-testing receipts just like 'real' transactions generate.

Have any of you seen anything like this before?

Could it be a problem on the civicrm side?  Could it be a problem (or setting) on the authorize.net side?

FYI civicrm settings for transaction processor seem OK, we processed several other transactions today with no problem (though both of the 'problem' transactions went through the same contribution page and the successful transactions went through a different contribution page).

Both contribution pages are similar--in fact one started as a clone of the other.  Of course a few settings were changed here & there, so maybe those differences is where the problem lies.

The contribution page uses a price set with contributions only, no members.

I check authorize.net and it is definitely not in 'test mode'.

We're running civicrm 4.2.2. and drupal 6.