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
When creating a legalEntity and a 200 success is received with an originalLegalEntityId & originalLegalEntityStatus in the response instead of a legalEntityId or legalEntityIdResponse then legalEntityResponse.legalEntityId == null and legalEntityResponse.originallegalEntityId == null.
I would expect in the above scenario for legalEntityId == null but for originallegalEntityId to equal the originalLegalEntityId from the response XML.
This appears to be a serialization issue - the XML is cased with an upper-case "Legal" while the C# property is written with a lower-case "legal". This appears to also be the issue with originalLegalEntityStatus.
When creating a legalEntity and a 200 success is received with an originalLegalEntityId & originalLegalEntityStatus in the response instead of a legalEntityId or legalEntityIdResponse then
legalEntityResponse.legalEntityId == null
andlegalEntityResponse.originallegalEntityId == null
.I would expect in the above scenario for
legalEntityId == null
but fororiginallegalEntityId
to equal the originalLegalEntityId from the response XML.This appears to be a serialization issue - the XML is cased with an upper-case "Legal" while the C# property is written with a lower-case "legal". This appears to also be the issue with originalLegalEntityStatus.
I believe the following property needs to be changed, or extra code needs to be added to properly convert the raw XML into the properties listed above
https://github.com/Vantiv/payfac-mp-sdk-dotnet/blob/13.x/PayFacMpSDK/PayFacMpSDK/Generated.cs#L3693
Example request XML (preprod env url removed):
Example response XML (preprod env url removed):
Example C# code to generate above XML (config removed):
Please let me know if further info is needed.
Edit: had a typo in my example code
The text was updated successfully, but these errors were encountered: