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

July

On July 1 we bill your five customers for their June usage and the July monthly fees. In this example, their payments all come in immediately. In the next day or so, we charge you for the costs of Amazon EC2 used by your customers in June, and for the 3% DevPay fee on the value-add amount per customer. For more information about how we collect the 3% fee, see When and How You Get Paid.

During July, two more people sign up for ABC AMI (for simplicity, we'll say they both sign up on July 16). You receive the new customers' prorated monthly fees to cover the rest of July when they sign up. Also, Customer B cancels on July 21, and we issue the customer a prorated refund for the remaining days in July. We still bill the customer on August 1 for any pre-cancellation usage. At the end of July, you have six customers signed up for ABC AMI.

Your July DevPay Activity Page at the End of July

Your customers use ABC AMI during July. The following tables (which are similar in format to the preceding ones for June) show your customers' usage, revenue, and value-add details at the end of July.

Usage

Customer

Usage Dimension

A

B

C

D

E

F

G

Total

Small instance-hours used

0

10

9

13

0

0

49

81

Large instance-hours used

0

0

0

0

0

12

0

12

X-large instance-hours used

8

0

4

3

155

0

0

170

GB data uploaded

118

14

34

98

82

57

76

479

GB data downloaded

44

19

60

120

21

49

78

391

Revenue

The next table shows your revenue at the end of July. This includes actual revenue and expected revenue.

The actual revenue covers the full July monthly fees your first five customers paid on July 1, plus the prorated monthly fees the two new customers paid at sign-up. For Customer B, the July monthly fee in the table is still listed as $20.00. We'll account for the cancellation refund we give Customer B elsewhere.

The expected revenue covers all the customers' usage during July (they don't actually pay that money until we bill them on August 1).

Customer

Revenue Source

A

B

C

D

E

F

G

Total

July monthly fee (full or prorated)

$20.00

$20.00

$20.00

$20.00

$20.00

$10.32

$10.32

$114.19

Small instance-hours used

$0.00

$2.00

$1.80

$2.60

$0.00

$0.00

$9.80

$16.20

Large instance-hours used

$0.00

$0.00

$0.00

$0.00

$0.00

$6.00

$0.00

$6.00

X-large instance-hours used

$7.20

$0.00

$3.60

$2.70

$139.50

$0.00

$0.00

$153.00

Total

$27.20

$22.00

$25.40

$25.30

$159.50

$16.32

$20.12

$295.84

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

F

G

Total

Small instance-hours used

$0.00

$1.00

$0.90

$1.30

$0.00

$0.00

$4.90

$8.10

Large instance-hours used

$0.00

$0.00

$0.00

$0.00

$0.00

$4.80

$0.00

$4.80

X-large instance-hours used

$6.40

$0.00

$3.20

$2.40

$124.00

$0.00

$0.00

$136.00

GB data uploaded

$11.80

$1.40

$3.40

$9.80

$8.20

$5.70

$7.60

$47.90

GB data downloaded

$7.48

$3.23

$10.20

$20.40

$3.57

$8.33

$13.26

$66.47

Total

$25.68

$5.63

$17.70

$33.90

$135.77

$18.83

$25.76

$263.27

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. Note that the table also has a row to show the refund we gave Customer B for the unused portion of the $20.00 monthly fee.

Customer

A

B

C

D

E

F

G

Revenue

$27.20

$22.00

$25.40

$25.30

$159.50

$16.32

$20.12

Refund

$0.00

$6.45

$0.00

$0.00

$0.00

$0.00

$0.00

AWS Costs

$25.68

$5.63

$17.70

$33.90

$135.77

$18.83

$25.76

Value-Add

$1.52

$9.92

$7.70

- $8.60

$23.73

- $2.51

- $5.64

3% DevPay Fee on Value-Add

$0.05

$0.30

$0.23

N/A

$0.71

N/A

N/A

At the end of July, only some of the individual value-add amounts that you can expect to receive from your customers are greater than zero. In terms of the 3% DevPay fees, you will owe $0.05 + $0.30 + $0.23 + $0.71 = $1.29 when we charge you after August 1.

DevPay Activity Page

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

Revenue Statement for July

Your total revenue for July is $295.84. You've already received $120.64 in the form of full and prorated monthly fees (shown in the Collected column).

You're expected to pay $3.99 in DevPay fees for July. You've already paid $0.60 of that in the form of the $0.30 transaction fees we subtracted when your two new customers paid the prorated monthly charges at sign-up.

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

Finally, Customer B canceled on August 21. We refunded the customer the prorated amount to cover the 10 remaining days in July ($6.45). We then charged you that amount.

The $120.64 is the sum of:

  • The $100.00 in monthly charges for July for the five existing customers (billed on July 1)

  • The $20.64 in prorated monthly charges for July for your two new customers (billed when they signed up)

The five existing customers were billed on July 1 for the $100.00, along with the usage charges for June (discussed in the section for June). In this example, the payments came in immediately on July 1 (shown on the following DevPay Transaction History page).

On July 16 you received the money you were due from the $20.64 prorated monthly charges.

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 $1.52, $9.92, $7.70, and $23.73, and they total $42.87.

The DevPay fee also includes the $0.30 transaction fee we collect each time we charge your customers. Therefore we're charging nine instances of the $0.30 fee to cover:

  • When we billed the two new customers for the sign-up charges

  • When we later bill all seven customers for their July usage (on August 1). Even though one of your customers canceled in July, we still charge that customer for any pre-cancellation usage.

Note

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

Your DevPay Transaction History for July

Following is the DevPay Transaction History page at the end of July.

Transaction History for July

Starting at the bottom of the page:

  • The July 1 deposit of $153.80 corresponds to the July 1 billing of your customers for their June usage and the July monthly fees. To recap: On July 1 your customers paid $55.30 for their usage in June and $100.00 for the July monthly fee, so the total they paid was $55.30 + $100.00 = $155.30. If you subtract the $0.30 transaction fee per customer, the result is $153.80.

  • On July 2 we charged you $99.24 for the cost of Amazon EC2 your customers used in June, plus $0.98, which is the 3% DevPay fee on the total of the value-add amounts greater than zero. The total charge is $100.22.

  • On July 16 you received the $20.04 in prorated payments from the two new customers who signed up that day. To recap: Those two customers paid $20.64 when they signed up. If you subtract the $0.30 transaction fee per customer, the result is $20.04.

  • On July 21, Customer B canceled, and we charged you for that refund.

Your July DevPay Activity Page on August 4

On August 1 we bill your customers for their July usage and the August monthly fees. A day or so later, we bill you for the costs of Amazon EC2 used by your customers in July, and for the DevPay fees you owe for July. Customer A's payment of $27.20 on August 1 fails, but it succeeds when we retry the payment on August 7. Following is the July DevPay Activity page as displayed on August 4. The summary table at the top has been updated to reflect the latest amounts collected.

Note

If we initially can't collect a customer's payment, we contact the customer by e-mail to provide a valid credit card. We then retry the collection three times, once every 7 days. If after 21 days our retries are still unsuccessful, that payment remains uncollected. We cancel the customer's access to your product. For more information about what happens when a customer doesn't pay, see If a Customer Doesn't Pay the Monthly Bill.

Revenue Statement for July on August 4

Customer A's payment of $27.20 failed, so out of the $295.84 in revenue you're due, you're missing $7.20 in Customer A's usage-based revenue (leaving $288.64 collected so far). The other $20.00 Customer A was supposed to pay on August 1 was to cover the August monthly payment. The August DevPay Activity page would reflect that some of the August revenue was not yet collected.

Because Customer A's payment failed on August 1, you haven't yet paid all the DevPay fees you owe. Specifically, you haven't paid the $0.30 transaction fee for Customer A's payment, and you haven't paid the 3% DevPay fee (of $0.05) on Customer A's $1.52 value-add. Therefore, of the $3.99 in DevPay fees you owe, you've paid only $3.64 of it as of August 4. After Customer A's $27.20 payment succeeds, we'll subtract the $0.30 from the payment and later charge you the $0.05.

Because Customer A's payment failed, you don't have enough July revenue from Customer A to cover the AWS costs that Customer A incurred in July ($25.68). So far, Customer A has paid you only $20.00 (the July monthly fee paid on July 1). Therefore, when we collect the AWS costs for July from you on August 2, for Customer A, we collect only $20.00. Therefore, of the $263.27 in AWS costs you owe for July, you've paid only $257.59 as of August 4. Later, if Customer A's $27.20 payment goes through, then we can collect the remaining $5.68 in AWS costs (and you'll get your remaining $7.20 in revenue).

To see how the August 1 deposits and August 2 charges appear in your DevPay Transaction History, see August.

Your July DevPay Activity Page after August 8

We're able to collect Customer A's payment of $27.20 on August 7. Following is the July DevPay Activity page after August 8 (when we collected the remaining AWS costs and DevPay fees). The summary table at the top has been updated to reflect the latest amounts collected.

Revenue Statement for July after August 8

Customer A's payment of $27.20 succeeded, so you finally received the remaining $7.20 in revenue. We subtracted the $0.30 transaction fee from the payment and deposited the remainder in your Amazon Payments account. On August 8, we charged your account the remaining $5.68 in AWS costs you owe and the 3% DevPay fee of $0.05 you owe. At this point, you've received all of your July revenue, and we've collected all the AWS costs and DevPay fees for July.

To see how the August 7 deposits and August 8 charges appear in your DevPay Transaction History, see August.