Amazon DevPay
Developer Guide (API Version 2007-12-01)

Testing and Going Live

This section describes the process we recommend you follow to test your DevPay product and to take it into production.


DevPay has no testing sandbox. You can only test your product in a live environment. Remember that you will incur real charges during testing and your credit card will be charged accordingly.

Overall Process for Testing and Going Live with Your Product


Understand how product pricing and DevPay fees work. For more information, see How Do You Set Your Product's Price?. The section links you to several other sections that describe possible implications of your pricing scheme.


Create an AWS developer account to use when creating your product. We recommend you have a single AWS developer account for all your DevPay products. Don't use the personal AWS account of one of the employees in your company.


Determine your pricing and the other product information you'll provide when registering your product. For more information, see Registering Your Product.


Register your product using the AWS developer account you created and get the product token, product code, and purchase URL for your product. After AWS approves your product, the purchase URL becomes live and available for anyone to use. Don't expose the purchase URL to the public yet.


Do any coding required to integrate your product with DevPay. For an Amazon EC2 paid AMI, see Amazon DevPay and Your Amazon EC2 AMIs. For an application using Amazon S3, see Using DevPay with Your Amazon S3 Product.


Use the purchase URL yourself to sign up for your product with a test customer account. You must provide an active credit card when you sign up. If you use the product with the test customer account, the credit card is charged accordingly.


If your system is designed to programmatically obtain the activation key, confirm your system gets it correctly when a test customer signs up for your product.


Use your product with the test customer account you've created.


Watch your DevPay Activity page and the Application Billing page for the test customer. These show the usage information and corresponding revenue you expect to receive for the usage of your product by your test customer. For an example of how charges appear on your DevPay Activity page and DevPay transaction history, see Appendix: Example DevPay Activity Pages.


Look at the revenue your product generates and verify that the product's pricing meets your requirements. If necessary, make changes to the pricing. For more information, see Changing Pricing.


If you're using the License Service API to validate the status of a customer's subscription, use the API to confirm the status of your test customer. Confirm the process fits correctly into your customer support workflow. For more information, see Verifying the Customer's Subscription Status.


Update the product information if you find you need to make any changes. For more information, see Making Changes to Your Product.


After you're satisfied with the pricing and product information and you're ready to go into production, make the purchase URL visible to the public. For more information, see Advertising Your Product.