Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« Start-Up Tour Round-Up (Part I) | Main | Coming Soon: Amazon EC2 With Windows »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c534853ef010534d34ce6970c

Listed below are links to weblogs that reference New Release of DevPay - Lower Fees and Reduced Risk:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Felix

Hi Jeff,

When are you going to offer the DevPay service to European developers? We do not have US bank accounts. Amazon has several European stores so i don't see why it takes so long.

John Luxford

I'll echo Felix and ask the same for Canada. It would be great to have an option like DevPay up here. So far, DevPay, Google Checkout, and Paypal Pro are all US-only (rather, Paypal Pro is 3x the price in Canada, making it unreasonable to choose). I'd love to see some competition, specifically from a flexible option like DevPay, come to Canada and shake things up. We have startups and developers too!!! :)

Jim Wilcoxson

If a developer writes a program that uses AWS and sells it at a fixed cost, and uses DevPay to bill customers using the service without markup, why should the developer pay any fees (the 30 cent transaction fee), and why should the developer be responsible to Amazon if the customer doesn't pay? By making his AWS application available, the developer has given Amazon an ongoing AWS customer and is not (in this case of no markup) making any money from the customer after the initial purchase of the application.

If the developer uses DevPay in the future to bill the customer for something other than AWS charges, perhaps for an application upgrade, then I can see where the developer pays the 3%, the 30 cent fee, and loses if the customer doesn't pay.

But for the developer to owe money to Amazon for a customer who doesn't pay, even though the developer is not marking up the service, does not make sense.

The changes are good, but you need to go a little further down the same road Jeff. :-)

Jim

Justin Kruger

Other features that amazon should implment.

*charging customers for public S3 files.

*allowing us to charge items by proxy, like instance hours.
-in this case, lets say we have a web service that process video, images, music or some sort of data. obviously we would like to manage the scalability of that app, and charge the user for only what they use. in a few situations, as the developer we might need to have a few things up and running, but it would be nice to charge for that service via processing time, or other metrics that we come up with. so, persay, per instance hour, per image, per movie, per video, per file, per audio file, etc.....

in eccense processing that video or file becomes a job and to some how set a price for that service would be grand.

The comments to this entry are closed.

Featured Events

The AWS Report


Brought to You By

Jeff Barr (@jeffbarr):



Jinesh Varia (@jinman):


Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30