CiviCRM Community Forums (archive)

We're using authorize.net for payment processing.  We've been using it for several years with the same basic setup.

Suddenly I'm getting the error "Payment Processor Error message 2: 33 Email is required." whenever a user attempts to submit an event registration with credit card payment.

 - Contribution pages work fine, no error.
 - Test event registrations work fine.
 - Backoffice event registrations with credit card (from the contact page/Events) work fine, no problem.
 - Our authorize.net settings do not include email messages to customers and the profile page doesn't require email address.

So this is somewhat mysterious.  Is anyone else experiencing it?

I'm always at a bit of a loss as to how to test this on the demo site as authorize.net isn't set up there.

This is under CiviCRM 4.2.2 and Drupal 6.

Suddenly I'm getting the error "Payment Processor Error message 2: 33 Email is required." whenever a user attempts to submit an event registration with credit card payment.

FYI I found the solution to this problem.  We actually do require the email address on the civicrm event registration form, but it is in a separate profile from the rest of the contact information for that contact, so my suspicion is that CiviCRM is not submitting the email address from this second profile in quite the correct way to Authorize.net

But at the same time, there is no reason for Authorize.net to require an email address--you can set it up to require an email address and send and email receipt, but in our case we process lots of credit card payments with no email address available, so there is no reason it should be required.

In our case, I am very sure we have turned off the 'email required' for CC purchase at Authorize.net before.  There must be something that makes this setting turn back on once in a while.

So in short, I think it is two minor bugs, one in CiviCRM and one at Authorize.net, that occasionally collide.

At any rate, here is how to go into your Authorize.net setup and change the settings to fix the problem:

When processing an event registration Authorize.net gives the error
    Payment Processor Error message
    2: 33 Email is required.

The solution:

 * Login to authorize.net
 * Click "Account"
 * Under Transaction Format Settings click “Payment Form”
 * “Form Fields”
 * Look for ‘email’ and uncheck ‘required’.
 * Submit

For some reason I had to do this twice--it didn’t take the first time

I'll add that a client just had the same experience with the phone number - disabling the requirement with Authorize.net (but keeping it on the profile!!) resolved the problem.

Curiously ... authorize.net indicated that they aren't receiving EITHER the phone or email.  In this instance the phone and email are both required, but in separate profiles so pointing our giant collective finger at the profiles doesn't seem to make sense.

btw  - v 4.3.5