Create Customer Profile requests with emails containing a + symbol return E00013 "email is invalid"

[jantzenw]

Create Customer Profile requests with emails containing a + symbol return E00013 "email is invalid"

Request without error: http://www.screencast.com/t/a5sxNsEn

Request with error: http://www.screencast.com/t/RZPbDcl57S

Request and response without error: https://gist.github.com/jantzenw/cf672ec18b36ac069109dcb452a2d525

Request and response with error: https://gist.github.com/jantzenw/a65636cd78f9757b5eb1222dd63766d5

The first instance of this error was today at 2018-03-29T14:23:40+00:00.

It is critical that the email validation be updated to allow + symbols because this is a valid email character: https://support.google.com/mail/answer/22370?hl=en#alias. This is commonly used in testing to allow multiple accounts to share the same inbox. 

[eweblife123]

Please note, many spouses share emails and use the + sign to create unique logins for systems and other purposes.  Gmail and some other providers allow this usage. 

[chsriniv9]

Hi Matth,

Could you please share more details about the payment flow and at what point you are getting error when trying to place order.

Regards,

Chethan

[matth]

Hi Chethan,

This is just with WooCommerce and the standard Authorize.Net plugin: https://docs.woocommerce.com/document/authorize-net-cim/

Whenever a customer tries to place an order and their Email address for their WooCommerce account has a + character in it this error "Code: E00013, Message: email is invalid." is returned.

Removing the + from their account and it works fine.

Matt

[maestrojed]

Us too.

A plus sign is valid character in an email according to any standard. It is used by, allowed and recommended by some of the largest providers.

We are receiving multiple errors because of this, in production....

[TSeale]

Please provide frequent updates to this issue. This is wreaking havoc on our testing as we've developed automation scripts that use this technique.

[denis8475]

Hi,

We use Authorize.net as a payment gateway with Chargify.com.  We are also affected by this change.  Like others who have replied, we rely on using "+" in email addresses to create unique email addresses for a shared inbox, to facilitate our development and QA processes.

Please consider rolling back this change to allow us to use "+" in our email addresses again.

Thanks,

Denis

[asolomon]

Like many of the other commenters, I too run a website that relies on the "+" symbol in email addresses. This unexpected change to the API has badly crippled our website and we are struggling to quickly correct our schema. Please revert the change, it is a valid character and many of the largest email providers support and encourage its use.

[DoveChris]

This change has really affected our sales website and the accounts we use. Can we get it reverted? It seems like a really major change to happen with no notice. 

[clincoln]

I work for a large company that relies on the "+" symbol in emails and we are being negatively impacted by this change. This change makes absolutely no sense since "+" is a valid character that is widely used by people and businesses. Please change back to allow this symbol ASAP!

[ksanborn]

We’re also encountering problems with this change, we rely on using “+” for email addresses in our system and this is creating significant support issues for us. It's an awfully significant update to issue with no warning. When can we expect to see this corrected?