Altova MobileTogether Designer

The Purchase action (screenshot below) sends a purchase request from the client device to the corresponding app store. The purchase request contains the ID of the product being purchased, the user's account ID and profile ID, and, for the Android store, the product's offer token if the product is a subscription. You can obtain the user IDs from, for example, a user's login credentials or some other suitable database.


When the purchase request reaches the app store, the app store will attempt to carry out the request and bill the user's account according to the user's billing information that is stored at the app store. After the app store executes the purchase request, it sends back information about the purchase. This data will be stored in the $MT_IN_APP_PURCHASE page source, with the buyer's data being stored in the @AccountID and @ProfileID attributes of the most recent Purchase element. You can authenticate the purchase by verifying that the device user's credentials match these two attributes (the buyer's credentials).


Note:If this action is the first In-App Purchase action to be added to the design, then the $MT_IN_APP_PURCHASE page source tree will be added automatically to the design's page sources. For a description of this page source, see the topic In-App-Purchase Page Source.


MobileTogether extension functions

MobileTogether provides a range of XPath extension functions that have been specifically created for use in MobileTogether designs. Some functions can be particularly useful with specific actions. For example, mt-available-languages() returns the languages in which the solution is available and could, for example, be used with the Message Box action. If a function is especially relevant to this action, it is listed below. For a full list of extension functions and their descriptions, see the topic MobileTogether Extension Functions.







© 2018-2024 Altova GmbH