You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have closely followed the example code and documentation, but no matter whether or not I explicitly include a merchantAuthentication element in my request it always fails with this error:
The element 'ARBCreateSubscriptionRequest' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'
has invalid child element 'merchantAuthentication' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'.
List of possible elements expected: 'refId, subscription' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'.
You'll note the tokenize_card method does not include the merchantAuthentication key and the create_subscription method does, but both return the exact same error other than the request namespace and expected elements. The code samples and documentation make zero mention of the merchantAuthentication key, which makes be believe that it's likely being handled internally by the API::Transaction object, but the error makes me believe it must be doing something incorrectly. I called support and all they could do was point me back to the documentation which holds no answers for this problem.
The text was updated successfully, but these errors were encountered:
I have closely followed the example code and documentation, but no matter whether or not I explicitly include a merchantAuthentication element in my request it always fails with this error:
Here's my code:
You'll note the tokenize_card method does not include the merchantAuthentication key and the create_subscription method does, but both return the exact same error other than the request namespace and expected elements. The code samples and documentation make zero mention of the merchantAuthentication key, which makes be believe that it's likely being handled internally by the API::Transaction object, but the error makes me believe it must be doing something incorrectly. I called support and all they could do was point me back to the documentation which holds no answers for this problem.
The text was updated successfully, but these errors were encountered: