CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviContribute »
  • Community Contributed Payment Processors »
  • Authorize.net Test Processing changes...
Pages: [1]

Author Topic: Authorize.net Test Processing changes...  (Read 8014 times)

hp3kman

  • I post occasionally
  • **
  • Posts: 74
  • Karma: 4
Authorize.net Test Processing changes...
September 08, 2008, 10:16:18 am
Just got off the phone w/ Authorize.net, and they informed me that they are doing away w/ their test system...

In trying to 'test-drive' pages, I was consistently getting the error message:

Payment Processor Error message
: 2:13 (TESTMODE) The merchant login ID or password is invalid or the account is inactive.

Their rep told me that this is because they are phasing out their test system; going forward, they are expecting test transactions to be sent to live, but flagged as a test...

Somewhere, in the doc, I read that there were two ways of sending test transactions to Authorize.net, and one of them was sending a specific flag to the live system indicating it was a test.

I've gotten everything up and working by setting my live system to test mode, but once I turn that off, I'll have no facility to test anything until this is changed...is this in the works??? I'm on version 2.0.5.

What I believe needs to happen is that, in CC Processor setup, there will no longer need to be different login credentials and urls for live vs. test transactions, and that the 'test-drive' links will add the test flag to the transaction, and send everything to their live servers...

Can anyone verify this???

Thanks!

MacRonin

  • I post frequently
  • ***
  • Posts: 153
  • Karma: 14
Re: Authorize.net Test Processing changes...
September 08, 2008, 12:15:05 pm
I can't speak as to future plans, but having a Global setting that activates the TEST flag on all transactions does sound like a good idea if Authorize.net is removing the test system. New users definitely need a way to safely test the system.

But for now if you goto the Manage Events page(where you can choose which event configurations that you want to change) you can instead choose the "Test Drive" option. I believe that this sets the transaction Test  flag that you mention. I've been using it recently(in the last week) with no problems. All transactions came thru as Test with no actual charges. I was also using their test MC cc#

hp3kman

  • I post occasionally
  • **
  • Posts: 74
  • Karma: 4
Re: Authorize.net Test Processing changes...
September 08, 2008, 04:39:21 pm
Thanks for the input...

My problem is that I can't 'test-drive' anything...with my settings in global config set to live servers for live transactions and test servers for test transactions, it errors out when I use 'test drive'.

From your post, though, I'm wondering if I should have their test servers set up at all, if that, indeed, is where the 'test' flag is being added...do you know??? And what are your servers set up as??? And what version of Civi are you on???

Mine are:

https://secure.authorize.net/gateway/transact.dll for LIVE
https://test.authorize.net/gateway/transact.dll for TEST

I'm on Civi version 2.0.5

To me, all that needs to be done is:

1) remove the 'Processor Details for Test Payments' entirely from global settings and;
2) Wherever you can "Test Drive" a payment process, add the test flag to what is being sent to the live servers.

I presently have my live servers in test mode, but if I knew for sure I were sending the test flag when I 'Test Drive', it wouldn't matter; Authorize.net treats anything with the 'test' flag as a test, regardless of your account settings on their end...

As I alluded to in my earlier post, the doc is sketchy on this point, because it says:

Quote
Live vs Test
Authorize.Net has a test server and you can set your Merchant Account to run in Test Mode. In this case, all transactions are considered to be tests. However, you can also use the live server and login for testing. The addition of a single field (x_test_request) to the information being sent to Authorize.Net indicates that the transaction is a test.

And then later it says:

Quote
Site URL for Test Mode
If your Merchant Account is set to run in Test Mode, then you must use the following test server in your Payment Processor Settings for Site URL: https://test.authorize.net/gateway/transact.dll
Once your Merchant Account is Live - you may need to modify the CiviCRM Payment Processor settings to use the live server Site URL for both test-drive and live payments:

https://secure.authorize.net/gateway/transact.dll

Which is absolutely INCORRECT...the first part is what is really the case; if your merchant account is in Test Mode, ALL incoming transactions are treated as tests, regardless that you are sending them to your LIVE url (NOT the test url, as is indicated above). Indeed, the test urls won't work at all anymore...(at least for me...); and, according to Authorize.net, any test - or TEST DRIVE in CiviSpeak - should include the "x_test_request" flag and be sent to the LIVE url...

Thanks again for your help in trying to clarify this...It could be, I suppose, that the coding is partially there, but I'd need to know which urls you are using to know for sure...

MacRonin

  • I post frequently
  • ***
  • Posts: 153
  • Karma: 14
Re: Authorize.net Test Processing changes...
September 09, 2008, 10:51:17 am
As ar as i can remember(It's been a while & we had Authorize.net before CiviCRM)You are correct that the account being in Test mode is an all or nothing approach. There was no way to do actual transactions while the account was in Test mode.

I just upgraded from 1.8php4 to 2.0 and didn't change my settings for Authorize.net. My Test and Live both point to https://secure.authorize.net/gateway/transact.dll The recurring URL is different but both do point to the same place. But then again I'm not using that function yet.

With this setup I can and do make individual Test transactions by using the Test version of the Contrib or Event pages, along with fake/text CC #'s. The CiviCRM receipts and the Authorize.net ones both correctly label and flag the transactions as Test. Neither actually tries to change the card and the fake numbers go thru

I know I did use explicit Test servers at some point in the far past when I used stand-alone code instead of CiviCRM to process charges, but can't be sure what the setting were(under 1.8 ) before my recent upgrade to 2.0 without restoring that version. But based on my current URL settings it would look like both should go to live URL and just use the Test flag to process a transaction in Test mode. But remember your mileage and configuration may vary and should double check all this yourself. (I don't want to be responsible for messing up your CC if you use a real card under what should be test mode and get charged  :o )

hp3kman

  • I post occasionally
  • **
  • Posts: 74
  • Karma: 4
Re: Authorize.net Test Processing changes...
September 09, 2008, 06:47:30 pm
Ah...just as I suspected...it seems that "Test Drive" DOES add the test flag, so having a Test setting in Global Settings...cc processors seems redundant (they're both set to the same thing on your site and they work as designed...).

I'll just set my test global settings to live and give it a go w/ a test CC...if it's flagged as test, it will go thru...if it goes to live, it will decline (according to Authorize.net).

Are there any plans to eliminate the test settings in global for Authorize.net???

I'm sure I'm not the only one who was confused by this...

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Authorize.net Test Processing changes...
September 09, 2008, 08:50:09 pm
Quote from: hp3kman on September 09, 2008, 06:47:30 pm
Are there any plans to eliminate the test settings in global for Authorize.net???

I'm sure I'm not the only one who was confused by this...

No plans for now. authorize.net is one of the few processors to use the same url for both live and test gateways. You might want to consider improving the docs / help screen for authorize.net to make it easier for future authorize.net users

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

hp3kman

  • I post occasionally
  • **
  • Posts: 74
  • Karma: 4
Re: Authorize.net Test Processing changes...
September 10, 2008, 05:27:23 am
Will do, lobo...where would I go to do that???

ishmael-sanchez

  • I’m new here
  • *
  • Posts: 3
  • Karma: 0
  • CiviCRM version: 3.3
  • CMS version: Drupal 6
  • MySQL version: 5
  • PHP version: 5
Re: Authorize.net Test Processing changes...
April 13, 2011, 06:29:01 pm
Ok this is still an issue. If you test-drive a page and you want the transaction recorded in Authorize.net you need to add

unset($cookedParams['x_test_request']);

in your civicrm_alterPaymentProcessorParams hook otherwise Authorize.net will see that flag and wont record your transaction. Is this a possible bug?
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviContribute »
  • Community Contributed Payment Processors »
  • Authorize.net Test Processing changes...

This forum was archived on 2017-11-26.