Open APIs

Dear Members,

Hereby I have some questions/comments regarding the current implementation of the mentioned above TMF670 Payment methods / TMF676 Payment management API. How somebody can clarify it: 

So:

for both APIs:
- why either API does not support Currency attributes in the models? From the user /use case perspective that would be useful and helpful to operate entities represented in a specific currency. 

for TMF670 Payment methods:
- does a support of the back-up payment method use-cases valuable enough to expose relevant ref object for payment method object?

for TMF676 Payment management :
-irrespectively to the SID comments probably it has to be additionally noted that swagger schema does not fully comply with base API spec (either some attributes are missing or wrongly named, like 
--there is an incorrect naming for 'preferred' attribute in swagger - which is currently exposed as 'isPreferred' while in TMF670 it is just 'preferred'.
--etc


Regards
Maksym

------------------------------
Maksym Shvets
Netcracker Technology
------------------------------

Hi Maksym
Both APIs are being refreshed, not sure of a committed date for this.
Payment method is being done by @Stephen Harrop , payment management by @Anh Tuan NGUYEN - so you may want to reach out to them with your concerns.
Please note that our API documentation and swagger files are now being generated from the same common schema files, so there should no longer be discrepancies between the spec (we are now calling this user guide) and swagger. 
We have a central Money type, which should now be used for all monetary amounts, its attributes are unit and value, where unit would be a currency code.

Hope it helps
​​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------