Choose a version:

TenderTransaction

object

Requires read_orders access scope.

A TenderTransaction represents a transaction with financial impact on a shop's balance sheet. A tender transaction always represents actual money movement between a buyer and a shop. TenderTransactions can be used instead of OrderTransactions for reconciling a shop's cash flow. A TenderTransaction is immutable once created.

Anchor to FieldsFields

Anchor to amountamount •MoneyV2! non-null: The amount and currency of the tender transaction.
Anchor to idid •ID! non-null: A globally-unique ID.
Anchor to orderorder •Order: The order that's related to the tender transaction. This value is null if the order has been deleted.
Anchor to paymentMethodpaymentMethod •String: Information about the payment method used for the transaction.
Anchor to processedAtprocessedAt •DateTime: Date and time when the transaction was processed.
Anchor to remoteReferenceremoteReference •String: The remote gateway reference associated with the tender transaction.
Anchor to testtest •Boolean! non-null: Whether the transaction is a test transaction.
Anchor to transactionDetailstransactionDetails •TenderTransactionDetails: Information about the payment instrument used for the transaction.
Anchor to useruser •StaffMember: The staff member who performed the transaction.

Was this section helpful?

Anchor to QueriesQueries

Anchor to tenderTransactions tenderTransactions •query: Transactions representing a movement of money between customers and the shop. Each transaction records the amount, payment method, processing details, and the associated Order.

Positive amounts indicate customer payments to the merchant. Negative amounts represent refunds from the merchant to the customer. Use the query parameter to filter transactions by attributes such as transaction ID, processing date, and point-of-sale device ID.

Was this section helpful?

Anchor to InterfacesInterfaces

Anchor to Node Node •interface

Was this section helpful?