Represents a service charge applied to an order.
A unique ID that identifies the service charge only within this order.
The version of the catalog object that this service charge references.
The service charge percentage as a string representation of a
decimal number. For example,
"7.25" indicates a service charge of 7.25%.
Exactly 1 of
amount_money should be set.
The amount of a non-percentage-based service charge.
Exactly one of
amount_money should be set.
Read only The amount of money applied to the order by the service charge, including any inclusive tax amounts, as calculated by Square.
- For fixed-amount service charges,
applied_moneyis equal to
- For percentage-based service charges,
applied_moneyis the money calculated using the percentage.
Read only The total amount of money to collect for the service charge.
Note: If an inclusive tax is applied to the service charge,
total_money does not equal
because the inclusive tax amount is already included in both
Read only The total amount of tax money to collect for the service charge.
The calculation phase at which to apply the service charge.
Indicates whether the service charge can be taxed. If set to
order-level taxes automatically apply to the service charge. Note that
service charges calculated in the
TOTAL_PHASE cannot be marked as taxable.
The list of references to the taxes applied to this service charge. Each
OrderLineItemAppliedTax has a
tax_uid that references the
uid of a top-level
OrderLineItemTax that is being applied to this service charge. On reads, the amount applied
OrderLineItemAppliedTax is automatically created on every taxable service charge
ORDER scoped taxes that are added to the order.
LINE_ITEM scoped taxes must be added in requests for the tax to apply to any taxable
service charge. Taxable service charges have the
taxable field set to
true and calculated
To change the amount of a tax, modify the referenced top-level tax.
Application-defined data attached to this service charge. Metadata fields are intended to store descriptive references or associations with an entity in another system or store brief information about the object. Square does not process this field; it only stores and returns it in relevant API calls. Do not use metadata to store any sensitive information (such as personally identifiable information or card details).
Keys written by applications must be 60 characters or less and must be in the character set
[a-zA-Z0-9_-]. Entries can also include metadata generated by Square. These keys are prefixed
with a namespace, separated from the key with a ':' character.
Values have a maximum length of 255 characters.
An application can have up to 10 entries per metadata field.
Entries written by applications are private and can only be read or modified by the same application.
For more information, see Metadata.