How To: Live Testing the Payment SDK with PlayBook Applications
on 06-05-201201:31 PM - edited on 01-21-201304:10 PM by melleb
This article applies to the following:
Applications created with any of the BlackBerry® PlayBook™ development SDKs that include Payment Services
Live testing permits you to test the purchase of digital goods against the live Payment Service server without being charged real money. To test your applications live, you must perform the following actions:
Add your application to the vendor portal for the BlackBerry® World™ storefront. Don't send your application to RIM for approval, but keep it in Draft state.
Add digital goods and a release bundle to your application in the vendor portal.
Create a sandbox account by registering your BlackBerry ID in the vendor portal.
After you add your application and digital goods, you can download your application from BlackBerry World and start testing the purchase process against the live Payment Service server.
By registering the BlackBerry ID with the vendor portal, you can use the BlackBerry ID to perform test purchases of applications, as well as digital goods within your applications. When you initiate a purchase, and log in using the BlackBerry ID that you registered with the vendor portal, you can simulate a real purchase without any charges to your account. The BlackBerry ID that you register with the vendor portal can be used only to purchase digital goods from the applications associated with your BlackBerry World vendor account.
Before you make products available to BlackBerry PlayBook tablet users, you can test the purchase of your products and any digital goods that you sell within your products by creating a sandbox account. When you create a sandbox account, you specify the email address that is associated with a BlackBerry ID. You then use the BlackBerry ID to test the purchase of your products without being charged for the purchases.
When you test a purchase using a sandbox account, BlackBerry World doesn't create a purchase record. If your application calls getExistingPurchases(true), the function doesn't return the purchases that you make using the sandbox account.
On the vendor portal for the BlackBerry World storefront, click Sandbox.
Click Add New User.
In the Email field, type the email address associated with a BlackBerry ID.
In the Description field, type a description for the sandbox account.
Download an application before you make it available for distribution
Add your application, a release bundle, and digital goods in the vendor portal for the BlackBerry World (the application status can remain as Draft).
Create a sandbox account in the vendor portal using a BlackBerry ID.
If your application has any distribution restrictions (such as the BlackBerry device models or BlackBerry Device Software versions that it supports), make sure that the BlackBerry device that you download the application to is compatible with your application, otherwise you won't be able to locate your application in the BlackBerry World storefront If you purchase another vendor's application or digital goods using your BlackBerry ID account that is configured for testing, the transaction is real, not simulated, and your account is charged. You can simulate only the purchases of your own applications and digital goods.
On the home screen of the BlackBerry PlayBook tablet, tap the BlackBerry World icon.
Swipe your finger from the bottom left corner of the screen toward the center of the screen to display the keyboard.
Type tst. Tap Return.
Open the browser on the tablet.
In the address bar, type the location of the application that you want to test (for example, you can type http://appworld.blackberry.com/webstore/content/xxxxx, where xxxxx is the ID of the application).
On the Details screen for your application, click Purchase.
Complete the instructions on the screen to download the application.
You can use the same BlackBerry ID login information to purchase the digital goods that your application offers.
NOTE: As no charges are incurred when performing Live testing there is no transaction history generated. As such, any simulated purchases will not appear in the transactions history if queried programmatically.