fix: restore versioned list payments and recurring payments - #377
fix: restore versioned list payments and recurring payments#377tessstoddard wants to merge 1 commit into
Conversation
83bcad6 to
35b9ac0
Compare
35b9ac0 to
a3c2718
Compare
|
What is the reason for the new version? From what I can tell, there isn't a difference between the models, which is typical. |
@mattnichols for sure, that's usually the reason for using the versioned endpoints. Basically, nextgen is trying to standardize all these transfer features. But doing that breaks Helios behavior for payments. And there is no reliable way for the backend to know if requests are coming from nextgen vs helios. So that is why we decided on versioned endpoints. The model is the same but the behavior is different. This is the original MR that was approved and merged. I just had to revert it because the serialization wasn't working. So this MR reenables this with the serialization fix #371 |
Summary of Changes
Restore list version endpoints for recurring payments and payments. I had to add a cast to the return value so that the xml serializer understands that it is a MdxList or MdxList
Fixes # https://mxcom.atlassian.net/browse/GCU-1345
Public API Additions/Changes
Adds a versioned endpoint for list payment and recurring payment
Downstream Consumer Impact
None. Services that currently have this feature should be getting the default behavior
How Has This Been Tested?
Created a local snapshot and tested
List payments
List payments v20260427
List recurring payments
List recurring payments v20260427
GCU payment arsenal tests passing
Checklist: