This extension is not maintained anymore. Please use Amazon Pay (Checkout v2) instead.
Frequently Asked Questions¶
I have successfully installed Login and Pay with Amazon extension, but when I try to go to the configuration pageI am getting: 404 Not Found error.
It’s a Magento bug, the ACL list is not reloaded after the new extension is installed. To solve this issue please logout from the Magento admin and next login again.
It is stated that the extension is compatible with Magento 1.5, but when I try to place an order I am getting an exception: Invalid method Mage_Sales_Model_Order_Payment::lookupTransaction().
Magento 1.5 doesn’t provide public wrapper for _lookupTransaction() method of order payment model, which is commonly used by Pay with Amazon extension. To fix this issue we have prepared a compatibility pack that rewrites current sales/order_payment model. You can install it via Magento Connect, to do so go to Install button., enter your admin credentials to get logged in, in the Install New Extensions section enter http://connect20.creativetest.de/Creativestyle_AmazonPaymentsCompatibilityPack key and click
Keep in mind that if any other 3rd party extension rewrites the sales/order_payment model as well, installing Magento 1.5 Compatibility Pack may lead to a rewrite conflict resulting in misfunction of one or more extensions. It is always advised to test it on a staging system prior to deploy to the production.
How can I disable Pay with Amazon for certain products?
There are few extensions available for disabling payment methods on-the-fly based on the desired conditions. We recommend to install and use Rico Neitzel’s PaymentFilter for Products and Customer Groups, which Pay with Amazon has been successfully tested against.
Lack of Pay with Amazon button in the cart is usually caused by one of the following reasons:
- incorrect Merchant ID set (double check if you don’t have any whitespaces in your Merchant ID),
- incorrect Marketplace set,
- your Amazon seller account is either blocked or not activated (you can check status of your account in Amazon Seller Central).
You can check validity of the provided Amazon Payments credentials using Validate Amazon Payments account button available in the extension settings. In case you are sure you have Merchant ID and Marketplace correctly set, check if any of the following extensions is installed and enabled in your shop and follow the instructions:
Those extensions replace default checkout.cart block with own ones. The replaced block doesn’t include checkout buttons defined previously. To bring the Pay with Amazon button back, find appropriate layout file:
noregion.xmlfor Mxperts_NoRegion extension,
ajaxaddtocart.xmlfor FME_Ajaxaddtocart extension
in your theme folder (or in the default theme folder) and modify checkout.cart.methods and / or checkout.cart.top_methods blocks by adding following code:
<block name="checkout.cart.methods" as="methods" type="core/text_list" translate="label"> (...) <block type="amazonpayments/pay_button" name="checkout.cart.methods.amazonpayments_pay.bottom" before="-"> <action method="setIdSuffix"><value>div</value></action> <action method="setEnableOr"><value>1</value></action> </block> </block> (...) <block name="checkout.cart.top_methods" as="top_methods" type="core/text_list" translate="label"> (...) <block type="amazonpayments/pay_button" name="checkout.cart.methods.amazonpayments_pay.top" before="-"> <action method="setIdSuffix"><value>top</value></action> <action method="setEnableOr"><value>1</value></action> </block> </block>
After upgrade to 3.x, when the buyer clicks Amazon Pay button in the cart, he is redirected to the customer dashboard instead of the checkout.
- Please make sure that your webserver serves the most recent version of the js/creativestyle/amazonpayments.min.js file. Some webservers (as well as CDNs) are caching static assets, so it may happen that your shop serves an outdated version of the frontend JS application.
- If you are using custom layout or template files for Amazon Pay, make sure that your customizations are compliant with the recent changes in the extension. The easiest way to check is your customization is the case is to delete following files as after refreshing Magento cache, see if this resolves your issue: