Not sure if this was addressed before but when I was using Store 1.6 with Authorize.net if a person failed to put a last name they would get an error.
After upgrading to Store 2.x it was necessary to split the
billing_name form field into separate First and Last name fields.
I don't recall if this was because the last name was simply no longer required somehow (so no error with just one word submitted) or it if was somehow slipping through, but it just made more sense to use First/Last names separately now that they're split in the Order itself.
At the time this was a pretty big problem for us as we really needed the customers' last names. Several people were able to purchase with providing only a first name. I am not sure if this problem exists for other gateways and the transition from 1.6.x to 2.x.
edit for clarity:
In Store 1.6.x w/ Authorize.net:
- One billing name field, last name is required with only
require="billing_name", user gets an error if submitting checkout form without a second name (
The Last Name field is required.which to me suggests it's from the gateway.)
In Store 2.x w/ Authorize.net:
- One billing name field, order goes through with only one name despite being same form with
require="billing_name...". Last name is no longer required.
We didn't change anything on our merchant account. What went wrong? Was Store 1.6.x's error really from Authorize.net? If so, why doesn't it appear in Store 2.x? If not, why did it disappear in Store 2.x without any notice in the docs?