complexType Charge

diagram
namespace	http://www.ibillingclient.org/schema/edi
type	extension of ClientObject
properties	base  ClientObject
used by	element  PaymentPlan/charge
attributes	Name   Type   Use   Default   Fixed   annotation id xs:ID required         documentation id: System generated identifier. createDate Date optional         documentation createDate: Date the transaction was created. code xs:string required         documentation code: User assigned identifier. (if not specified, id is used) merchantAccountCode MerchantAccountCode required         documentation merchantAccountCode: Merchant account code. processedDate Date optional         documentation processedDate: Date when the charge was processed by the invoicing process. isPrepaid xs:boolean optional         documentation isPrepaid: If true, payment was taken against this charge. This doesn't guaranteethat the invoice created from this charge will be automatically paid type xs:string optional         documentation type: TYpe of charge. index xs:int optional         documentation index: Sequential number of the charge within PaymentPlan. 0 indicates that thecharge will be processed in the next billing process, 1 - the one afterthe next and so on paymentPlan xs:IDREF optional         documentation paymentPlan: Reference to the PaymentPlan holding the charges.
annotation	documentation Represents a future invoice within a PaymentPlan. Each time when billing isprocessed (Invoicing processing is executed) a charge is processed. Fixed andPerpetual charges are converted into invoices. Complimentary charges areconverted into invoices that are immediately balanced out with allowances.Freezes and Deferment produce no invoices.
source	<xs:complexType name="Charge">   <xs:annotation>     <xs:documentation>Represents a future invoice within a PaymentPlan. Each time when billing isprocessed (Invoicing processing is executed) a charge is processed. Fixed andPerpetual charges are converted into invoices. Complimentary charges areconverted into invoices that are immediately balanced out with allowances.Freezes and Deferment produce no invoices.</xs:documentation>   </xs:annotation>   <xs:complexContent>     <xs:extension base="ClientObject">       <xs:attribute name="processedDate" type="Date" use="optional">         <xs:annotation>           <xs:documentation>processedDate: Date when the charge was processed by the invoicing process.</xs:documentation>         </xs:annotation>       </xs:attribute>       <xs:attribute name="isPrepaid" type="xs:boolean" use="optional">         <xs:annotation>           <xs:documentation>isPrepaid: If true, payment was taken against this charge. This doesn't guaranteethat the invoice created from this charge will be automatically paid</xs:documentation>         </xs:annotation>       </xs:attribute>       <xs:attribute name="type" type="xs:string" use="optional">         <xs:annotation>           <xs:documentation>type: TYpe of charge.</xs:documentation>         </xs:annotation>       </xs:attribute>       <xs:attribute name="index" type="xs:int" use="optional">         <xs:annotation>           <xs:documentation>index: Sequential number of the charge within PaymentPlan. 0 indicates that thecharge will be processed in the next billing process, 1 - the one afterthe next and so on</xs:documentation>         </xs:annotation>       </xs:attribute>       <xs:attribute name="paymentPlan" type="xs:IDREF" use="optional">         <xs:annotation>           <xs:documentation>paymentPlan: Reference to the PaymentPlan holding the charges.</xs:documentation>         </xs:annotation>       </xs:attribute>     </xs:extension>   </xs:complexContent> </xs:complexType>

attribute Charge/@processedDate

type	Date
properties	isRef  0 use  optional
facets	pattern  \d\d\d\d\d\d\d\d
annotation	documentation processedDate: Date when the charge was processed by the invoicing process.
source	<xs:attribute name="processedDate" type="Date" use="optional">   <xs:annotation>     <xs:documentation>processedDate: Date when the charge was processed by the invoicing process.</xs:documentation>   </xs:annotation> </xs:attribute>

attribute Charge/@isPrepaid

type	xs:boolean
properties	isRef  0 use  optional
annotation	documentation isPrepaid: If true, payment was taken against this charge. This doesn't guaranteethat the invoice created from this charge will be automatically paid
source	<xs:attribute name="isPrepaid" type="xs:boolean" use="optional">   <xs:annotation>     <xs:documentation>isPrepaid: If true, payment was taken against this charge. This doesn't guaranteethat the invoice created from this charge will be automatically paid</xs:documentation>   </xs:annotation> </xs:attribute>

attribute Charge/@type

type	xs:string
properties	isRef  0 use  optional
annotation	documentation type: TYpe of charge.
source	<xs:attribute name="type" type="xs:string" use="optional">   <xs:annotation>     <xs:documentation>type: TYpe of charge.</xs:documentation>   </xs:annotation> </xs:attribute>

attribute Charge/@index

type	xs:int
properties	isRef  0 use  optional
annotation	documentation index: Sequential number of the charge within PaymentPlan. 0 indicates that thecharge will be processed in the next billing process, 1 - the one afterthe next and so on
source	<xs:attribute name="index" type="xs:int" use="optional">   <xs:annotation>     <xs:documentation>index: Sequential number of the charge within PaymentPlan. 0 indicates that thecharge will be processed in the next billing process, 1 - the one afterthe next and so on</xs:documentation>   </xs:annotation> </xs:attribute>

attribute Charge/@paymentPlan

type	xs:IDREF
properties	isRef  0 use  optional
annotation	documentation paymentPlan: Reference to the PaymentPlan holding the charges.
source	<xs:attribute name="paymentPlan" type="xs:IDREF" use="optional">   <xs:annotation>     <xs:documentation>paymentPlan: Reference to the PaymentPlan holding the charges.</xs:documentation>   </xs:annotation> </xs:attribute>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy