|
smejia
|
February 10, 2015 at 11:14 am
I keep getting an error when trying to pay with authorize.net. It’s giving me the following error: Declined
Phone is required. (code: 33)
I’ve also tried testing it in test mode.
The phone number is on there. One thing I also noticed is that there is no star next to the number stating that it’s required.
|
|
Seth Shoultes
|
February 10, 2015 at 8:28 pm
Hello,
I believe we may have a fix released for this soon, but it also looks like something that can be changed within your Authorize.net account.
Got this from the Authorize.net website:
Response Reason Code: 33
Response Reason Text: FIELD cannot be left blank.
Integration Team Suggestions: The FIELD is set as Required in the Merchant Interface and the FIELD is not being sent to the gateway. To change the FIELD value to NOT REQUIRED: Login to the Merchant Interface ( https://secure.authorize.net ), click on Settings and Profile -> Payment Form -> Form Fields and uncheck the Required box for the particular FIELD.
Other Suggestions: The word FIELD will be replaced by an actual field name. This error indicates that a field the merchant specified as required was not filled in.
|
|
smejia
|
February 11, 2015 at 8:55 am
Hi Seth,
Thanks for the reply. I’ll look into this with authorize, but this is definitely something that should be working on your end. There is definitely a problem with the field not populating. If you see on this print screen, it’s the only important field that isn’t required – http://snag.gy/XWaIM.jpg.
|
|
Tony
|
February 11, 2015 at 11:17 am
Hi,
We have a fix for the Phone number not being passed to Auth.net that is being tested currently.
By default we only require information that is required for the transaction, name, email & address info. Phone number is an optional extra as it is not required to process the transaction.
However we do realise that you can set different settings within your your auth.net account, therefore setting ‘Phone number’ within auth.net to required and it not being the same on the gateway form could cause problems. We have opened a ticket to address this.
|
|
Josh
|
February 16, 2015 at 7:39 pm
Hi there,
A little update: This is fixed in Event Espresso 4.6.7.p.
|
