 | Feedback |  |
Amazon FPS provides an environment called the sandbox for testing your applications. In the sandbox you can try out your applications without incurring charges or making purchases. We recommend that you test all of your requests in the sandbox before exposing them on your web site.
The Amazon FPS Sandbox enables you to try the following:
Make Amazon FPS web service and Co-Branded service requests
Make Pay requests to transfer money
Use credit cards and bank accounts in your test transactions without any prior verification and without incurring charges
Simulate errors
You can simulate certain errors that could appear in a real transaction. This simulation can help you test the error handling capabilities in your application.
For information about signing up for an Amazon FPS Sandbox account, go to the Amazon Flexible Payments Service Getting Started Guide. For more information about the Amazon FPS Sandbox, go to https://payments-sandbox.amazon.com.
Sandbox endpoints are different from Amazon FPS production endpoints. The Amazon FPS Sandbox endpoints are as follows:
Amazon FPS API sandbox— https://fps.sandbox.amazonaws.com
Amazon Co-Branded service sandbox— https://authorize.payments-sandbox.amazon.com/cobranded-ui/actions/start
You can test the following user experiences in the sandbox:
Registering for a business or personal account via a Co-Branded service request
Depositing funds into a test account's Amazon Payments account using a
Pay request
Checking the account balance for a test account
Checking the activity for a test account
The sandbox accepts any random number as a credit card and token ID in Pay
and Reserve requests. However, you can simulate a variety of declines that
occur by using a specific token IDs and Amounts in the sandbox, as shown in
the following three tables.
The following table shows the errors you can simulate by entering specific
SenderTokenId values.
| Error | SenderTokenId Value |
|---|---|
| Email address not verified |
|
| Suspended account |
|
| Closed account |
|
The following table shows the errors you can simulate by entering specific
RecipientTokenId values. These token IDs are relevant only in
marketplace environments.
| Error | RecipientTokenId Value |
|---|---|
| Email address not verified |
|
| Suspended account |
|
| Closed account |
|
The following table shows the errors you can simulate by entering specific
Amount values.
| Error | Amount Value |
|---|---|
| Failure | Amounts that include a "7" or "8" after a decimal point of the form
N.7n or N.8n, where N
and n are any numbers, for example, 20.7, 100.73, 4.8,
0.81 |
