Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PR57 + Fix #64

Merged
merged 4 commits into from
Nov 10, 2016
Merged

PR57 + Fix #64

merged 4 commits into from
Nov 10, 2016

Conversation

judgej
Copy link
Member

@judgej judgej commented Nov 10, 2016

This is PR #57 with a small fix to the position of the "order" element, which MUST come before the [optional] "customer" element. You would not notice this as a problem unless the customer ID is set. The documentation shows no examples with both "customer" and "order" elements in an AIM authorization request, but the test gateway does show up an error if the positions are not correct.

@judgej
Copy link
Member Author

judgej commented Nov 10, 2016

The error we are avoiding is:

{
   "messages":  { 
      "resultCode": "Error",
      "message":  {
         "code": "E00003", 
         "text": "The element 'transactionRequest' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' has invalid child element 'order' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'. List of possible elements expected: 'billTo, shipTo, customerIP, cardholderAuthentication, retail, employeeId, transactionSettings, userFields' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'." 
      }
   }
} 

@judgej judgej merged commit 104290d into thephpleague:master Nov 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants