         | Did this page help you? Yes No Tell us about it... |
Recommendations for Product Development
When developing your product and planning how your system will work, we suggest you follow the recommendations described in the following table.
| Recommendation | Description |
|---|---|
|
Special AWS developer account for your products |
When registering your first product with DevPay, create a single AWS developer account to use with all your DevPay products. All the products will then appear on the DevPay Activity page associated with that AWS developer account. Use a business e-mail address not associated with a specific person as the login for the account. |
|
Amazon Payments branding |
On your site, mention that Amazon Payments handles the billing for your product. Include the Amazon Payments trademark or logo to help orient your customers. The trademark, logo, and guidelines for using them with Amazon DevPay are available in the co-marketing area of the Developer Connection web site. |
|
Link to Application Billing page |
Display an obvious link to the Application Billing page (http://www.amazon.com/dp-applications). Explain that this is the location where customers get usage and billing information about your product, cancel use of your product, and manage their payment methods. |
|
Your customer service contact information |
Display your own customer service information prominently so that customers know how to contact you with questions about your product. |
|
Amazon Payments contact information |
Display the |
|
Area for product news on your site |
Include an area on your site where you post the latest news or information about your product, and make customers aware of the area. |
|
Activation key |
When you read the sections in this guide about integrating your product with DevPay, you'll see that you probably need to obtain an activation key from DevPay for each customer. Whether you need to do this depends on the type of product you have and whether you want to verify if a customer is still subscribed to your product. The details of these situations are discussed later in the guide. AWS makes the activation key available to you in several ways discussed elsewhere in the guide. One of the ways involves customer interaction and requires the customer to get the key and give it to you. Another way doesn't involve the customer; instead, you programmatically obtain the key from a redirect URL. We recommend you use the programmatic method but also have a backup plan to obtain the key from the customer, should the programmatic method fail. Any time you ask the customer to get the activation key for you (for reasons described in subsequent sections in this guide), display the activate URL (http://www.amazon.com/dp-activate), which goes to a page where customers can obtain an activation key for your product (for an example, see The Application Activation Page). Customers must log in with their Amazon.com login IDs. |
|
Implication of cancellation |
Make customers aware of what happens when they cancel use of your product. For example, if your product stores images for them, let the customers know they can't access those images once they cancel. Caution them to retrieve their data before canceling (for more information about customer cancellation and access to data, see Customer Cancellation and Customer Access Stored Data). |
|
Amazon EC2 sign-up |
If your product is an Amazon EC2 AMI product, make your customers aware that they must be signed up for Amazon EC2 to purchase your product. Customers who are not already signed up for Amazon EC2 will be prompted to sign up when they purchase your product. |
|
Product security |
Design your product and system with security in mind. For information about some possible product risks you should be aware of, see Appendix: Risks to DevPay Products. If your product is an Amazon EC2 AMI, don't enable root access to the AMI unless it's necessary. For more information, go to the section about protecting shared AMIs in the Amazon Elastic Compute Cloud Developer Guide. |
