Distributing digital goods
You can distribute digital goods either by sending data files over the wireless network from your own server, or by unlocking existing functionality from within the application's code.
If the digital goods for your application don't require dynamic updates, it's generally more efficient to include the functionality for those goods in the source code. For example, if you sell a game that offers additional levels as a digital good, your game logic can control access to the extra levels based on purchase logic.
If, however, you host your digital goods on a content server and deliver them to BlackBerry devices over the wireless network, you can update and add to your offering of digital goods without having to submit a new release of your application to the BlackBerry World storefront.
Distributing digital goods from a content server
There are two ways to keep your content server up to date on successful purchases: design your application to send a notification to the content server, or request a notification from the Payment Service.
To request notifications from the Payment Service, you must set up a dynamic license model when you register the digital goods in the BlackBerry World vendor portal.
The dynamic license model for digital goods requires an HTTPS URL for your content server. During each successful purchase, the Payment Service server sends your content server a request for a license key, and the following purchase parameters:
- The device pin.
- The email address associated with the user's BlackBerry ID account.
- The product name for the application that the digital goods are purchased from.
- The version of the application that the digital goods are purchased from.
- The transactionid, used as a unique identifier for the successful purchase.
- The product sku.
- The results of a true or false test that indicates whether the purchase was initiated using a BlackBerry ID account configured for testing.
Your content server needs to respond to the Payment Service server with a license key, which is then passed to the user's device as part of the purchase transaction.
Last modified: 2013-10-02