An overview of CFAmazon for the Austin ColdFusion User Group.

1. CFAmazon A ColdFusion library for Amazon Services Corey Butler Ecor Group Consulting

2. Goals Vision: A single library of Amazon web services for CF developers. Serves the purpose of simplifying communication with Amazon. Predictable development patterns. Avoid common issues. Faster ramp-up. Currently focused on Amazon Payments.

3. Amazon Payments? Checkout By Amazon (CBA) A complete checkout and payment solution for ecommerce retailers. Enables millions of customers to use their trusted Amazon.com accounts on your website. Amazon Marketplace Web Services (MWS) An API for managing back-office services such as orders, inventory, fulfillment, & reporting.Supports Fulfillment by Amazon (FBA). CFAmazon supports BOTH What can I do with it? You can automate the entire sales lifecycle with web-based applications. For example, customers can buy from your site using their Amazon.com account with prices, shipping methods, discounts, taxes, etc. calculated as you see fit. If you’re using a 3rd party fulfillment center (such as Amazon), you can automate inventory levels, be alerted when shipments happen, etc. The MWS API is very powerful and flexible.

4. CBA Signed Carts (Basic Transactions) Callback API Instant Order Payment Notification (IPN/IOPN)

5. MWS REST-like Feeds Reports

6. Avoiding Common Headaches Read the Docs!!!! The API documentation is a little scattered, but reading the developer overview will help. Pay attention to the small details. The Amazon API’s are very powerful and very secure, but at the cost of simplicity. CFAmazon abstracts much of the implementation complexity, but transaction processing logic is still something you need to be aware of regardless of your selected provider. Key “Gotchas” Resolved by CFAmazon: Encoding: You can’t always use CF URL encoding/decoding (non-standard) Signatures: Generating signatures is the #1 issue I troubleshoot. Standardization: Amazon Payments is a subsidiary of Amazon. They operate several other wholly owned subsidiaries as well. Just because an API works with one Amazon service doesn’t mean it will necessarily work with another. Find the Tools Amazon provides several developer tools, such as the error console found in Seller Central. Use them! Start Small: Baby Steps Build your app one step at a time and follow OOP principles. Reusability can significantly decrease coding efforts & understanding the logic behind Amazon web services.

7. Connecting The Dots There are 2 configuration points: Amazon Your Server You must configure your Amazon Seller account and your server. Considerations: Defaults, Authentication, SSL

8. Getting Started On Amazon Read the Amazon Docs!! Setup Amazon Seller Account Configure Amazon Development Sandbox Obtain Amazon Access Keys Configure Amazon Pipeline Settings On Your Server Configure Your Development Environment Write Your Code & Test Go Live!

9. SETUP (On Amazon)

10. Seller Account: Signup http://payments.amazon.com

11. Seller Account: Sandbox & Keys

13. Make sure you use the credentials provided when you sign up:

14. Marketplace ID

15. Merchant IDSignup at https://developer.amazonservices.com

16. Seller Account: MWS Keys

17. Seller Account: CBA Settings

18. SETUP (On Your Server)

19. SSL Alert! Your server needs a valid level SSL certificate from a recognized authority in order to use CFAmazon CBA in production. Self-signed certificates are not recognized. Recommended: Use a leading authority like VeriSign Development: Use a free service like StartSSL.com or Comodo. WHY? Amazon must protect their customers & expects the same of anyone using their platform. You can develop w/o SSL, but it’s easier to get it out of the way early. Gotcha! Amazon MWS only supports SSL 2 & TLS (i.e. SSL 3.1)

20. CFAmazon Setup 1. Put com directory in web root. 2. Create response pages (post-order) 3. Create callback.cfm(if using IOPN) com directory contains the CFAmazon library. All of the other files are application-specific.

21. CODE (Finally!)

22. Seller Account: Code Tools

23. Placing an Order (Secure) https://gist.github.com/916466 <cfscript> //Create the cart cart =createObject("component","com.amazon.cba.cart"); cart.init('@ID','@SECRET','@MERCHANT',true); //Add a regular item to the cart. cart.addItem('Red Fish',19.99,1); //Add a customized item to the cart. item =createObject("component","com.amazon.cba.item"); item.init('Blue Fish',29.99,1); item.setWeight(1.75,"lb"); cart.addCustomItem(item); </cfscript> <html> <head> <script language="javascript" src="https://payments-sandbox.amazon.com/cba/js/PaymentWidgets.js"></script> <title>XML Signed Cart Example</title> </head> <body> <div id="signedBtn"/> <cfoutput> <script> newCBA.Widgets.StandardCheckoutWidget({ merchantId:'#cart.merchantID#', orderInput:{ format:"XML", value: "type:merchant-signed-order/aws-accesskey/1;order:#toBase64(cart.getXml())#;"+ "signature:#cart.getXmlSignature()#;aws-access-key-id:#cart.accessKeyID#" }, buttonSettings:{size:'large',color:'orange',background:'green'} }).render("signedBtn"); </script> </cfoutput> </body> </html>

24. Results

25. Behind the Scenes Construct XML object (cart) Generate Signature (HMAC-SHA256) Construct Request String Encode Request Set Request Headers (as appropriate)

26. Signatures https://gist.github.com/916846 Signatures are one of the most frequent problem areas for new users. READ THE DOCS!! For the nuances of each service.

27. MWS Challenges CF8 had SSL connectivity issues Some CF hosts use page caching or cache servers based on URL.

28. That’s It! Get It https://github.com/ecorgroup/cfamazon http://cfamazon.riaforge.org Contact http://www.coreybutler.com http://www.linked.com/in/ecorsystems @goldglovecb, @ecorgroup Meetup Facebook