OptionalcostIf present, users have to accept this message before creating an order. May contain (some) HTML. If accepting the costs and performing the order is one click (which is allowed), the create order button label must contain the information that costs are accepted.
OptionalcostLink to the broker's cost statement document. See "Cost statement" above for how to present it.
OptionalentryEntry costs for the order.
OptionalexpectedExpected counter value (Kurswert) when the order is executed.
OptionalorderOrder fees ("Orderkosten": sum of commission, exchange fees and brokerage).
OptionalorderExplanation for orderFees (plain text), e.g. to be displayed as a tooltip or below the order fees.
OptionaltotalThe total amount spent for this order.
OptionaltransactionFinancial transaction tax.
Result of a cost estimation ("Ex-ante Kosteninformation"), as returned by
PreparedInstrument.estimateOrderCostsandQuote.estimateOrderCosts.All fields are optional; brokers only fill what they know. The summary fields (
orderFees,expectedCounterValue,transactionTax, ...) should be displayed as early as possible, so the estimation should be requested as soon as the order is prepared or the quote has been received.Cost statement ("Kostenausweis")
A broker provides its full cost statement in one of two ways:
costDetailsLinkof this estimation, orbuildDetailedOrderCostEstimationToken(ofPreparedInstrumentorQuote) andgetDetailedCostEstimationTableof the session. The table itself may consist of only adetailsLink.Both are alternative ways to the same cost statement. Frontends must display exactly one "Kostenausweis" entry, which is visible if
costDetailsLink.urlis set or a token can be built. When the user clicks it:costDetailsLink.urlis set, open that URL,getDetailedCostEstimationTable. Only load it at this point, as it sends another request to the broker. If the table hasrowsorfooterHtml, display it; if it only hasdetailsLink.url, open that URL.