Open APIs

  • 1.  TMF670 - Type enumeration and status

    TM Forum Member
    Posted Oct 15, 2021 05:42
    Edited by Paul Austdal Oct 15, 2021 07:49

    When looking at the TMF670 Payment Method API specification in, I see that the enumeration values for '@type' does not match the actual sub types. For example, we see the enumeration value 'voucher', but the type is named 'Voucher'. Is this an error, or is it a convention to always use type enumeration in lowercase?

    About status of payment methods. Is there a recommended list of status values for a payment method? In the documentation and specification, I've only found a few examples: 'Active' and 'InActive'. Is it expected that we define whatever statuses are relevant in our context? For example when using vouchers, we need to represent a reserved status, and perhaps others as well.


    Paul Austdal
    Telia Company

  • 2.  RE: TMF670 - Type enumeration and status

    TM Forum Member
    Posted Oct 25, 2021 09:48
    Hi Paul
    In the user guide (spec) that you refer to, PaymentMethod.@type is a string, not an enum. The documentation string suggests examples, but these are not definitions.
    In fact, the actual type values would be derived from the concrete subclasses of PaymentMethod, which are indeed uppercase since they are data type names.
    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.