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.
CompletePurchaseValueSpec
Stay organized with collections
Save and categorize content based on your preferences.
AI-generated Key Takeaways
This content describes specifications for initiating in-app purchases of digital goods like in-app purchases and subscriptions, part of the deprecated Orders version 2 API.
The CompletePurchaseValueSpec includes skuId, which specifies the product being purchased, and developerPayload, an opaque string for developers to associate with the purchase.
The SkuId object identifies a SKU and includes fields for skuType, a string id, and packageName.
[[["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 document details the structure for initiating in-app purchases (including subscriptions) within a deprecated API. It utilizes `skuId` and `developerPayload` fields to define a purchase. `skuId` further specifies the `skuType`, `id`, and `packageName` of the product. The `developerPayload` is an opaque string used for associating data with the purchase. The information includes the JSON representations of this purchase information. It emphasizes that it belongs to version 2 and provides a link for version 3 migration.\n"]]