Component 
SUMMARY: XML REP | DERIVED | USE
DETAIL: DESC | XML SRC | TYPE | ATTR | CHILD
eBay Trading API

complexType "ns:OrderType"
Namespace:
Content:
complex, 48 elements, elem. wildcard
Defined:
globally in Schema in ebaySvc.wsdl; see XML source
Includes:
definitions of 48 elements, elem. wildcard
Used:
Component Diagram
XML Representation Summary
<...>
   
Content: 
</...>
All Direct / Indirect Based Elements (4):
ns:Order (defined in ns:OrderArrayType complexType),
Known Usage Locations
Annotation
This type is used to express the details of an order. An order may contain one or more line items (purchases) from the same buyer. Regardless of how many line items an order has, only one payment is made for the order.

The GetOrders and GetOrderTransactions calls return many of the fields of this type.

The GetItemTransactions and GetSellerTransactions calls will only return order-level details if the IncludeContainingOrder boolean field is included in the call request and set to true.

The AddOrder call is used to combine two or more unpaid order line items (between the same seller and buyer) into a 'Combined Invoice' order. While combining these order line items into one 'Combined Invoice' order, the seller can make adjustments to accepted payment methods, shipping details (including costs), and the total cost of the order. Sometimes, sellers will reduce the cost of shipping if one or more order line items can be shipped together in the same package.

The GetMyeBaySelling call returns order details if the seller wishes to view listings that have sold, and the GetMyeBayBuying call returns order details if the buyer wishes to view items they have won or purchased.
XML Source (w/o annotations (49); see within schema source)
<xs:complexType name="OrderType">
<xs:sequence>
<xs:element minOccurs="0" name="OrderID" type="ns:OrderIDType"/>
<xs:element minOccurs="0" name="OrderStatus" type="ns:OrderStatusCodeType"/>
<xs:element minOccurs="0" name="AdjustmentAmount" type="ns:AmountType"/>
<xs:element minOccurs="0" name="AmountPaid" type="ns:AmountType"/>
<xs:element minOccurs="0" name="AmountSaved" type="ns:AmountType"/>
<xs:element minOccurs="0" name="CheckoutStatus" type="ns:CheckoutStatusType"/>
<xs:element minOccurs="0" name="ShippingDetails" type="ns:ShippingDetailsType"/>
<xs:element minOccurs="0" name="CreatingUserRole" type="ns:TradingRoleCodeType"/>
<xs:element minOccurs="0" name="CreatedTime" type="xs:dateTime"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="PaymentMethods" type="ns:BuyerPaymentMethodCodeType"/>
<xs:element minOccurs="0" name="SellerEmail" type="xs:string"/>
<xs:element minOccurs="0" name="ShippingAddress" type="ns:AddressType"/>
<xs:element minOccurs="0" name="ShippingServiceSelected" type="ns:ShippingServiceOptionsType"/>
<xs:element minOccurs="0" name="Subtotal" type="ns:AmountType"/>
<xs:element minOccurs="0" name="Total" type="ns:AmountType"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="ExternalTransaction" type="ns:ExternalTransactionType"/>
<xs:element minOccurs="0" name="TransactionArray" type="ns:TransactionArrayType"/>
<xs:element minOccurs="0" name="BuyerUserID" type="ns:UserIDType"/>
<xs:element minOccurs="0" name="PaidTime" type="xs:dateTime"/>
<xs:element minOccurs="0" name="ShippedTime" type="xs:dateTime"/>
<xs:element minOccurs="0" name="IntegratedMerchantCreditCardEnabled" type="xs:boolean"/>
<xs:element minOccurs="0" name="BundlePurchase" type="xs:boolean"/>
<xs:element minOccurs="0" name="BuyerCheckoutMessage" type="xs:string"/>
<xs:element minOccurs="0" name="EIASToken" type="xs:string"/>
<xs:element minOccurs="0" name="PaymentHoldStatus" type="ns:PaymentHoldStatusCodeType"/>
<xs:element minOccurs="0" name="PaymentHoldDetails" type="ns:PaymentHoldDetailType"/>
<xs:element minOccurs="0" name="RefundAmount" type="ns:AmountType"/>
<xs:element minOccurs="0" name="RefundStatus" type="xs:string"/>
<xs:element minOccurs="0" name="RefundArray" type="ns:RefundArrayType"/>
<xs:element minOccurs="0" name="IsMultiLegShipping" type="xs:boolean"/>
<xs:element minOccurs="0" name="MultiLegShippingDetails" type="ns:MultiLegShippingDetailsType"/>
<xs:element minOccurs="0" name="MonetaryDetails" type="ns:PaymentsInformationType"/>
<xs:element minOccurs="0" name="PickupDetails" type="ns:PickupDetailsType"/>
<xs:element minOccurs="0" name="PickupMethodSelected" type="ns:PickupMethodSelectedType"/>
<xs:element minOccurs="0" name="SellerUserID" type="ns:UserIDType"/>
<xs:element minOccurs="0" name="SellerEIASToken" type="xs:string"/>
<xs:element minOccurs="0" name="CancelReason" type="xs:token"/>
<xs:element minOccurs="0" name="CancelStatus" type="ns:CancelStatusCodeType"/>
<xs:element minOccurs="0" name="CancelReasonDetails" type="xs:string"/>
<xs:element minOccurs="0" name="ShippingConvenienceCharge" type="ns:AmountType"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="CancelDetail" type="ns:CancelDetailType"/>
<xs:element minOccurs="0" name="LogisticsPlanType" type="xs:token"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="BuyerTaxIdentifier" type="ns:TaxIdentifierType"/>
<xs:element minOccurs="0" name="BuyerPackageEnclosures" type="ns:BuyerPackageEnclosuresType"/>
<xs:element minOccurs="0" name="ExtendedOrderID" type="xs:string"/>
<xs:element minOccurs="0" name="ContainseBayPlusTransaction" type="xs:boolean"/>
<xs:element minOccurs="0" name="eBayCollectAndRemitTax" type="xs:boolean"/>
<xs:element minOccurs="0" name="OrderLineItemCount" type="xs:long"/>
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>
</xs:sequence>
</xs:complexType>
Content Element Detail (all declarations defined in this component; 49/49)
ns:AdjustmentAmount
Type:
ns:AmountType, simple content
This value indicates the dollar amount by which the buyer has adjusted the order total. Adjustments to order costs may include shipping and handling, buyer discounts, or added services. A positive amount indicates the amount is an extra charge being paid to the seller by the buyer. A negative value indicates this amount is a credit given to the buyer by the seller.
Component Diagram
XML Representation Summary
<ns:AdjustmentAmount
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:AdjustmentAmount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="AdjustmentAmount" type="ns:AmountType"/>

ns:AmountPaid
Type:
ns:AmountType, simple content
This value indicates the total amount paid by the buyer for the order. This amount includes the sale price of each line item, shipping and handling charges, additional services, and any sales tax that the seller has applied towards the order. This value is only returned after the buyer has paid for the order.

Note: As of November 2019, for orders subject to eBay 'Collect and Remit' taxes, PayPal has begun distributing order funds to the seller's account with the sales tax included. eBay 'Collect and Remit' tax includes US sales tax for numerous states, and 'Good and Services' tax that is applicable to Australian and New Zealand sellers. This 'Collect and Remit' tax amount for the order will be included in the AmountPaid value. To determine if 'Collect and Remit' taxes were added into AmountPaid value, the user can check for the Transaction.eBayCollectAndRemitTaxes.TaxDetails and the Transaction.Taxes.TaxDetails containers in the response. If both of these containers appear in the response with a TaxDetails.TaxDescription value of SalesTax (in US) or GST (in Australia or New Zealand), the tax amount that the buyer paid is in this amount.

Sellers should be aware that the sales tax that the buyer pays for the order will initially be included when the order funds are distributed to their PayPal account, but that PayPal will pull out the sales tax amount shortly after the payment clears, and will distribute the sales tax to the appropriate taxing authority. Previous to this change, PayPal would strip out the 'Collect and Remit' tax before distributing order funds to the seller's account.

This logic change does not apply to sellers who are in eBay managed payments, so the amount in this field will never reflect any 'Collect and Remit' tax, even if the order is subject to 'Collect and Remit' tax.
Component Diagram
XML Representation Summary
<ns:AmountPaid
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:AmountPaid>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="AmountPaid" type="ns:AmountType"/>

ns:AmountSaved
Type:
ns:AmountType, simple content
This value indicates the amount that the buyer saved on the order due to any discounts (item, shipping, promotional) applied to the purchase, or if the seller 'manually' reduced the order total. This field is always returned even when it is '0.0'.
Component Diagram
XML Representation Summary
<ns:AmountSaved
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:AmountSaved>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="AmountSaved" type="ns:AmountType"/>

ns:BundlePurchase
Type:
xs:boolean, predefined, simple content
Reserved for future use.
XML Representation Summary
<ns:BundlePurchase>
   
Content: 
{ xs:boolean }
</ns:BundlePurchase>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BundlePurchase" type="xs:boolean"/>

ns:BuyerCheckoutMessage
Type:
xs:string, predefined, simple content
This field is returned if the buyer left a message for the seller during checkout.
XML Representation Summary
<ns:BuyerCheckoutMessage>
   
Content: 
{ xs:string }
</ns:BuyerCheckoutMessage>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BuyerCheckoutMessage" type="xs:string"/>

ns:BuyerPackageEnclosures
Type:
This container is returned in GetOrders (and other order management calls) if the 'Pay Upon Invoice' option is being offered to the buyer, and the seller is including payment instructions in the shipping package(s) for the order. The 'Pay Upon Invoice' option is only available on the Germany site.
Component Diagram
XML Representation Summary
<ns:BuyerPackageEnclosures>
   
Content: 
</ns:BuyerPackageEnclosures>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BuyerPackageEnclosures" type="ns:BuyerPackageEnclosuresType"/>

ns:BuyerTaxIdentifier
Type:
ns:TaxIdentifierType, complex content
This container will either consist of VAT or Codice Fiscale taxpayer identification information for the buyer.

It is now required that buyers registered on the Italy site provide their Codice Fiscale ID (similar to the Social Security Number for US citizens) before buying an item on the Italy site.

On the Spain site, a Spanish seller has the option to require that Spanish buyers (registered on Spain site) provide a tax ID before checkout. This option is set by the seller at the account level. Once a Spanish buyer provides a tax ID, this tax ID is associated with his/her account, and once a tax ID is associated with the account, Spanish buyer will be asked to provide the tax ID during checkout on all eBay sites. Buyers with a registered address outside of Spain will not be asked to provide a tax ID during checkout.

This container is only returned for Spanish or Italian sellers when the buyer was asked to provide tax identifier information during checkout. A BuyerTaxIdentifier container will be returned for each tax ID that is associated with the buyer's account.
Component Diagram
XML Representation Summary
<ns:BuyerTaxIdentifier>
   
Content: 
</ns:BuyerTaxIdentifier>
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="BuyerTaxIdentifier" type="ns:TaxIdentifierType"/>

ns:BuyerUserID
Type:
ns:UserIDType, simple content
The eBay user ID of the order's buyer.
XML Representation Summary
<ns:BuyerUserID>
   
Content: 
{ xs:string }
</ns:BuyerUserID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="BuyerUserID" type="ns:UserIDType"/>

ns:CancelDetail
Type:
ns:CancelDetailType, complex content
This container consists of details related to an eBay order that has been cancelled or is in the process of possibly being cancelled. Order cancellation requests can be viewed and managed with the cancellation API calls that are available in the Post Order API.

Note: Only the CancelReason and CancelStatus fields are returned. The CancelDetail container and the CancelReasonDetails field are no longer returned. A seller can use the Search Cancellations method of the Post-Order API to retrieve more details on a cancelled order. If the seller does use this method, they can use the Order ID or Item ID as a filter in the request to retrieve the correct cancellation request.
Component Diagram
XML Representation Summary
<ns:CancelDetail>
   
Content: 
</ns:CancelDetail>
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="CancelDetail" type="ns:CancelDetailType"/>

ns:CancelReason
Type:
xs:token, predefined, simple content
This value indicates the reason why the order cancellation was initiated. This field is only returned if an order cancellation has been initiated by the buyer or seller. Typical buyer-initiated cancellation reasons include 'OrderPlacedByMistake', 'WontArriveInTime', or 'FoundCheaperPrice'. Sellers may initiate an order cancellation on behalf of the buyer. In this scenario, the seller should state the cancellation reason as 'BuyerCancelOrder'. If the seller is cancelling an order because he/she is out of stock on an item, the seller should state the cancellation reason as 'OutOfStock'. Unfortunately, in this scenario, the seller will receive a seller defect for this cancellation reason. See CancelReasonCodeType for the complete list of enumeration values that can be returned in this field.

Note: Only the CancelReason and CancelStatus fields are returned. The CancelDetail container and the CancelReasonDetails field are no longer returned. A seller can use the Search Cancellations method of the Post-Order API to retrieve more details on a cancelled order. If the seller does use this method, they can use the Order ID or Item ID as a filter in the request to retrieve the correct cancellation request.
XML Representation Summary
<ns:CancelReason>
   
Content: 
{ xs:token }
</ns:CancelReason>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CancelReason" type="xs:token"/>

ns:CancelReasonDetails
Type:
xs:string, predefined, simple content
The detailed reason for the cancellation of an eBay order. This field is only returned if it is available when a cancellation request has been made on the order, or if the order is currently going through the cancellation process, or if the order has already been cancelled.

Note: Only the CancelReason and CancelStatus fields are returned. The CancelDetail container and the CancelReasonDetails field are no longer returned. A seller can use the Search Cancellations method of the Post-Order API to retrieve more details on a cancelled order. If the seller does use this method, they can use the Order ID or Item ID as a filter in the request to retrieve the correct cancellation request.
XML Representation Summary
<ns:CancelReasonDetails>
   
Content: 
{ xs:string }
</ns:CancelReasonDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CancelReasonDetails" type="xs:string"/>

ns:CancelStatus
Type:
ns:CancelStatusCodeType, simple content
The current status for the order cancellation request (if it exists for the order). This field is only returned if a cancellation request has been made on the order, or if the order is currently going through the cancellation process, or if the order has already been cancelled.

Note: Only the CancelReason and CancelStatus fields are returned. The CancelDetail container and the CancelReasonDetails field are no longer returned. A seller can use the Search Cancellations method of the Post-Order API to retrieve more details on a cancelled order. If the seller does use this method, they can use the Order ID or Item ID as a filter in the request to retrieve the correct cancellation request.
XML Representation Summary
<ns:CancelStatus>
   
Content: 
{ enumeration of xs:token }
</ns:CancelStatus>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CancelStatus" type="ns:CancelStatusCodeType"/>

ns:CheckoutStatus
Type:
ns:CheckoutStatusType, complex content
This container indicates the current status of the order, including a timestamp that indicates the last time that the status of the order changed. For orders that have been paid for, the Status value will show as Complete.
Component Diagram
XML Representation Summary
<ns:CheckoutStatus>
   
Content: 
</ns:CheckoutStatus>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CheckoutStatus" type="ns:CheckoutStatusType"/>

ns:ContainseBayPlusTransaction
Type:
xs:boolean, predefined, simple content
If true, the order contains a transaction for an item that was purchased under the eBay Plus program. eBay Plus is a premium account option for buyers, which provides benefits such as fast free domestic shipping and free returns on selected items. Top-Rated eBay sellers must opt in to eBay Plus to be able offer the program on qualifying listings. Sellers must commit to next-day delivery of those items.

Note: Currently, eBay Plus is available only to buyers in Germany and Australia.
XML Representation Summary
<ns:ContainseBayPlusTransaction>
   
Content: 
{ xs:boolean }
</ns:ContainseBayPlusTransaction>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ContainseBayPlusTransaction" type="xs:boolean"/>

ns:CreatedTime
Type:
xs:dateTime, predefined, simple content
Timestamp that indicates the date and time that the order was created.

Note: For single line item orders, this timestamp value is often the same as the CreatedDate field in the corresponding Transaction container.
XML Representation Summary
<ns:CreatedTime>
   
Content: 
{ xs:dateTime }
</ns:CreatedTime>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CreatedTime" type="xs:dateTime"/>

ns:CreatingUserRole
Type:
ns:TradingRoleCodeType, simple content
This value indicates whether a 'Combined Invoice' order was initiated/created by the buyer or by the seller. This field is only returned for Combined Invoice orders.

An AddOrder call can be used by a seller or buyer to combine two or more unpaid order line items into a 'Combined Invoice' order. Once two or more line items are successfully combined into one order, the buyer only needs to make one payment (instead of multiple payments - one for each order line item). The CreatingUserRole field is required in the AddOrder call request.

Note: Except for listings that required immediate payment, buyers also may have the opportunity to combine multiple line items (from the same seller) into a 'Combined Invoice' order through the buy/checkout flow. This may include accepted Best Offers or auctions that the buyer wins.
XML Representation Summary
<ns:CreatingUserRole>
   
Content: 
{ enumeration of xs:token }
</ns:CreatingUserRole>
Simple Content
Enumeration:
"Buyer"
 - 
The eBay user is acting as the buyer for the order(s). In GetOrders, this value should be passed into the OrderRole field in the request to retrieve orders in which the calling eBay user is the buyer in the order.
"Seller"
 - 
The eBay user is acting as the seller for the order(s). In GetOrders, this value should be passed into the OrderRole field in the request to retrieve orders in which the calling eBay user is the seller in the order.
"CustomCode"
 - 
This value is reserved for future or internal use.
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CreatingUserRole" type="ns:TradingRoleCodeType"/>

ns:eBayCollectAndRemitTax
Type:
xs:boolean, predefined, simple content
This boolean field is returned as true if one or more line items in the order are subject to a tax (US sales tax or Australian Goods and Services tax) that eBay will collect and remit to the proper taxing authority on the buyer's behalf. This field is also returned if false (not subject to eBay Collect and Remit). A Transaction.eBayCollectAndRemitTaxes container is returned for any order line items subject to such a tax, and the type and amount of this tax is displayed in the Transaction.eBayCollectAndRemitTaxes.TaxDetails container.

Australian 'Goods and Services' tax (GST) is automatically charged to buyers outside of Australia when they purchase items on the eBay Australia site. Sellers on the Australia site do not have to take any extra steps to enable the collection of GST, as this tax is collected by eBay and remitted to the Australian government. For more information about Australian GST, see the Taxes and import charges help topic.

As of April 1, 2020, buyers in 40 US states will automatically be charged sales tax for eBay purchases, and are subject to eBay Collect and Remit Tax. eBay will collect and remit this sales tax to the proper taxing authority on the buyer's behalf. Sellers do not have to take any extra steps to enable the collection of this sales tax. If the seller is employing a Sales Tax Table for the listing, and a sales tax rate is established for a state that is subject to 'eBay Collect and Remit', this sales tax rate will be ignored by eBay. For a list of the US states that are or will become subject to 'eBay Collect and Remit Tax' (and effective dates), see the eBay sales tax collection help topic.
XML Representation Summary
<ns:eBayCollectAndRemitTax>
   
Content: 
{ xs:boolean }
</ns:eBayCollectAndRemitTax>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="eBayCollectAndRemitTax" type="xs:boolean"/>

ns:EIASToken
Type:
xs:string, predefined, simple content
Unique identifier for the user that does not change when the eBay user name is changed. Use when an application needs to associate a new eBay user name with the corresponding eBay user.

Since a bidder's user info is anonymous, this tag will be returned only to that bidder, and to the seller of an item that the user is bidding on.
XML Representation Summary
<ns:EIASToken>
   
Content: 
{ xs:string }
</ns:EIASToken>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="EIASToken" type="xs:string"/>

ns:ExtendedOrderID
Type:
xs:string, predefined, simple content
A unique identifier for an eBay order in the new eBay REST API model. ExtendedOrderID values will be used to identify orders in REST-based APIs, including the Post-Order API and the Fulfillment API.

For GetOrders, GetOrderTransactions, and GetItemTransactions only: If using Trading WSDL Version 1019 or above, this field will only be returned to the buyer or seller, and no longer returned at all to third parties. If using a Trading WSDL older than Version 1019, the correct Order ID is returned to the buyer or seller, but a dummy Order ID value of 1000000000000 will be returned to all third parties.

Note: As of June 2019, eBay has changed the format of order identifier values, and this new format is relevant to both legacy and REST API-based order ID fields. The new format is a non-parsable string, globally unique across all eBay marketplaces, and consistent for both single line item and multiple line item orders. Unlike in the past, instead of just being known and exposed to the seller, these unique order identifiers will also be known and used/referenced by the buyer and eBay customer support.

For developers and sellers who are already integrated with the Trading API's order management calls, this change shouldn't impact your integration unless you parse the existing order identifiers (e.g., OrderID or OrderLineItemID), or otherwise infer meaning from the format (e.g., differentiating between a single line item order versus a multiple line item order). Because we realize that some integrations may have logic that is dependent upon the old identifier format, eBay is rolling out this Trading API change with version control to support a transition period of approximately 9 months before applications must switch to the new format completely.

During the transition period, for developers/sellers using a Trading WSDL older than Version 1113, they can use the X-EBAY-API-COMPATIBILITY-LEVEL HTTP header in API calls to control whether the new or old OrderID format is returned in call response payloads. To get the new OrderID format, the value of the X-EBAY-API-COMPATIBILITY-LEVEL HTTP header must be set to 1113. During the transition period and even after, the new and old OrderID formats will still be supported/accepted in all Trading API call request payloads. After the transition period (which will be announced), only the new OrderID format will be returned in all Trading API call response payloads, regardless of the Trading WSDL version used or specified compatibility level.
XML Representation Summary
<ns:ExtendedOrderID>
   
Content: 
{ xs:string }
</ns:ExtendedOrderID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ExtendedOrderID" type="xs:string"/>

ns:ExternalTransaction
Type:
Container consisting of payment details for an eBay order, including an identifier for the monetary transaction and a field to express any fees or credits applied to the monetary transaction. This field is only returned after payment for the order has occurred.

Note: The MonetaryDetails container also shows payment information for the order. In the future, it is possible that the ExternalTransaction container will be deprecated, so you are encouraged to start using MonetaryDetails as soon as possible.
Component Diagram
XML Representation Summary
<ns:ExternalTransaction>
   
Content: 
</ns:ExternalTransaction>
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="ExternalTransaction" type="ns:ExternalTransactionType"/>

ns:IntegratedMerchantCreditCardEnabled
Type:
xs:boolean, predefined, simple content
This field being returned with a value of true indicates that the order can be paid for with a credit card through the seller's payment gateway account.

Note: As of May 1, 2019, eBay no longer supports electronic payments through Integrated Merchant Credit Card accounts. To accept online credit card payments from buyers, a seller must specify PayPal as an accepted payment method, or opt in to eBay managed payments program (if the program is available to that seller).

Note: For the GetItemTransactions, GetOrders, and GetOrderTransactions calls, this field is only returned to the seller of the order; this field is not returned for the buyer or third party.
XML Representation Summary
<ns:IntegratedMerchantCreditCardEnabled>
   
Content: 
{ xs:boolean }
</ns:IntegratedMerchantCreditCardEnabled>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="IntegratedMerchantCreditCardEnabled" type="xs:boolean"/>

ns:IsMultiLegShipping
Type:
xs:boolean, predefined, simple content
If IsMultilegShipping is true, at least one order line item in the order will not be shipped directly to the buyer. Instead, the item(s) may be shipped to eBay's Global Shipping Program (GSP) partner who will handle the international leg of shipment, or the item may be shipped to eBay's Authenticity Guarantee service partner if the item is subject to the Authenticity Guarantee service program. In both cases, the partner's shipping address can be found in the MultiLegShippingDetails.SellerShipmentToLogisticsProvider.ShipToAddress container.

If an order line item is subject to the Authenticity Guarantee service, the Transaction.Program container will be returned.
XML Representation Summary
<ns:IsMultiLegShipping>
   
Content: 
{ xs:boolean }
</ns:IsMultiLegShipping>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="IsMultiLegShipping" type="xs:boolean"/>

ns:LogisticsPlanType
Type:
xs:token, predefined, simple content
This field will be returned at the order level only if the buyer purchased a digital gift card, which is delivered by email, or if the buyer purchased an item that is enabled with the 'Click and Collect' feature.

Currently, LogisticsPlanType has two applicable values: PickUpDropOff, which indicates that the buyer selected the 'Click and Collect' option. With Click and Collect, buyers are able to purchase from thousands of sellers on the eBay UK and Australia sites, and then pick up their order from the nearest 'eBay Collection Point', including over 750 Argos stores in the UK. The Click and Collect feature is only available on the eBay UK and Australia sites; or, DigitalDelivery, which indicates that the order is a digital gift card that will be delivered to the buyer or recipient of the gift card by email.
XML Representation Summary
<ns:LogisticsPlanType>
   
Content: 
{ xs:token }
</ns:LogisticsPlanType>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="LogisticsPlanType" type="xs:token"/>

ns:MonetaryDetails
Type:
Contains information about each monetary transaction that occurs for the order, including order payment, any refund, a credit, etc. Both the payer and payee are shown in this container.

Note: MonetaryDetails can already be used instead of the older ExternalTransaction container, and the ExternalTransaction container may eventually get deprecated. Due to this possibility, you are encouraged to start using MonetaryDetails as soon as it is convenient.
Component Diagram
XML Representation Summary
<ns:MonetaryDetails>
   
Content: 
</ns:MonetaryDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="MonetaryDetails" type="ns:PaymentsInformationType"/>

ns:MultiLegShippingDetails
Type:
This container consists of details about the domestic leg of a Global Shipping Program (GSP) shipment or shipment to eBay's Authenticity Guarantee service partner. With GSP, the shipment has a domestic leg and an international leg. In the domestic leg, the seller ships the item to eBay's shipping partner. In the Authenticity Guarantee service, the seller ships the item to the authentication partner, and if the item passes an authentication inspection, the authentication partner ships it directly to the buyer.

This container is only returned if the order has one or more order line items that require shipping through GSP or shipment to an Authenticity Guarantee service partner. It is not returned if IsMultilegShipping is false.
Component Diagram
XML Representation Summary
<ns:MultiLegShippingDetails>
   
Content: 
</ns:MultiLegShippingDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="MultiLegShippingDetails" type="ns:MultiLegShippingDetailsType"/>

ns:OrderID
Type:
ns:OrderIDType, simple content
A unique identifier for a single or multiple line item eBay order. In the ContainingOrder container of a GetItemTransactions or GetSellerTransactions response, this identifier identifies the parent order of the order line item. A single buyer payment is made for each order.

For order management calls only: This field is returned with the correct order ID only to the buyer, the seller, and PayPal (if PayPal is the payment method). For third parties (except PayPal):
  • If using a Trading WSDL older than version 1019, the Order ID will be returned to third parties as dummy data in the form of 1000000000000 or 1000000000000-1000000000000.
  • If using Trading WSDL version 1019 or newer, the Order ID will be returned to third parties as an empty field (<OrderID/>).


Note: In June 2019, eBay introduced a new order ID format, but allowed developers/sellers to decide whether to immediately adopt the new format, or to continue working with the old format. Users who wanted to adopt the new format, could either use a Trading WSDL Version 1113 (or newer), or they could even use an older Trading WSDL but set the X-EBAY-API-COMPATIBILITY-LEVEL HTTP header value to 1113 in API calls. Beginning in June 2020, only the new order ID format will be returned in response payloads for paid orders, regardless of the WSDL version number or compatibility level.

Note that the unique identifier of a 'non-immediate payment' order will change as it goes from an unpaid order to a paid order. Due to this scenario, all calls that accept Order ID values as filters in the request payload, including the GetOrders and GetOrderTransactions calls, will support the identifiers for both unpaid and paid orders. The new order ID format is a non-parsable string, globally unique across all eBay marketplaces, and consistent for both single line item and multiple line item orders. Unlike in the past, instead of just being known and exposed to the seller, these unique order identifiers will also be known and used/referenced by the buyer and eBay customer support.

Sellers can check to see if an order has been paid by looking for a value of 'Complete' in the CheckoutStatus.Status field in the response of GetOrders or GetOrderTransactions call, or in the Status.CompleteStatus field in the response of GetItemTransactions or GetSellerTransactions call. Sellers should not fulfill orders until buyer has made payment.
XML Representation Summary
<ns:OrderID>
   
Content: 
{ xs:string }
</ns:OrderID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="OrderID" type="ns:OrderIDType"/>

ns:OrderLineItemCount
Type:
xs:long, predefined, simple content
This field indicates the total number of line items in the order. This field is returned under the ContainingOrder container of a GetItemTransactions or GetSellerTransactions call. In order for the ContainingOrder container to be returned, a user must include the IncludeContainingOrder field in the call request and set its value to true.

Note: This field is automatically returned if the user is using Version 1113 of the Trading WSDL (or newer, as versions roll out). If the user is using Versions 1107 or 1111 of the Trading WSDL, this field will only be returned if the user includes the X-EBAY-API-COMPATIBILITY-LEVEL HTTP header and sets its value to 1113. If a user is using a Trading WSDL older than 1107, this field will not be returned.
XML Representation Summary
<ns:OrderLineItemCount>
   
Content: 
{ xs:long }
</ns:OrderLineItemCount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="OrderLineItemCount" type="xs:long"/>

ns:OrderStatus
Type:
ns:OrderStatusCodeType, simple content
This enumeration value indicates the current status of the order.
XML Representation Summary
<ns:OrderStatus>
   
Content: 
{ enumeration of xs:token }
</ns:OrderStatus>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="OrderStatus" type="ns:OrderStatusCodeType"/>

ns:PaidTime
Type:
xs:dateTime, predefined, simple content
Timestamp indicating the date and time of order payment. This field is not returned until payment has been made by the buyer.

This time is specified in GMT (not Pacific time). See eBay Features Guide for information about converting between GMT and other time zones.
XML Representation Summary
<ns:PaidTime>
   
Content: 
{ xs:dateTime }
</ns:PaidTime>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PaidTime" type="xs:dateTime"/>

ns:PaymentHoldDetails
Type:
ns:PaymentHoldDetailType, complex content
This container consists of information related to the payment hold on the order, including the reason why the buyer's payment for the order is being held, the expected release date of the funds into the seller's account, and possible action(s) the seller can take to expedite the payout of funds into their account. This container is only returned if a payment hold has placed on the order.

See PaymentHoldReasonCodeType for some details on why/when a seller's funds may be held, or visit the Pending payments help topic for more information on eBay's payment hold policies.
Component Diagram
XML Representation Summary
<ns:PaymentHoldDetails>
   
Content: 
</ns:PaymentHoldDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PaymentHoldDetails" type="ns:PaymentHoldDetailType"/>

ns:PaymentHoldStatus
Type:
This field indicates the type and/or status of a payment hold on the item. It is always returned for GetOrders and GetOrderTransactions, even if there are no payment holds (in which case, an enumeration value of None is shown).

Note: For the GetItemTransactions, GetOrders, and GetOrderTransactions calls, this field is only returned to the seller of the order; this field is not returned for the buyer or third party.
XML Representation Summary
<ns:PaymentHoldStatus>
   
Content: 
{ enumeration of xs:token }
</ns:PaymentHoldStatus>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PaymentHoldStatus" type="ns:PaymentHoldStatusCodeType"/>

ns:PaymentMethods
Type:
In GetOrders, GetOrderTransactions, and OrderReport, a PaymentMethods field will appear for each payment method available to the buyer for the order's purchase. However, once the buyer pays for the order, any and all of these PaymentMethods fields will stop being returned, and instead, the actual payment method used will be returned in the PaymentMethod field of the CheckoutStatus container.

In an AddOrder call, the seller can use one or more PaymentMethods fields to override whatever available payment methods were already defined for each individual line item. For sellers opted in to eBay managed payments, only the CreditCard enumeration value should be passed into this field or the call may fail.

Note: For sellers in the eBay managed payments program, the enumeration value returned in this field will be CreditCard, regardless of which payment method that the buyer used (or is planning to use).

Similarly, for an AddOrder call, a seller opted in to eBay managed payments should only pass a value of CreditCard into this field.

eBay managed payments is currently available to a select set of sellers. For the current list of eBay marketplaces in which eBay managed payments has rolled out, see the eBay Managed Payments landing page. For sellers in the eBay managed payments program, a payment method does not need to be specified at listing/checkout time.

Note: As of May 1, 2019, eBay no longer supports electronic payments through a seller's Integrated Merchant Credit Card account. To accept online credit card payments from buyers, a seller must either specify PayPal as an accepted payment method, or opt in to the eBay managed payments program. If IMCC is passed in as a value, this value will be ignored and dropped (and listing will possibly get blocked if IMCC is the only specified payment method).
XML Representation Summary
<ns:PaymentMethods>
   
Content: 
{ enumeration of xs:token }
</ns:PaymentMethods>
Simple Content
Enumeration:
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="PaymentMethods" type="ns:BuyerPaymentMethodCodeType"/>

ns:PickupDetails
Type:
ns:PickupDetailsType, complex content
Container consisting of an array of PickupOptions containers. Each PickupOptions container consists of the pickup method and its priority. The priority of each pickup method controls the order (relative to other pickup methods) in which the corresponding pickup method will appear in the View Item and Checkout page.

For GetOrders and GetOrderTransactions, this container is always returned prior to order payment if the seller created/revised/relisted the item with the EligibleForPickupInStore and/or EligibleForPickupDropOff flag in the call request set to 'true'. If and when the In-Store pickup method (US only) or 'Click and Collect' pickup method (UK and Australia only) is selected by the buyer and payment for the order is made, this container will no longer be returned in the response, and will essentially be replaced by the PickupMethodSelected container.

Note: A seller must be eligible for the In-Store Pickup feature or Click and Collect feature to list an item that is eligible for In-Store Pickup or Click and Collect. At this time, the In-Store Pickup and Click and Collect features are generally only available to large retail merchants, and can only be applied to multiple-quantity, fixed-price listings.
Component Diagram
XML Representation Summary
<ns:PickupDetails>
   
Content: 
</ns:PickupDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PickupDetails" type="ns:PickupDetailsType"/>

ns:PickupMethodSelected
Type:
Container consisting of details related to the selected pickup method, including the pickup method type, the merchant's store ID, the status of the pickup, and the pickup reference code (if provided by merchant).

This container is only returned when the buyer has selected the In-Store Pickup or Click and Collect option and has paid for the order. All fields in the PickupMethodSelected container are static, except for the PickupStatus field, which can change states based on the notifications that a merchant sends to eBay through the Inbound Notifications API.

Note: A seller must be eligible for the In-Store Pickup or Click and Collect feature to list an item that is eligible for these features. At this time, the In-Store Pickup and Click and Collect features are generally only available to large retail merchants, and can only be applied to multiple-quantity, fixed-price listings.
Component Diagram
XML Representation Summary
<ns:PickupMethodSelected>
   
Content: 
</ns:PickupMethodSelected>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PickupMethodSelected" type="ns:PickupMethodSelectedType"/>

ns:RefundAmount
Type:
ns:AmountType, simple content
The amount of the refund due to, or already issued to the buyer for the order. This field is only returned in GetMyeBaySelling if a buyer refund is due, or was issued for the order.
Component Diagram
XML Representation Summary
<ns:RefundAmount
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:RefundAmount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="RefundAmount" type="ns:AmountType"/>

ns:RefundArray
Type:
ns:RefundArrayType, complex content
Note: This container was only used for Half.com orders, and since the Half.com site was taken down, this container is no longer applicable.
Component Diagram
XML Representation Summary
<ns:RefundArray>
   
Content: 
</ns:RefundArray>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="RefundArray" type="ns:RefundArrayType"/>

ns:RefundStatus
Type:
xs:string, predefined, simple content
This string value indicates the result of a seller's refund to the buyer. Its value are 'Success', 'Failure' or 'Pending'. This field is only returned in GetMyeBaySelling if the buyer has received a refund from the seller, or is due to receive a refund.
XML Representation Summary
<ns:RefundStatus>
   
Content: 
{ xs:string }
</ns:RefundStatus>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="RefundStatus" type="xs:string"/>

ns:SellerEIASToken
Type:
xs:string, predefined, simple content
This is a unique identifier for the seller that does not change when the eBay user name is changed. This is useful when an application needs to associate a new eBay user name with the corresponding eBay user.

Note: For the GetOrders call, this field is only returned to the seller of the order; this field is not returned for the buyer or third party.
XML Representation Summary
<ns:SellerEIASToken>
   
Content: 
{ xs:string }
</ns:SellerEIASToken>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SellerEIASToken" type="xs:string"/>

ns:SellerEmail
Type:
xs:string, predefined, simple content
The email address of the seller involved in the order. The email address of the seller is only returned if it is the same seller making the call.

Note: For the GetOrders and GetOrderTransactions calls, this field is only returned to the seller of the order; this field is not returned for the buyer or third party.
XML Representation Summary
<ns:SellerEmail>
   
Content: 
{ xs:string }
</ns:SellerEmail>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SellerEmail" type="xs:string"/>

ns:SellerUserID
Type:
ns:UserIDType, simple content
This is the eBay user ID of the order's seller.
XML Representation Summary
<ns:SellerUserID>
   
Content: 
{ xs:string }
</ns:SellerUserID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SellerUserID" type="ns:UserIDType"/>

ns:ShippedTime
Type:
xs:dateTime, predefined, simple content
Timestamp indicating the date and time of order shipment. This field is not returned until shipment tracking is provided for all line items in the order, or if the order has been marked as 'shipped' by the seller.

This time is specified in GMT (not Pacific time). See eBay Features Guide for information about converting between GMT and other time zones.
XML Representation Summary
<ns:ShippedTime>
   
Content: 
{ xs:dateTime }
</ns:ShippedTime>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ShippedTime" type="xs:dateTime"/>

ns:ShippingAddress
Type:
ns:AddressType, complex content
This container shows the shipping address for the order.

Note: For an Authenticity Guarantee program shipment, this is the address of the authenticator's warehouse. The authenticator is responsible for delivery to the buyer's shipping address. Note: For GetOrderTransactions, the buyer's shipping address may also be returned at the order line item level in the Transaction.Buyer.BuyerInfo.ShippingAddress container.
Component Diagram
XML Representation Summary
<ns:ShippingAddress>
   
Content: 
</ns:ShippingAddress>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ShippingAddress" type="ns:AddressType"/>

ns:ShippingConvenienceCharge
Type:
ns:AmountType, simple content
Note: This field is no longer applicable/used. It was previously used for eBay Now and 'eBay On Demand Delivery' orders - two features that have been deprecated.
Component Diagram
XML Representation Summary
<ns:ShippingConvenienceCharge
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:ShippingConvenienceCharge>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ShippingConvenienceCharge" type="ns:AmountType"/>

ns:ShippingDetails
Type:
ns:ShippingDetailsType, complex content
Container consisting of order-level shipping details. More shipping-related details can be found at the line item level for each line item in the order.

In an AddOrder call, the seller can use the ShippingDetails container to make adjustments to shipping details, including the available shipping service options and shipping cost. Sometimes, sellers will reduce the cost of shipping if one or more order line items can be shipped together in the same package.
Component Diagram
XML Representation Summary
<ns:ShippingDetails>
   
Content: 
</ns:ShippingDetails>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ShippingDetails" type="ns:ShippingDetailsType"/>

ns:ShippingServiceSelected
Type:
Container consisting of details about the domestic or international shipping service selected by the buyer for delivery of the order. Note that more shipping service information may be returned at the order line item level in the Transaction.ShippingServiceSelected container.
Component Diagram
XML Representation Summary
<ns:ShippingServiceSelected>
   
Content: 
</ns:ShippingServiceSelected>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ShippingServiceSelected" type="ns:ShippingServiceOptionsType"/>

ns:Subtotal
Type:
ns:AmountType, simple content
The cumulative item cost for all line items in the order. This value does not take into account any shipping/handling costs, sales tax costs, or any discounts. For a single line item order, the amount in this field should be the same as the amount in the Transaction.TransactionPrice field. For a multiple line item order, the amount in this field should equal the cumulative amount of each Transaction.TransactionPrice fields for each order line item.
Component Diagram
XML Representation Summary
<ns:Subtotal
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:Subtotal>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Subtotal" type="ns:AmountType"/>

ns:Total
Type:
ns:AmountType, simple content
The Total amount shows the total cost for the order, including total item cost (shown in Subtotal field), shipping charges (shown in ShippingServiceSelected.ShippingServiceCost field), and seller-applied sales tax (shown in SalesTax.SalesTaxAmount field).

In an AddOrder call, the seller can pass in the Total amount for the 'Combined Invoice' order, and this is what the buyer will be expected to pay for the order.

Note: As of November 2019, for orders subject to eBay 'Collect and Remit' taxes, PayPal has begun distributing order funds to the seller's account with the sales tax included. eBay 'Collect and Remit' tax includes US sales tax for numerous states, and 'Good and Services' tax that is applicable to Australian and New Zealand sellers. This 'Collect and Remit' tax amount for the order will be included in the Total value. To determine if 'Collect and Remit' taxes were added into Total value, the user can check for the Transaction.eBayCollectAndRemitTaxes.TaxDetails and the Transaction.Taxes.TaxDetails containers in the response. If both of these containers appear for one or more transactions in the response with a TaxDetails.TaxDescription value of SalesTax (in US) or GST (in Australia or New Zealand), the tax amount that the buyer paid is in this amount. For a multiple line item order, the seller will need to look at and add up the TaxDetails.TaxAmount values for each line item to see how much sales tax is applicable for the whole order.

Sellers should be aware that the sales tax that the buyer pays for the order will initially be included when the order funds are distributed to their PayPal account, but that PayPal will pull out the sales tax amount shortly after the payment clears, and will distribute the sales tax to the appropriate taxing authority. Previous to this change, PayPal would strip out the 'Collect and Remit' tax before distributing order funds to the seller's account.

This logic change does not apply to sellers who are in eBay managed payments, so the amount in this field will never reflect any 'Collect and Remit' tax, even if the order is subject to 'Collect and Remit' tax.
Component Diagram
XML Representation Summary
<ns:Total
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:Total>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Total" type="ns:AmountType"/>

ns:TransactionArray
Type:
ns:TransactionArrayType, complex content
Container consisting of one or more line items that comprise an order. The data for each order line item in the order is stored in a separate Transaction container.

Under the TransactionArray container in an AddOrder call, a seller or buyer specifies two or more (up to 40) order line items into a 'Combined Invoice' order.
Component Diagram
XML Representation Summary
<ns:TransactionArray>
   
Content: 
</ns:TransactionArray>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="TransactionArray" type="ns:TransactionArrayType"/>

{any element from any namespace}
XML Source (see within schema source)
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>

 Component 
SUMMARY: XML REP | DERIVED | USE
DETAIL: DESC | XML SRC | TYPE | ATTR | CHILD
eBay Trading API

WSDL documentation generated with FlexDoc/XML 1.13 using FlexDoc/XML WSDLDoc 1.2.5 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit.