Looks like since 1.2.0 came out, a client of ours that uses may have had issues where the form would accept everything but transactions never showed up on authorize.net's end. After some digging, it looks like it is tied to the latest updates of the Authoize.net plugin starting with 1.2.0 but seems to happen with 1.2.1

After turning on the debug I see this error:

(AuthorizeNet) Transaction Failed
The element 'shipTo' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' has invalid child element 'phoneNumber' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'. List of possible elements expected: 'country' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'.

In this client's, there is no ship to information fields mapped because nothing is physically shipped and also this was never needed before. It is for a digital service so those were never mapped. Is this now needed or something else going on?

I had a copy of 1.7 and rolled back to it and works fine without any shipTo mapping set.

I cannot find any change log for 1.2.0 and 1.2.1. Nothing listed in at www.rsjoomla.com/blog recently so not sure what is going on.

The plugin's Documentation doesn't indicated this is needed either and I'd think if this a requirement by Authorize.net the 1.7 version would fail too.

Using RSForm! Pro 2.1.0 either way so I don't think that is the issue. It is only if we try the latest version of the Authorize.net plugin.

Note we also don't have any "Country" field anywhere so that has never been mapped on any Authorize.net field and never been an issue before.

But then I also don't understand why that would have any impact on a phone # scheme filed with authorize.net mappings.

Just seems like something is mixed up in the scheme formatting