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

getTransactionDetailsRequest throws XML exception #278

Open
Bb2jake opened this issue Feb 17, 2020 · 3 comments
Open

getTransactionDetailsRequest throws XML exception #278

Bb2jake opened this issue Feb 17, 2020 · 3 comments

Comments

@Bb2jake
Copy link

Bb2jake commented Feb 17, 2020

Certain transactions are throwing the following error when trying to get the transaction details

System.InvalidOperationException: 'There is an error in XML document (1, 40).'

Inner Exception
was not expected.

Most requests are successful. Just a few specific transactions have this error, but I can find no differences between the transactions to explain the exception behavior.

@gnongsie
Copy link
Contributor

Hi,

Thank you for reaching out to us. Can you confirm if there is anything different between the successful request and the failed request? Maybe there are some slight differences in the data.

@Bb2jake
Copy link
Author

Bb2jake commented Feb 20, 2020

I've looked at them side by side. There's literally no difference except the credit card that was used. It's the same customer, same name, all the info is the same.

And the request itself is the exact same except for the transaction id.

@Bb2jake
Copy link
Author

Bb2jake commented Feb 20, 2020

I can retrieve the data via the postman POST call. After looking at the data retrieved, the only difference between the failed requests via the SDK and successful is this

"purchaseOrderDateUTCDateTime": "0001-01-01T00:00:00",
"purchaseOrderDateUTC": "0001/01/01"

under transaction -> order

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants