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.
Stay organized with collections
Save and categorize content based on your preferences.
If you're having trouble fulfilling transaction intents with your Action, see if
you're experiencing any of the symptoms described in the following sections and
take the recommended troubleshooting steps.
Action not responding
Symptom: When checking for transaction requirements or decision of the user,
the user gets back a response of "App isn't responding at the moment. Try again soon."
Troubleshooting: Ensure your Action project has all the required directory information, including a privacy policy link.
Unable to process receipt
Symptom: During purchase authorization, the user gets a response saying
"Sorry, I am unable to process your receipt."
Troubleshooting:
Make sure your merchantOrderId is unique. A new order can't be placed
with a previous, existing order ID.
Make sure you're sending a simple response
alongside the initial orderUpdate; this is the mandatory response format.
Unable to send order updates
Symptom: When sending an order update for an existing order, the Orders API
responds with error code 500 and the following error message: "Order OrderID
for project ProjectID could not be updated. Please try again."
Symptom: Initial order is placed and follow-up order updates succeed with
status code 200 but don't appear as push notifications on the user's Assistant-enabled
device.
Troubleshooting: Not all order updates will be reflected as a push notification;
only updates with a status of CANCELLED, FULFILLED, REJECTED, or RETURNED
result in a notification.
View transactions on your account
You can view transactions that have been made through your account by following these steps:
You can also view sandbox transactions by adding the following URL query parameter:
myaccount.google.com/purchases?sandbox=1
Other troubleshooting tips
If the above symptoms don't describe the problem you're running into, you may
want to refer to your project's Stackdriver logs
for further troubleshooting. You can also refer to your Google Account settings
to view and manage any purchases you've made with your Action.
[[["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."],[[["\u003cp\u003eTransaction functionalities for Conversational Actions are unavailable in Denmark, France, Germany, Italy, the Netherlands, Norway, Poland, Spain, and Sweden due to regulatory requirements.\u003c/p\u003e\n"],["\u003cp\u003eActions with Transactions will continue to function in all other supported locales.\u003c/p\u003e\n"],["\u003cp\u003eTroubleshooting steps are provided for common issues like Action unresponsiveness, receipt processing failures, order update failures, and missing order update notifications.\u003c/p\u003e\n"],["\u003cp\u003eUsers can view their transaction history through their Google Account settings or by visiting myaccount.google.com.\u003c/p\u003e\n"]]],["Due to regulatory changes, Conversational Actions' transaction features are unavailable in Denmark, France, Germany, Italy, the Netherlands, Norway, Poland, Spain, and Sweden. Troubleshooting steps include ensuring complete directory information, unique `merchantOrderIds`, and proper JWT authentication for the Orders API. Only order updates with specific statuses (`CANCELLED`, `FULFILLED`, `REJECTED`, `RETURNED`) trigger notifications. Users can view transactions on their Google Account via the \"Payments & subscriptions\" section or via Stackdriver logs.\n"],null,["# Troubleshooting physical transactions\n\n| **Warning:** Due to new regulatory requirements, transaction functionalities for Conversational Actions are no longer available in the following countries:\n|\n|\n| Denmark, France, Germany, Italy, the Netherlands, Norway, Poland, Spain, Sweden\n|\n|\n| Actions with Transactions will continue to work in all supported locales.\n\n\u003cbr /\u003e\n\nIf you're having trouble fulfilling transaction intents with your Action, see if\nyou're experiencing any of the symptoms described in the following sections and\ntake the recommended troubleshooting steps.\n\nAction not responding\n---------------------\n\n**Symptom:** When checking for transaction requirements or decision of the user,\nthe user gets back a response of *\"App isn't responding at the moment. Try again soon.\"*\n\n**Troubleshooting:** Ensure your Action project has all the required directory information, including a privacy policy link.\n\nUnable to process receipt\n-------------------------\n\n**Symptom:** During purchase authorization, the user gets a response saying\n\"*Sorry, I am unable to process your receipt.*\"\n\n**Troubleshooting:**\n\n- Make sure your `merchantOrderId` is unique. A new order can't be placed with a previous, existing order ID.\n- Make sure you're sending a [simple response](/assistant/conversational/prompts-simple) alongside the initial `orderUpdate`; this is the mandatory response format.\n\nUnable to send order updates\n----------------------------\n\n**Symptom:** When sending an order update for an existing order, the Orders API\nresponds with error code 500 and the following error message: \"*Order `OrderID`\nfor project `ProjectID` could not be updated. Please try again.*\"\n\n**Troubleshooting:**\n\n- Make sure you're supplying working credentials during [JWT authentication for\n the Orders API](https://github.com/google/google-api-nodejs-client#using-jwt-service-tokens).\n\nOrder updates not appearing as notifications\n--------------------------------------------\n\n**Symptom:** Initial order is placed and follow-up order updates succeed with\nstatus code 200 but don't appear as push notifications on the user's Assistant-enabled\ndevice.\n\n**Troubleshooting:** Not all order updates will be reflected as a push notification;\nonly updates with a status of `CANCELLED`, `FULFILLED`, `REJECTED`, or `RETURNED`\nresult in a notification.\n\nView transactions on your account\n---------------------------------\n\nYou can view transactions that have been made through your account by following these steps:\n\n1. Navigate to [myaccount.google.com](https://myaccount.google.com) and log in.\n2. Click **Payments \\& subscriptions** in the left menu.\n3. Under **Purchases** , click **Manage purchases**.\n\nYou can also view sandbox transactions by adding the following URL query parameter: \n\n```text\nmyaccount.google.com/purchases?sandbox=1\n```\n\nOther troubleshooting tips\n--------------------------\n\nIf the above symptoms don't describe the problem you're running into, you may\nwant to refer to your project's [Stackdriver logs](/assistant/console/troubleshooting)\nfor further troubleshooting. You can also refer to your [Google Account settings](https://myaccount.google.com/preferences?pli=1#subscriptions)\nto view and manage any purchases you've made with your Action."]]
