TenderTransactionResponse

Information about a tender transaction from the tender provider. The Toast POS system uses this information to complete guests' tender transactions.

The set of information in this object depends on the tender transaction type. The transaction type is specified in the Toast-Transaction-Type header parameter for the request.

All TenderTransactionResponse objects must include a transactionStatus value.

The TenderTransactionResponse object includes the following values for specific transaction types:

  • TENDER_RETRIEVE_DISCOUNTS - includes a discountsResponse value.
  • TENDER_RETRIEVE_PAYMENTS - includes a paymentsResponse value.
  • TENDER_REDEEM - no additional fields
  • TENDER_GRATUITY - includes a gratuityResponse value.
  • TENDER_REVERSE - no additional fields.
  • TENDER_SEARCH_CONFIG - includes a searchConfigResponse value.
  • TENDER_SEARCH - includes an searchResponse value.
object (TransactionResponseDiscounts)

A list of discounts that apply to the given check with the given account identifier.

object (TransactionResponseGratuity)

Response to a request to update the gratuity amount on an already tendered payment.

object (TransactionResponsePayments)

A list of discounts that apply to the given check with the given account identifier.

object (TransactionResponseSearchConfig)

A list of search terms supported by the tender provider. This will populate the list of search terms displayed by the Toast POS system when a search is requested.

object (TransactionResponseSearch)

A list of accounts matching the search terms submitted as part of a search request.

transactionStatus
string

Indicates the result of a tender transaction, reported by the tender service provider. This property must be present on all responses. Possible values are:

  • `ACCEPT` - The tender service provider processed the transaction successfully.
  • `ERROR_INVALID_TOAST_TRANSACTION_TYPE` - The requested Toast-Transaction-Type is not valid.
  • `ERROR_INVALID_INPUT_PROPERTIES` - The specified JSON properties in the request body are not valid.
  • `ERROR_INVALID_TOKEN` - The token supplied in the `Authorization` header field is invalid or cannot be validated.
  • `ERROR_INVALID_RESTAURANT` - The restaurant specified by the `Toast-Restaurant-External-ID` is invalid.
  • `ERROR_ACCOUNT_INVALID` - The tender identifier provided did not correspond to an account, or the account is not valid at the current restaurant.
  • `ERROR_ACCOUNT_NO_POST` - The tender identifier provided corresponded to an account which has no card on file or has been marked as "no post".
  • `ERROR_FOLIO_IN_USE` - Some property management systems limit guest folio access to one source at a time. If the front desk agent is using the property management system to access a guest folio, it may be locked and therefore unavailable for room charge posting during that time.
  • `ERROR_INSUFFICIENT_FUNDS` - The payment or tip, specified in TENDER_RETRIEVE_PAYMENTS or TENDER_RETRIEVE_GRATUITY, cannot be retrieved because the tender account does not have sufficient balance.
  • `ERROR_UNABLE_TO_PROCESS` - The transaction cannot be processed by the partner.
  • `ERROR_TRANSACTION_DOES_NOT_EXIST` - The transaction that is being requested to be reversed or updated does not exist. Only occurs on a `TENDER_REVERSE` or `TENDER_GRATUITY` response.
  • `ERROR_TRANSACTION_CANNOT_BE_REVERSED` - The specified transaction cannot be reversed. Only `TENDER_REDEEM` and `TENDER_GRATUITY` transactions can be reversed.
Enum: "ACCEPT" "ERROR_INVALID_TOAST_TRANSACTION_TYPE" "ERROR_INVALID_INPUT_PROPERTIES" "ERROR_INVALID_TOKEN" "ERROR_INVALID_RESTAURANT" "ERROR_TRANSACTION_DOES_NOT_EXIST" "ERROR_TRANSACTION_CANNOT_BE_REVERSED" "ERROR_ACCOUNT_INVALID" "ERROR_ACCOUNT_NO_POST" "ERROR_FOLIO_IN_USE" "ERROR_INSUFFICIENT_FUNDS" "ERROR_UNABLE_TO_PROCESS"
{
  • "transactionStatus": "ACCEPT",
  • "searchConfigResponse": {
    },
  • "searchResponse": {
    },
  • "discountsResponse": {
    },
  • "paymentsResponse": {
    },
  • "gratuityResponse": {
    }
}