Amazon FPS

Amazon FPS

Setting Up Amazon FPS for FoxyCart

Obtain your Access Key ID and Secret Access Key at https://portal.aws.amazon.com/gp/aws/securityCredentials. Input these values into appropriate fields at FoxyCart admin.


Obtaining a Test Account

Create a separate Access Key ID / Secret Access Key pair at https://portal.aws.amazon.com/gp/aws/securityCredentials.

Test Card Numbers

With the Amazon Payments developer sandbox, you can force an error by placing certain decimal values in the amount.

  • The amount includes a decimal value between .60 and .69 Temporary Decline (Occurs when a downstream process is not available)
  • The amount includes a decimal value between .70 and .89 Payment Error (Insufficient funds)

Troubleshooting & Interpreting Response Codes

Contact amazon fps for info. Know more? Feel free to edit this page with info.

Important Notes and Caveats

Action required: Phone number required

Current Amazon FPS requires that a phone number be submitted with the order, but by default the phone field on the checkout is optional. We plan to dynamically update this requirement out of the box, but in the meantime, if you are using this gateway you'll need to add some javascript to your checkout to make the phone field required. See this page for details of how to do that.

Action required: Custom flat rate shipping on checkout

If you are changing the shipping values on the checkout using flat rates, you'll need to hide the button from the cart using CSS. Amazon FPS has a restriction that once the customer has been authorized, the payment total can't be increased. By sending the customer to the checkout first, their final total can be correctly calculated.

Possible Action: Datafeed Handling

An Amazon FPS transaction may not process instantly, so at the time we process the initial transaction, we don't know if it was approved or not. To handle this, transactions are initially marked as pending, and when we get a confirmation from Amazon on the result of the transaction, we update it accordingly. Each time the status changes, a datafeed will be sent to your endpoint if configured with the transaction details and the status node will be present.

The status node can contain one of three different values: pending, approved or rejected. Depending on the types of actions you're needing to perform at your datafeed endpoint, you need to make sure the appropriate status value is present.

User Notes and Experiences

If you have tips, experience, or helpful notes related to this gateway that would benefit others, please add them below, including your name and the date. We reserve the right to edit or remove comments that don't add value to this page.

Site Tools