open menu
axerve docs
Payments/Alternative payments/Amazon Pay

Amazon Pay Amazon Pay


Amazon Payexternal link is a service that lets your customers use the payment methods already associated with their Amazon account to pay for goods and services. To perform a payment, users can use any of the payment methods registered in their Amazon account.


In order to integrate Amazon Pay you need to follow these operations:

  • Setup the account:

  1. Sign in on Amazon Pay Seller Central

  2. Configure Amazon Pay

  3. Generate a MWS Token

  4. Use your Amazon Pay credentials to set up your Axerve account, first in sandbox and then in production

  5. Integrate Amazon Pay button in the list of the available payment methods on your website.

  • Execute the payment:

  1. Execute the data encryption

  2. Redirect the user to the payment page

  3. Read the result and decrypt the response

  4. If you’re using Amazon Pay with the shipping address selection mode, you have to read the shipping and billing address by calling CallReadTrxS2S.

Account setup

  • Sign in on Amazon Pay Seller Central

To use Amazon Pay you must registerexternal link and follow the instructions.

  • Configure Amazon Pay

To communicate with Axerve Ecommerce Solutions sandbox and production environments, you need to access this page and follow these instructions:

  1. From the Seller Central home page, in production or sandbox view, select “Integration - Integration Central” from the navigation bar on top-left side.

2. From Integration Central page, scroll down to the “Manage client ID/store ID(s)” section, and click “View client ID/store ID(s)”.

3. If you have an existing Client or Store ID registered yet, review the configuration of the selected store. You can click on the “Edit” link on the right side to edit information.

4. f you click on the “Edit” button, you can edit all the client details.

5. From step 3, by clicking on the “Create new configuration” link on top, you will be able to create a new client configuration providing all the relevant information.


Allowed Javascript Origins

Allowed Return URLs

Allowed Return URLs Mobile

IPN Notification Urls


Allowed Javascript Origins

Allowed Return URLs

Allowed Return URLs Mobile

IPN Notification Urls

  • Generate MWS Token

The MWS Token is needed to delegate Axerve Ecommerce Solutions to operate on your behalf.

In order to generate the MWS Token:

  • On your seller account dashboard, click on the Settings menu and then on User Permissions.

  • On this page you’ll see all MWS developer permissions. Click on Authorise a Developer button to generate a new one:

  • In the next window, set this data:


Developer’s Name


Developer ID


  • Once you’ve saved the developer information in Amazon, you’ll see the MWS token in the table “Amazon MWS Developer Permissions” on the previous page (see step 2).

  • Axerve Ecommerce Solutions configuration

In the Axerve Back Office, you can insert the Amazon Pay credentials received when signed in:

The Show Address Widget checkbox allows the selection of the address from Amazon Pay during the payment by showing the widget. This setting can be disabled if the merchant sells non-shippable items (e.g. non physical goods).

Amazon Pay payment flow with the Payment Page

In order to use Amazon Pay:

  • start the payment process by calling Encrypt with mandatory data.

  • redirect the user to the payment page, passing the CryptDecryptString received in response.

  • Axerve Ecommerce Solutions will call the merchant’ Positive (or Negative) Response URL to acknowledge the status of the transaction; Axerve Ecommerce Solutions will also call the merchant’ Server-to-Server URL. The merchant has to decrypt the parameters and read the transaction status.

  • To retrieve the buyer’s address, you have to call callReadTrxS2Sapi link.

1. Encrypt

The first step is to encrypt the payment request and send it to Axerve Ecommerce Solutions. To do this, you’ll call Encryptapi link in WsCryptDecryptapi link webservice.

An Encrypt example is available in our API sectionapi link.

If you want to use the paymentType tag for this method, the value to use is AMAZONPAY. See the section Standard Payment Page to learn how to use the paymentType tag.


With Amazon Pay the ShopTransactionId must be unique.

ShopTransactionId can contains only the following characters:

  • lowercase a-z

  • uppercase A-Z

  • numbers 0-9

  • dash (-)

  • underscore (_)

  • Maximum: 32 characters

2. Redirect the user

Axerve Ecommerce Solutions will answer to your request with an EncryptResponseapi link, that will contain a field CryptDecryptString.

For test environment, redirect the user to<ShopLogin>&b=<CryptDecryptString>external link

For production environment, the url is<ShopLogin>&b=<CryptDecryptString>external link

More info on this can be found in Using Axerve payment page.

Once the buyer is redirected, and if he is not authenticated, Amazon will show a login form:

Once the buyer is logged, they will be shown a page where they can choose the shipping address from Amazon saved addresses:

Then they can choose a credit card amongst the saved amazon credit cards.

At the end, Axerve Ecommerce Solutions will perform an authorization request on the selected credit card, and the buyer will be redirected to the merchant website (positive or negative response URL).

3. Read response from Axerve Ecommerce Solutions

After the payment has been acknowledged, Axerve Ecommerce Solutions will:

  • redirect the user to the URL specified in URL for positive (or negativeresponse;

  • asynchronously call the URL Server to Server with the transaction data.

This process is described in the docs page about the standard payment pageapi link.

The payload of this call are two query parameters, the first being the shopLogin and the second being a encrypted string.

To decrypt the encrypted string you must call Decryptapi link in WsCryptDecryptapi link webservice; in the response you’ll see the transaction result.

4. Get the buyer’ shipping and billing address

To retrieve the buyer’s shipping addresses, you call callReadTrxS2Sapi link in WsS2S webserviceapi link. There, you’ll find also a response example.

The relevant data is contained in the OrderReferenceDetails tag; here we’ll report an example of the response relevant data:

1<callReadTrxS2SResponse xmlns="">
2  <callReadTrxS2SResult>
3    <GestPayS2S xmlns="">
4      ...
5      <OrderReferenceDetails>
6        <OrderReferenceStatus>
7          <State>Draft</State>
8        </OrderReferenceStatus>
9        <OrderLanguage>it-IT</OrderLanguage>
10        <Destination>
11          <DestinationType>Physical</DestinationType>
12          <PhysicalDestination>
13          <StateOrRegion>BI</StateOrRegion>
14          <Phone>33333333</Phone>
15          <City>BIELLA</City>
16          <CountryCode>IT</CountryCode>
17          <PostalCode>13900</PostalCode>
18          <Name>Marco Rossi</Name>
19          <AddressLine1>via Gobe 15</AddressLine1>
20          </PhysicalDestination>
21        </Destination>
22        <ExpirationTimestamp>2018-05-13T07:24:02.186Z</ExpirationTimestamp>
23        <IdList/>
24        <SellerOrderAttributes>
25          <SellerOrderId>4354395804398dkfjlhsdfk</SellerOrderId>
26        </SellerOrderAttributes>
27        <OrderTotal>
28          <CurrencyCode>EUR</CurrencyCode>
29          <Amount>10.00</Amount>
30        </OrderTotal>
31        <Buyer>
32          <Name>Ale</Name>
33          <Email></Email>
34        </Buyer>
35        <ReleaseEnvironment>Sandbox</ReleaseEnvironment>
36        <AmazonOrderReferenceId>S02-0319513-4657042</AmazonOrderReferenceId>
37        <CreationTimestamp>2017-11-14T07:24:02.186Z</CreationTimestamp>
38        <BillingAddress>
39          <PhysicalAddress>
40          <City>Neunkirchen</City>
41          <CountryCode>DE</CountryCode>
42          <PostalCode>66538</PostalCode>
43          <Name>Liam Barker</Name>
44          <AddressLine1/>
45          <AddressLine2>Meininger Strasse 58</AddressLine2>
46          </PhysicalAddress>
47          <AddressType>Physical</AddressType>
48        </BillingAddress>
49        <RequestPaymentAuthorization>false</RequestPaymentAuthorization>
50      </OrderReferenceDetails>
51      ...
52    </GestPayS2S>
53  </callReadTrxS2SResult>

If you want to implement your custom payment page by loading AmazonPay widgetsexternal link, you can call Axerve Ecommerce Solutions callPagamS2S (the webservice that allows to pay via server-to-server) with this data:





the Amazon Order Reference Id field received by Amazon

An example call can be found in the APIapi link.


Multiple captures on payments via AmazonPay are currently not supported in Axerve Ecommerce Solutions.

Recurring payments via Amazon Pay

With Amazon Pay you can set up recurrent payments. To do this, in the Encrypt method you can use the option amazonPayBillingAgreementDescription:

2  <shopLogin>9000001</shopLogin>
3  <uicCode>242</uicCode>
4  <amount>100</amount>
5  <shopTransactionId>34az85ord20</shopTransactionId>
6  <paymentTypes>
7    <paymentType>AMAZONPAY</paymentType>
8  </paymentTypes>
10  <!-- use this tag for recurring payments -->
11  <amazonPayBillingAgreementDescription>
12    paynowandrecurring
13  </amazonPayBillingAgreementDescription> 
14  ...

Possible values for amazonPayBillingAgreementDescription:

  • Empty – no token is returned.

  • paynowandrecurring – a payment is performed instantly and a token is generated for subsequent payments.

  • onlyrecurring – only a token is returned.

An example can be found in the API docsapi link.

To use the token for repeated payments, see CallPagamS2S.api link

Apple Paynext