Transactions API will be deprecated on May 3, 2023, ahead of the Conversational Actions sunset on June 13, 2023. For more information, see Conversational Actions sunset.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[[["This documentation describes the `TransactionRequirementsCheckSpec` type, which is deprecated and part of the Orders version 2 API."],["Developers should migrate to Orders version 3 and refer to the provided migration guide for assistance."],["`TransactionRequirementsCheckSpec` is used with the `actions.intent.TRANSACTION_REQUIREMENTS_CHECK` and includes order and payment options."],["This type is input for the `actions.intent.TRANSACTION_REQUIREMENTS_CHECK` intent within the deprecated Orders v2 API."],["It contains details about order and payment options, represented by the `orderOptions` and `paymentOptions` fields respectively."]]],["This document details the JSON representation and fields for a deprecated API input, `actions.intent.TRANSACTION_REQUIREMENTS_CHECK`. The input consists of two key fields: `orderOptions` and `paymentOptions`. `orderOptions` contains options related to the order, while `paymentOptions` includes payment details or is empty if no payment is involved. This information is part of the deprecated Orders version 2 API, and users are directed to a migration guide for version 3.\n"]]
