Authorize.net Not accepting CC "Customer ID Required" Error

[jlamarferren]

Hello,

I'm using Authorize.net as my gateway for S2member Pro and for some reason when I tested it in Sandbox everything went fine.

I put in my live API credentials and generated the pro form for Authorize.net. When I use Credit Card to signup, I'm getting an Error 33: Customer ID Required

There is no field for the customer ID. I only ask for name, email, username, home address, and billing info... That's it!

Has anyone ever received this error? Is it something with the S2 Member plugin or do you think it might be Authorize.net. Please let me know because we're live and I guess this is the main reason why we haven't seen any subscriptions...

[Cristián Lávaque]

Could you post a screenshot of the error as well as the pro-form shortcode you're using?

And the log entries for a transaction that failed with this error? (x'ing out any private info) WP Admin -> s2Member -> Auth.Net Options -> Account Details -> Enable Logging

[Jason Caldwell]

This sounds like a conflict in your Authorize.Net account configuration. s2Member does not collect, nor does it generate a Customer ID. A Customer ID is only valid when/if an application is utilizing the Authorize.Net CIM service, which s2Member does not. Thus, no Customer ID is passed through.

Please read over the following, or go here and type in 33 please.
http://developer.authorize.net/tools/re ... easoncode/

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.

[jlamarferren]

You're absolutely right Jason. We had to authenticate one of the settings within Authorize.net and have been successfully getting subscriptions.

[Jason Caldwell]

Great, thanks for reporting back on this!