Testing your integration in the Sandbox environment

The Amazon Pay and Login with Amazon Sandbox environment enables you to thoroughly test your Amazon Pay and Login with Amazon integration before going live with the Amazon Pay payment option. You can enable Sandbox mode by changing the widgets.js URL in the header of each web page where you have added an Amazon Pay button to this:

https://static-eu.payments-amazon.com/OffAmazonPayments/eur/lpa/js/Widgets.js

For the full set of Sandbox and Production endpoints, see Taking your integration live.

When you test your implementation in Sandbox mode, you can simulate the buyer experience as buyers navigate through the Amazon Pay widgets on your website. You can also test your API operation calls to Amazon to ensure that the calls are configured correctly and that the responses include all the payment parameters that you need to for tracking the entire order. The Sandbox environment even lets you simulate various error conditions to help you better manage your buyers' experiences in the event that something goes wrong during the checkout experience.

You can also test your API operation calls to Amazon Payments to ensure that the calls are configured correctly and that the responses include all the payment parameters that you need for tracking the entire order. The Sandbox environment even lets you simulate various error conditions to help you better manage your buyers' experiences in the event that something goes wrong during the checkout experience.

For example, you can test the decline flow and validate the different declines using several test credit card numbers that are provided in Sample addresses and payment instruments.

Differences between the Sandbox and Production environments

• English
• German

Button in Sandbox mode

Button in Production mode

Button in Sandbox mode

Button in Production mode

The various objects used in Amazon Pay and Login with Amazon are all managed through a set of business rules, like the amount of time until an object expires after being created. To help facilitate testing in the Amazon Pay and Login with Amazon Sandbox, the following business rule has been adjusted:

Adding test buyer accounts

When you first access the Sandbox environment through Seller Central, Amazon recommends configuring some test buyer accounts to help with your integration testing. These test accounts can be modified to suit most use cases, including the addition of shipping addresses that might violate a business rule your company has about where items can be shipped. You can configure these accounts in Seller Central by clicking Integration and choosing Test Accounts.

With the customization available through Seller Central, Amazon encourages you to test as many scenarios as you see fit through multiple test buyer accounts.

Shipping addresses and payment instruments

Sample shipping addresses and payment instruments have been added in the Sandbox environment to enable the development and debugging of the AddressBook and Wallet widgets.

When you create a test buyer account, the account is pre-loaded with test payment instruments and a set of shipping addresses. You can edit the test buyer account properties, except for the payment instruments, to simulate various purchase scenarios. The shipping address and payment instrument are rendered in the AddressBook and Wallet widgets accordingly.

You can simulate declined authorizations by using one of these preconfigured cards in the Sandbox environment. You can't simulate the ProcessingFailure error.

Billing address

A single default billing address has been added to the Sandbox environment to enable testing of addresses for your locale. The sample billing address cannot be changed. For more information, see VAT-registered sellers.

Sandbox simulations of constraints

You can simulate the PaymentMethodNotAllowed constraint in the Sandbox environment to test your code and ensure that you handle this constraint properly.

Here's how to simulate the PaymentMethodNotAllowed constraint response to the SetOrderReferenceDetails operation in Sandbox:

1. Set the SellerNote field of OrderReferenceAttributes with this simulation string: {"SandboxSimulation": {"Constraint":"PaymentMethodNotAllowed"}}
2. Choose the direct debit method from the sandbox Wallet widget.

In Sandbox, switching to and from direct debit enables or disables this constraint as long as the applicable simulation string is set. This is helpful for simulating real world scenarios in the Production environment where the constraint might appear or disappear depending upon the payment method chosen by the buyer. To reduce the likelihood of this constraint triggering in Production, we recommend that you set the OrderTotal before you render the Wallet widget.

Here is a fully encoded example:

https://mws-eu.amazonservices.com/OffAmazonPayments_Sandbox/2013-01-01
?AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE
&Action=SetOrderReferenceDetails
&AmazonOrderReferenceId=S23-1234567-1234567
&OrderReferenceAttributes.OrderTotal.Amount=106
&OrderReferenceAttributes.OrderTotal.CurrencyCode=EUR
&OrderReferenceAttributes.SellerNote={"SandboxSimulation":{
"Constraint":"PaymentMethodNotAllowed"}}
&OrderReferenceAttributes.SellerOrderAttributes.SellerOrderId=5678-23
&SellerId=YOUR_SELLER_ID_HERE
&SignatureMethod=HmacSHA256
&SignatureVersion=2
&Timestamp=2013-11-16T19:01:11Z
&Version=2013-01-01
&Signature=2RPzkOgQmDybUjk0dA54maCEXAMPLE}

For more information about the SetOrderReferenceDetails operation, including the request parameters and response elements, see SetOrderReferenceDetails in the Amazon Pay API reference guide.

Testing responses and state transitions

The following tables outline how certain responses and state transitions can be simulated. For more information about the states and reason codes, see the Introduction section of the Amazon Pay API reference guide.

Note: For states and reason codes that can be used with a simulation string, you must specify the desired State and ReasonCode in a call to an Amazon Pay API section operation. Invalid combinations result in an InvalidSandboxSimulationSpecified error.

To simulate various object states and reason codes:

Billing Agreement object

Authorization object

Capture object

Refund object

To simulate various ValidationResult and reason codes for the ValidateBillingAgreement operation:

ValidateBillingAgreement operation

The following example demonstrates how you can simulate the Authorization Declined state with reason code InvalidPaymentMethod by using the SellerAuthorizationNote request parameter:

https://mws-eu.amazonservices.com/OffAmazonPayments_Sandbox/2013-01-01
?AWSAccessKeyId=AKIAFBM3LG5JEEXAMPLE
&Action=AuthorizeOnBillingAgreement
&AmazonBillingAgreementId=C12-1234567-1234567
&AuthorizationAmount.Amount=10
&AuthorizationAmount.CurrencyCode=EUR
&AuthorizationReferenceId=test_authorize_1
&MWSAuthToken=amzn.mws.4ea38b7b-f563-7709-4bae-87aeaEXAMPLE
&SellerId=YOUR_SELLER_ID_HERE
&SellerAuthorizationNote=
    {"SandboxSimulation":{"State":"Declined",
    "ReasonCode":"InvalidPaymentMethod"}}
&SellerOrderAttributes.SellerOrderId=testSellerOrderId
&SellerOrderAttributes.StoreName=testStore
&SellerOrderAttributes.CustomInformation=ExampleInformation
&InheritShippingAddress=true
&SignatureMethod=HmacSHA256
&SignatureVersion=2
&Timestamp=2012-10-03T19:01:11Z
&TransactionTimeout=60
&Version=2013-01-01
&Signature=WlQ708aqyHXMkoUBk69Hjxj8qdh3aDcqpY71hVgEXAMPLE

See also

Taking your integration live