3 ms·

Amazon payments for cost efficiency. We thought considered using pay pal but it was more expensive. The other nice thing about Amazon is they let payers use the

Amazon payments for cost efficiency. We thought considered using pay pal but it was more expensive. The other nice thing about Amazon is they let payers use their amazon payment accounts.

picasso81 18y ago
"The other nice thing about Amazon is they let payers use their amazon payment accounts." Hardly convenient if you don't already have an account. The layers of sign-up added to the process creates too many hoops to make users jump through.
justinsb 18y ago
Amazon payments seems very bad for repeated billings, particularly variable repeated billing. They seem to be really pushing their P2P payments, so if that's what you're doing then great, otherwise I would think twice...
- jasonkester 18y ago
  Check out their DevPay service. It's intended use is reselling Amazon Web Services with a markup, but you can also use it to do a simple recurring monthly fee. It's dead simple to set up compared to every other ecommerce system I've looked at, including Amazon SimplePay. It's almost like a loophole, finding something so dead simple that doesn't require you to run SSL at your end. If only they could roll that interface out to their other payment products.
- eob 18y ago
  Does Amazon payments allows 3rd party developers to hook into the P2P-style payments? Their web site is a bit confusing.. as a consumer, it seems that they offer me P2P micropayment services. As a developer, it seems like they just offer me the ability to bill people. What if I want to write an application that wraps around their P2P services? (Like an "Email Money" application)?
  - justinsb 18y ago
    You can definitely facilitate a P2P transaction - they have 3 entities in each transaction - the sending account, the receiving account and the calling account. All 3 can be different. Sounds like your app is exactly in the target zone for FPS - I just wish they hadn't neglected the more conventional use cases!

Amazon payments for cost efficiency. We thought considered using pay pal but it was more expensive. The other nice thing about Amazon is they let payers use their amazon payment accounts.

picasso81 18y ago

"The other nice thing about Amazon is they let payers use their amazon payment accounts." Hardly convenient if you don't already have an account. The layers of sign-up added to the process creates too many hoops to make users jump through.

justinsb 18y ago

Amazon payments seems very bad for repeated billings, particularly variable repeated billing. They seem to be really pushing their P2P payments, so if that's what you're doing then great, otherwise I would think twice...

jasonkester 18y ago
Check out their DevPay service. It's intended use is reselling Amazon Web Services with a markup, but you can also use it to do a simple recurring monthly fee. It's dead simple to set up compared to every other ecommerce system I've looked at, including Amazon SimplePay. It's almost like a loophole, finding something so dead simple that doesn't require you to run SSL at your end. If only they could roll that interface out to their other payment products.
eob 18y ago
Does Amazon payments allows 3rd party developers to hook into the P2P-style payments? Their web site is a bit confusing.. as a consumer, it seems that they offer me P2P micropayment services. As a developer, it seems like they just offer me the ability to bill people. What if I want to write an application that wraps around their P2P services? (Like an "Email Money" application)?
- justinsb 18y ago
  You can definitely facilitate a P2P transaction - they have 3 entities in each transaction - the sending account, the receiving account and the calling account. All 3 can be different. Sounds like your app is exactly in the target zone for FPS - I just wish they hadn't neglected the more conventional use cases!