… in accordance with the Amazon FPS spec: http://docs.amazonwebservices.com/AmazonFPS/latest/FPSMarketplaceGuide/index.html?Reserve.html
…e supposed to stop supporting signature v1 on November 1st -- however, signature v1 was still working with my webapp until I finally had time to do this ... <checks watch> ... on November 17th. So hard to know how long they will support signature v1, but best to upgrade ASAP. * Using the utilities Amazon provided for Ruby (in lib/amazon/fps): http://aws.amazon.com/code/Amazon-FPS/3022 * This can't just be dropped into place -- when using the gem in your Ruby code, when you create an object to process a PipelineResponse or an IpnRequest, you must additionally pass the request.url and your FPS_SECRET_KEY ... here see diffs: pipeline_response = Remit::PipelineResponse.new( params, + request.url, + FPS_ACCESS_KEY, FPS_SECRET_KEY ) ipn_request = Remit::IpnRequest.new( params, + request.url, + FPS_ACCESS_KEY, FPS_SECRET_KEY ) * Tests updated and passing.
…. it's an undocumented feature, described here: http://developer.amazonwebservices.com/connect/thread.jspa?messageID=121716𝭴 "you can set the value of the parameter, collectEmailAddress, to true when you are redirecting the sender to CBUI. When the sender is redirected back to your website, you will receive the sender's email address as part of the return URL" on return, buyer's email comes back in `params['senderEmail']` (i tried it, it works.)