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

June

On June 1 you introduce ABC AMI, and several days later people begin signing up for it. During June, five people sign up. They pay a prorated monthly charge to cover the remaining portion of June.

Your June DevPay Activity Page on June 14

We'll first focus on what your DevPay Activity Page looks like in the middle of June after your customers have been using ABC AMI for a while.

Usage

The following table shows your customers' usage details as of June 14. By this date, only three of the five customers who will sign up in June have signed up and started to use ABC AMI. Customer A signed up on June 3, Customer B on June 4, and Customer C on June 5. Notice that Customer C signs up to use your product, but doesn't use it during June.

Customer

Usage Dimension

A

B

C

Total

Small instance-hours used

0

8

0

8

Large instance-hours used

3

0

0

3

X-large instance-hours used

5

0

0

5

GB data uploaded

64

40

0

104

GB data downloaded

35

10

0

45

Revenue

The next table shows your revenue as of June 14. This includes actual revenue and expected revenue. The actual revenue covers the prorated monthly fees your customers already paid at sign-up. The expected revenue covers their usage up to June 14 (they don't actually pay that money until we bill them on July 1). In this example, your usage-based revenue comes only from small, large, and extra-large instances used. Remember that to keep the example short, we're ignoring all other usage-based dimensions for Amazon EC2 (such as high-CPU instance types, Elastic Block Store, regional data transfer, etc).

Customer

Revenue Source

A

B

C

Total

June prorated monthly fee

$18.67

$18.00

$17.33

$54.00

Small instance-hours used

$0.00

$1.60

$0.00

$1.60

Large instance-hours used

$1.50

$0.00

$0.00

$1.50

X-large instance-hours used

$4.50

$0.00

$0.00

$4.50

Total

$24.67

$19.60

$17.33

$61.60

AWS Costs

The next table shows the AWS costs you owe based on your customers' usage amounts. These costs are based on the amount AWS charges for Amazon EC2.

Note

The Amazon EC2 prices shown here 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.

Customer

Usage Dimension

A

B

C

Total

Small instance-hours used

$0.00

$0.80

$0.00

$0.80

Large instance-hours used

$1.20

$0.00

$0.00

$1.20

X-large instance-hours used

$4.00

$0.00

$0.00

$4.00

GB data uploaded

$6.40

$4.00

$0.00

$10.40

GB data downloaded

$5.95

$1.70

$0.00

$7.65

Total

$17.55

$6.50

$0.00

$24.05

Value-Add

The next table shows your value-add for each customer, which is the difference between the revenue from the customer and the AWS costs the customer incurred (both of these values are shown in the preceding tables).

Customer

A

B

C

Revenue

$24.67

$19.60

$17.33

AWS Costs

$17.55

$6.50

$0.00

Value-Add

$7.12

$13.10

$17.33

3% DevPay Fee on Value-Add

$0.21

$0.39

$0.52

As of June 14, each of the individual value-add amounts that you expect to receive from your customers is greater than zero. The sum of them is $7.12 + $13.10 + $17.33 = $37.55 (we calculate the value-add amounts per individual customer, but we're mentioning this summed value because it explicitly appears on the DevPay Activity page).

We charge you a 3% DevPay fee on each value add amount that is greater than zero. This means that as of June 14, you owe $0.21 + $0.39 + $0.52 = $1.13.

DevPay Activity Page

The preceding tables show the details of the usage, revenue, and value-add amounts for each customer up to June 14. We present a summary of this information across all your customers on your DevPay Activity page, which you can view at any time. Following is an image of your DevPay Activity page on June 14, which shows the month-to-date summary for ABC AMI.

Note

During the month, the DevPay Activity page reflects the current month's data up to and through the previous day. Therefore, on the first day of the month, the page has no data to display yet and so shows zeros.

The dates displayed on the DevPay Activity page and related pages are in Coordinated Universal Time (Greenwich Mean Time).

The page is divided into two main areas: the main summary and then a larger area containing a table for each DevPay product you have. The Summary section at the top summarizes the revenue, costs, and fees across all your DevPay products (in this example you have only one product). It shows both the revenue you expect to receive (assuming all your customers pay their bills), and the actual revenue that we have collected. You can come back to this page at any time to see how much of your expected revenue for the month we've collected from your customers. Note that during the month, there is typically a big difference between the expected values and the collected values, because we don't bill you or your customers for much of that money until after the end of the month.

Following the summary is a table for each DevPay product you have. Each table has three sections:

  • The top part shows the product's name and three links on the right:

    • View Product Details—Displays the information you provided when you registered the product. You can edit the information there. The page also displays the purchase URL, product code, and product token for the product.

    • Change Pricing—Steps you through the process of changing the product's price (for more information, see Changing Pricing).

    • View Customer Reports—Takes you to a page where you can access the DevPay reports (for more information, see Reports).

  • The middle part of the table shows the revenue the product has generated during the month. Currently it shows month-to-date values as of June 14.

  • The bottom part shows the costs the product incurred during the month. The section includes both the AWS service costs (in this case, the costs of Amazon EC2) and the DevPay fees. Currently it shows month-to-date values as of June 14.

Revenue Statement on June 14

The summary includes two columns: Expected and Collected. The Expected column shows:

  • Your total expected revenue for June to date (assuming your customers pay their bills when we bill them on July 1)

  • The DevPay fees you're expected to pay for June to date

  • The AWS costs you're expected to pay when we bill you after July 1 (the amount is based on your customers' usage of your product to date in June)

For June to date, you expect to receive $61.60 in revenue. You've already received $54.00 of that in the form of prorated monthly fees, so the $54.00 shows up in the Collected column.

You're also expected to pay $2.93 in DevPay fees for June to date. You've already paid $0.90 of that in the form of the $0.30 transaction fees we subtracted when your first three customers signed up and paid the prorated monthly charges. We'll bill you for any remaining fees you owe after July 1.

Finally, you're also expected to pay $24.05 in AWS costs for June to date. However, we won't bill you for that until after July 1, so 0.00 is displayed in the Collected column for now.

$54.00 is the total of the prorated monthly charges your three customers paid immediately when they signed up. The description says "Monthly charges including prorated monthly amounts," but at this point you have only prorated monthly amounts. Next month you'll have both full monthly charges and prorated amounts because your existing customers will be charged full monthly fees, and then more people will sign up and be charged prorated monthly fees.

Your customers have used 8 small, 3 large, and 5 extra-large instance hours by June 14. The page shows the price they pay you for this usage and the corresponding costs you pay to AWS.

The DevPay fee includes 3% of the sum of the individual value-add amounts that are greater than zero. These were shown in a preceding table to be $7.12 for Customer A, $13.10 for Customer B, and $17.33 for Customer C, and they total $37.55.

The DevPay fee also includes the $0.30 transaction fee that we collect each time we charge your customers. Therefore we include six instances of the $0.30 fee because we charged each of your three customers when they signed up during June, and we will charge them on July 1 for their June usage.

Note

The July 1 bill will cover your revenue for both June (usage) and July (monthly fees); however, the $0.30 transaction fee per customer collected on July 1 is reported on the June statement.

Notice that the number of transactions shown here (six) does not equal the number of customers you currently have (three). To get the number of customers you have for a product, use the subscription report (for more information, see Subscription Report).

Important

In the main Revenue section of the table, there could be a slight discrepancy between the math shown in the Details column (in the middle) and the value in the Totals column (on the right). This is due to rounding. We round sub-penny charges up to a whole penny, and we round charges over a penny up or down to the closest penny.

Your June DevPay Activity Page at the End of June

Now we'll look at your DevPay Activity page at the end of June. After June 14, your three existing customers continue to use ABC AMI, and two new customers sign up (one on June 15 and the other on June 20). The following tables (which are similar in format to the preceding ones) show your ABC AMI customers' usage, revenue, and value-add details at the end of June.

Usage

Customer

Usage Dimension

A

B

C

D

E

Total

Small instance-hours used

0

12

2

9

1

24

Large instance-hours used

5

0

6

0

0

11

X-large instance-hours used

5

0

4

11

30

50

GB data uploaded

72

43

22

112

68

317

GB data downloaded

35

10

19

14

44

122

Revenue

The next table shows your revenue as of the end of June. This includes actual revenue and expected revenue. The actual revenue covers the prorated monthly fees your customers already paid at sign-up. The expected revenue covers their usage through the end of June.

Customer

Revenue Source

A

B

C

D

E

Total

June prorated monthly fee

$18.67

$18.00

$17.33

$10.67

$7.33

$72.00

Small instance-hours used

$0.00

$2.40

$0.40

$1.80

$0.20

$4.80

Large instance-hours used

$2.50

$0.00

$3.00

$0.00

$0.00

$5.50

X-large instance-hours used

$4.50

$0.00

$3.60

$9.90

$27.00

$45.00

Total

$25.67

$20.40

$24.33

$22.37

$34.53

$127.30

AWS Costs

The next table shows the AWS costs you owe based on the usage amounts shown in the preceding usage table.

Customer

Usage Dimension

A

B

C

D

E

Total

Small instance-hours used

$0.00

$1.20

$0.20

$0.90

$0.10

$2.40

Large instance-hours used

$2.00

$0.00

$2.40

$0.00

$0.00

$4.40

X-large instance-hours used

$4.00

$0.00

$3.20

$8.80

$24.00

$40.00

GB data uploaded

$7.20

$4.30

$2.20

$11.20

$6.80

$31.70

GB data downloaded

$5.95

$1.70

$3.23

$2.38

$7.48

$20.74

Total

$19.15

$7.20

$11.23

$23.28

$38.38

$99.24

Value-Add

At the end of June, we again calculate the individual value-add amount for each customer (as shown in the following table). Note that some of the amounts are less than zero, meaning you have no value-add for that particular customer (and therefore pay no 3% DevPay fee for that customer; you still, however, pay the $0.30 transaction fee).

Customer

A

B

C

D

E

Revenue

$25.67

$20.40

$24.33

$22.37

$34.53

AWS Costs

$19.15

$7.20

$11.23

$23.28

$38.38

Value-Add

$6.52

$13.20

$13.10

- $0.91

- $3.85

3% DevPay Fee on Value-Add

$0.20

$0.40

$0.39

N/A

N/A

The value-add amounts for Customer D and E are less than zero because based on the price you set for ABC AMI, the prorated monthly fee they paid plus the usage-based revenue wasn't enough to cover the AWS costs they incurred. Depending on their usage in July (a month where they pay the full $20.00 monthly fee), you might have a value-add amount that is greater than zero for each of them.

The following table compares the value-add amounts for Customers A–C on June 14 and at the end of June.

Customer

A

B

C

Value-add on June 14

$7.12

$13.10

$17.33

Value-add at end of June

$6.52

$13.20

$13.10

We use the final sum at the end of June as the basis for the 3% DevPay fee that you pay after July 1. However, the DevPay Activity page is updated daily with the current sum of all value-add amounts greater than zero.

DevPay Activity Page

Following is the final June 2009 DevPay Activity page that summarizes the details in the preceding tables.

Revenue Statement for June

In the summary, the Expected label has changed to Billed to reflect that the month is closed and we're moving on to the end-of-month billing cycle.

Your total revenue for June is $127.30. You've already received $72.00 in the form of prorated monthly fees (shown in the Collected column).

You're expected to pay $3.98 in DevPay fees for June. You've already paid $1.50 of that in the form of the $0.30 transaction fees we subtracted when your five customers signed up and paid the prorated monthly charges. After July 1, we'll bill you for any remaining fees you owe.

Finally, you're expected to pay $99.24 in AWS costs for June. However, we won't bill you for that until after July 1, so 0.00 is displayed in the Collected column for now.

The additional two customers have signed up since June 14, so the $72.00 is the total of the prorated monthly charges all five customers paid when they signed up.

The DevPay fee includes 3% of the sum of the individual value-add amounts that are greater than zero. These were shown in a preceding table to be $6.52 for Customer A, $13.20 for Customer B, and $13.10 for Customer C, and they total $32.82.

The DevPay fee also includes the $0.30 transaction fee we collect each time we charge your customers. Therefore we include 10 instances of the $0.30 fee because we charged each of your five customers when they signed up during June, and we will charge them on July 1 for their June usage.

Note

The July 1 bill will cover your revenue for both June (usage) and July (monthly fees); however, the $0.30 transaction fee per customer collected on July 1 is reported on the June statement.

Your DevPay Transaction History in June

At the bottom of the DevPay Activity page is a link to your DevPay Transaction History page. Following is the page at the end of June. It shows each deposit and charge related to DevPay. We aggregate all the deposits that occur on a single day, and all charges that occur on a single day.

Transaction History for June

The deposits are the prorated monthly charges your customers paid when they signed up during June. The sum total of their payments is $72.00 (which is shown on the preceding Account Activity page). If you subtract the $0.30 transaction fees (5 x $0.30), the result is $70.50. This is the current total balance displayed on the page.

Note

The DevPay transaction history is updated continuously as deposits or withdrawals are made during the day. However, the DevPay Activity page is updated once each day. Because of this, the DevPay transaction history might show entries that are not yet reflected in the DevPay Activity page.

The following table shows the entries you can expect to see in the DevPay transaction history. For all entries where we collect money from you, we indicate whether we charge your Amazon Payments account or your credit card.

EntryDescription

Deposit (Revenue collected minus $0.30 fee per customer)

A deposit we make into your account when we collect money from your customers. For more information, see When and How You Get Paid.

Charge (Revenue collected minus $0.30 fee per customer)

A charge we make for the net amount you owe if the revenue collected from your customer is less than the $0.30 fee you owe for that customer. We typically aggregate these types of charges because they're very small (less than $0.30), so the listed amount might cover multiple charges. For more information, see When You Have a Small Monthly Charge.

AWS Costs and 3% DevPay Fees for MM/YYYY

The monthly charge we make for:

  • The cost of AWS services used by your customers (for more information, see The Cost of AWS Services)

  • The 3% DevPay fees on each individual value-add amount greater than zero (for more information, see DevPay Fees)

Customer Refunds

A charge we make for any recent refunds we have processed for your customers. For more information, see Customer Refunds and Chargebacks.

Withdrawal

A withdrawal you make from your Amazon Payments account to your bank account. For more information, see Your Amazon Payments Account.

Note

The account balance displayed on the DevPay Transaction History page does not necessarily reflect all the items displayed in the DevPay transaction history. For more information, see Your Amazon Payments Account.

Your June DevPay Activity Page in Early July

You can view your June DevPay Activity Page in July to see how much of the June revenue you've received. We update the numbers in the Collected column daily with the latest information.

Following is the June DevPay Activity page as displayed in July after we've billed your customers and charged you for the AWS costs and DevPay fees. We've successfully collected the remaining revenue (and deposited it into your Amazon Payments account) and successfully charged you for all the costs and remaining fees you owe. Therefore, the amounts in the Collected column match the amounts in the Billed column. To see how those remaining deposits and charges appear in your DevPay Transaction History, see Your DevPay Transaction History for July.

Revenue Statement for June