| « PreviousNext » | |
  | Did this page help you? Yes | No | Tell us about it... |
Testing Signatures
You can easily test your signature creation code using any of the examples in Amazon FPS API Reference. Each example contains a signature calculated from the values in the rest of the example.
Copy any one of the sample query request examples from among the Actions in Amazon FPS API Reference.
Remove the HTTP verb (GET or POST) and the URI from your copy. Also remove the explicit '\n' characters.
Remove the line with the
Signatureparameter from your copy.Create a signature using the instructions in Generating a Signature
Compare the output from your signature creation code with the value you removed from the HTML example. They should be identical.
Migrating your Application from the Sandbox to Production
When your application is running correctly in the sandbox, you need to do the following to switch it to the production environment:
Launch Process
|
1 |
Change the Amazon FPS sandbox endpoint to the Amazon FPS live endpoints as listed in the following table:
| ||||||||
|
2 |
If your application is set up to receive IPN notifications, set its IPN URL at https://payments.amazon.com/sdui/sdui/managecobranding. | ||||||||
|
3 |
Please ensure you have specified your co-branding URL on production using the form at https://payments.amazon.com/sdui/sdui/managecobranding. | ||||||||
|
4 |
Please ensure that the rest of your account settings are current at https://payments.amazon.com/sdui/sdui/accountsettings. |
You can use the same credentials to sign your requests as long as your Amazon Payments Developer account on both Sandbox and Production are linked to the same email address and password.
