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

Monthly Payments


Amazon DevPay is not accepting new seller accounts at this time. Please see AWS Marketplace for information on selling your applications on Amazon Web Services.

This section describes the process we use to pay you each month, and to collect the DevPay fees and the costs of AWS services that you owe.

Overall Timing

After your customers sign up for your product, we bill them monthly on the first day of the month. On that day, we bill them for the previous month's usage and the current month's fee (assuming the product has both usage-based and monthly charges). For example, on May 1, we bill them for their usage in April and for the monthly fee to cover May.

If you think of this from the perspective of the revenue for a particular month (e.g., April), then you can see that you receive your April revenue at two main times (April 1 and May 1). At any point during April, you can view your DevPay Activity Page and see how much revenue we've actually collected in April monthly fees to date, and how much April revenue you expect to receive after we bill your customers for their April usage on May 1 (for more information about using the page, see Your DevPay Activity Page).

At the end of April, we summarize the data for that month and display it in the April revenue statement (for an example, see Appendix: Example DevPay Activity Pages). During May and thereafter, you can view the April revenue statement and see how much of the April usage-based revenue we've actually been able to collect from your customers.

The following figure illustrates the concepts of your collected revenue and expected revenue.

						Monthly Billing Cycle: Revenue Collected

The Monthly Billing Process

As discussed in the preceding section, we bill your customers monthly. We also charge you monthly for the DevPay fees and for the cost of the AWS services your customers used during the month. This section describes how the process works. We'll continue to use the month of April as an example and focus on the May 1 billing cycle. We'll assume that your customers all paid their April monthly fees on April 1 (during the April 1 billing cycle).

The overall process for the monthly billing cycle is described in the following figure and table.

						Billing and payment flow

Process for Monthly Billing


We bill your customers.

On May 1, we bill your customers for their usage in April and the monthly fee to cover May.


Your customers' payments come in during the first few days of May.


We subtract the $0.30 DevPay fee per product from each payment and deposit the remaining amount in your Amazon Payments account.

The customers' payments cover revenues for both April and May: usage-based revenue for April, and monthly fee revenue for May. However, the $0.30 transaction fee collected on May 1 is reported on your April DevPay revenue statement.


We charge you a few days later.

We calculate your value-add for each customer in April. We then charge you for:

  • The 3% DevPay fee on any value-add amount greater than zero for each customer

  • The costs of the AWS services each customer used during April

We attempt to charge your Amazon Payments account, and if the balance is insufficient, we charge the remainder to your credit card.


We aggregate all the 3% fee amounts and AWS costs for your customers and charge you once, so you don't have a separate individual charge for each customer.

You can withdraw funds from your Amazon Payments account at any time, but we recommend you wait until after we charge you in step 4 to be sure you have sufficient funds.

Let's continue with the earlier example about Joe who signs up for your product on April 16 (for that example, see Sign-Up Payments). What happens with the May 1 billing cycle? We'll follow the four steps in the monthly billing process described in the preceding table.

For step 1, we bill Joe for his usage from sign-up on April 16 through April 30. We also bill him for the monthly charge that covers all of May. The following figure shows his usage amounts, the corresponding AWS costs for Amazon EC2, and the details of the bill he pays on May 1. We're currently only interested in revenue related to April, so we'll ignore the monthly charge that covers May.


The Amazon EC2 prices shown in the following example were valid when this document was originally written. The prices might have changed since then. For the current Amazon EC2 prices, go to the Amazon EC2 product page.

						Example: Charges on May 1 (step 1)

For step 2, we collect Joe's May 1 payment of $18.50. For step 3, we subtract the $0.30 transaction fee and deposit the remainder ($18.20) in your account.

						Example: Charges on May 1 (step 2 and 3)

Step 4 occurs around May 2. We calculate the total revenue Joe generated in April ($24.50) and your value-add for April ($20.15). We charge you 3% of your value-add (3% * $20.15 = $0.60) plus $4.35 for the AWS costs for Amazon EC2. The total amount you pay is $4.95.

						Example: Charges on May 1 (step 4)

The following equation shows your net revenue for Joe for April.

						Example: April net revenue