Question

I’m trying to implement in-app payment support in a BB application.

Ok, I’ve read the API/docs and now I need to write a simple test. Here is what API says about testing:

To test the end-to-end purchase flow without being charged money, you can set up a BlackBerry ID as a test account. The test account allows you to download any applications or digital goods that are associated with your BlackBerry App World vendor account without incurring any costs. Local testing must be turned off for this type of testing, otherwise no network connections will be attempted.

From the above I see that I need to achieve 2 goals:

• (1) “set up a BlackBerry ID as a test account” (what ever it means).
• (2) “Local testing must be turned off for this type of testing” (what ever it means).

The API is vague on how to do that. I can only guess that point (1) can be done on the side of my customer (whom I’m writing the app for) via his AppWorld account. Is it true? And I’m totally out of ideas on point (2). Could anyone point me in the right direction?

Answer 1

Ah yes, the Payment API is particularly vague on testing, and in the latest version (1.5) RIM have removed the ability to test locally, so all testing must be done via App World. Here’s how:

1. Setup a ‘sandbox’ account using the BlackBerry App World vendor portal
2. Upload your app into BlackBerry App world but don’t publish it, just save it and leave it in draft state
3. Also in the vendor portal, set up your digital goods (the things available for in-app purchase)
4. On your BlackBerry, load App World and login with your sandbox account email address.
5. Within any screen in App World press ALT+TST and enter the SKU or ID of your test app.
6. You can then download the test version of your app (which is not available to anyone else)
7. Once the app is downloaded and installed you will be able to test your in app payments.

Bit of a faff, but not too hard once you’ve got the process sorted.