Class PaymentMeansType


  • public class PaymentMeansType
    extends Object

    Java class for PaymentMeansType complex type

    .

    The following schema fragment specifies the expected content contained within this class.

    
     <complexType name="PaymentMeansType">
       <complexContent>
         <restriction base="{http://www.w3.org/2001/XMLSchema}anyType">
           <sequence>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2}ID" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2}PaymentMeansCode"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2}PaymentDueDate" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2}PaymentChannelCode" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2}InstructionID" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2}InstructionNote" maxOccurs="unbounded" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2}PaymentID" maxOccurs="unbounded" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2}CardAccount" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2}PayerFinancialAccount" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2}PayeeFinancialAccount" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2}CreditAccount" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2}PaymentMandate" minOccurs="0"/>
             <element ref="{urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2}TradeFinancing" minOccurs="0"/>
           </sequence>
         </restriction>
       </complexContent>
     </complexType>
     
    • Constructor Detail

      • PaymentMeansType

        public PaymentMeansType()
    • Method Detail

      • getID

        public IDType getID()
        Gets the value of the id property.
        Returns:
        possible object is IDType
      • setID

        public void setID​(IDType value)
        Sets the value of the id property.
        Parameters:
        value - allowed object is IDType
      • setPaymentDueDate

        public void setPaymentDueDate​(PaymentDueDateType value)
        Sets the value of the paymentDueDate property.
        Parameters:
        value - allowed object is PaymentDueDateType
      • setInstructionID

        public void setInstructionID​(InstructionIDType value)
        Sets the value of the instructionID property.
        Parameters:
        value - allowed object is InstructionIDType
      • getInstructionNote

        public List<InstructionNoteType> getInstructionNote()
        Gets the value of the instructionNote property.

        This accessor method returns a reference to the live list, not a snapshot. Therefore any modification you make to the returned list will be present inside the JAXB object. This is why there is not a set method for the instructionNote property.

        For example, to add a new item, do as follows:

         getInstructionNote().add(newItem);
         

        Objects of the following type(s) are allowed in the list InstructionNoteType

        Returns:
        The value of the instructionNote property.
      • getPaymentID

        public List<PaymentIDType> getPaymentID()
        Gets the value of the paymentID property.

        This accessor method returns a reference to the live list, not a snapshot. Therefore any modification you make to the returned list will be present inside the JAXB object. This is why there is not a set method for the paymentID property.

        For example, to add a new item, do as follows:

         getPaymentID().add(newItem);
         

        Objects of the following type(s) are allowed in the list PaymentIDType

        Returns:
        The value of the paymentID property.
      • setCardAccount

        public void setCardAccount​(CardAccountType value)
        Sets the value of the cardAccount property.
        Parameters:
        value - allowed object is CardAccountType
      • setPayerFinancialAccount

        public void setPayerFinancialAccount​(FinancialAccountType value)
        Sets the value of the payerFinancialAccount property.
        Parameters:
        value - allowed object is FinancialAccountType
      • setPayeeFinancialAccount

        public void setPayeeFinancialAccount​(FinancialAccountType value)
        Sets the value of the payeeFinancialAccount property.
        Parameters:
        value - allowed object is FinancialAccountType
      • setCreditAccount

        public void setCreditAccount​(CreditAccountType value)
        Sets the value of the creditAccount property.
        Parameters:
        value - allowed object is CreditAccountType
      • setPaymentMandate

        public void setPaymentMandate​(PaymentMandateType value)
        Sets the value of the paymentMandate property.
        Parameters:
        value - allowed object is PaymentMandateType
      • setTradeFinancing

        public void setTradeFinancing​(TradeFinancingType value)
        Sets the value of the tradeFinancing property.
        Parameters:
        value - allowed object is TradeFinancingType