The Instant Order Processing Notification API Guide

User Manual:

Open the PDF directly: View PDF .
Page Count: 34

Download
Open PDF In Browser	View PDF

The Instant Order
Processing
Notification API
Guide
A reference guide for developers who want to automate order notifications
with their Checkout by Amazon orders.

The Instant Order Processing Notification API Guide

Table of Contents
1

7
8

Overview of the Instant Order Processing Notification API .............................................................1
1.1 Prerequisites for Using the Instant Order Processing Notification API .........................................1
1.2
Your Tasks When Using the Instant Order Processing Notification API ....................................1
1.3
Other Documentation.................................................................................................................. 2
1.4
What’s New in This Document .................................................................................................... 3
Specifications....................................................................................................................................... 4
2.1
Order Notifications Content ........................................................................................................ 4
2.2
Order Notification Types ............................................................................................................. 4
2.2.1 1. New Order Notification ........................................................................................................ 4
2.2.2 2. Order Ready-to-Ship Notification ........................................................................................ 4
2.2.3 3. Order Canceled Notification ................................................................................................ 4
2.3
The Order Notification Flow ........................................................................................................ 5
2.4
Notifications and Multiple Checkouts......................................................................................... 5
Enabling the Instant Order Processing Notification API .................................................................. 7
3.1.1 Set or Edit Your Endpoint URL ................................................................................................ 7
3.2
Retries to the Endpoint ............................................................................................................... 9
Receiving and Processing Notifications .......................................................................................... 10
4.1
The Notification Content ........................................................................................................... 10
4.1.1 1. The UUID .............................................................................................................................. 12
4.1.2 2. The Timestamp .................................................................................................................... 12
4.1.3 3. The Signature ......................................................................................................................13
4.1.4 4. The NotificationType ..........................................................................................................13
4.1.5 OrderCancelledNotification....................................................................................................13
4.1.6 5. The NotificationData ...........................................................................................................13
4.1.7 6. The AWSAccessKeyId ........................................................................................................ 16
Processing the Notification Request ................................................................................................ 17
5.1.1 1. Parse the Request Data ....................................................................................................... 17
5.1.2 2. Verify that the Notification Request Is Valid...................................................................... 17
5.1.3 3. Process the Data ................................................................................................................ 18
5.1.4 4. Respond to the Request .................................................................................................... 18
Using Custom Data Fields ................................................................................................................. 19
6.1
Prerequisites for Using Custom Data Fields ............................................................................. 19
6.2
How We Process the Custom Data Fields ................................................................................. 19
6.3
Modifying Your Order XML to Use Custom Data Fields........................................................... 19
6.4
Using Custom Data Fields with the Instant Order Processing Notification API ..................... 20
6.5
Using a Custom Namespace as Part of the Custom Data Entry ............................................... 21
Appendix A—the Instant Order Processing Notification API Schema.......................................... 24
Appendix B—Frequently Asked Questions ..................................................................................... 27
8.1
What is the Instant Order Processing Notification API? .......................................................... 27
8.2
What are order notifications? .................................................................................................... 27
8.3
How does the Instant Order Processing Notification API benefit me?................................... 27
8.4
What are the prequisites for using the Instant Order Processing Notification API? .............. 27
8.5
Where are Instant Order Processing Notification API messages sent? .................................. 27
8.6
What messages can I receive and when will I receive them? .................................................. 28
8.7
Why am I not receiving an Instant Order Processing Notification API message? .................. 28

© 2009-10 Amazon.com, Inc. or its Affiliates
8.8
Why did I receive an Order Canceled Notification or Order Ready-to-Ship notification before
the New Order notification for the same order?.................................................................................. 28
8.9
Why did I receive an Order Canceled notification before an Order Ready-to-Ship notification
for the same order? ................................................................................................................................ 29
8.10 What do I do if I get a notification request with a duplicate UUID? ....................................... 29
8.11
What happens if my service or endpoint is unavailable? ......................................................... 29
8.12 What is the 14-day Exponential Back-off Retry Policy? ............................................................ 29
8.13 What should I do if I cannot process the notification I receive? ............................................. 29
8.14 How do I authenticate order notifications?.............................................................................. 30
8.15 Why did I receive an order notification with items referring to multiple carts?..................... 30
8.16 Why did I receive an order notification with fewer items than were in the submitted cart? 30
8.17 I received a New Order Notification. Should I ship the order now? ........................................ 30

iii

Overview of the Instant Order Processing Notification API

Order notifications inform you about new orders or status changes for existing orders placed using
Checkout by Amazon. When you receive these notifications, you can pass them to your internal order
management system (OMS) and then process the orders.
An instant order notification is an HTTPS POST request, issued when the order is placed or changed,
containing the XML-based notification data in its body. To use the Instant Order Processing
Notification API, you must be running a web service that can receive the Checkout by Amazon
notifications and then pass the required information to your internal order fulfillment system.
This document shows the types and structure of different notifications. This document also explains
how you can enable notification, how to authenticate notifications, and how to process the received
notifications.

1.1

Prerequisites for Using the Instant Order Processing Notification API

Before you can use the Instant Order Processing Notification API, your systems must meet the
following prerequisites.
You must be using the order.xsd version 2009-05-15 or later. (Download the latest version
here.)
2. You must be using the iopn.xsd version 2008-11-30 or later. (Download the latest version
here.)
3. You must be running a web service that can receive HTTPS POST requests made to your
endpoint using port 443.
4. Your HTTPS must use valid SSL certificates from a trusted certificate provider. To view a
complete list of acceptable SSL certificate providers, please see “Accepted SSL Certificates”
in the Callback API Guide (PDF).
1.

1.2

Your Tasks When Using the Instant Order Processing Notification API

You have two tasks to accomplish when using the Instant Order Processing Notification API:
1. Enable Order Notifications.
2. Process the Order Notifications.
The rest of this document discusses how to accomplish these two tasks.

The Instant Order Processing Notification API Guide

1.3

Other Documentation

You can read our downloadable files (PDF) to understand more about Checkout by Amazon.
Resource
Getting Started Guide
(PDF)

Implementation Guide
Using the Create
Checkout Button Feature
(PDF)
Implementation Guide
Using HTML-based
Button Code and
Shopping Carts (PDF)
Implementation Guide
Using XML-based Button
Code and Shopping Carts
(PDF)
Using Seller Central (PDF)
Best Practices Guide
(PDF)

Audience, Purpose, and Goals
For merchants who want to use a simple, step-by-step approach in setting
up Checkout by Amazon on their websites, from start to finish. The Getting
Started Guide walks merchants through the process, from gathering the
required information for signing up for an account setting up a button on
their websites.
For merchants who want detailed information about integrating their
website with Checkout by Amazon using the Create Checkout Button
feature in Seller Central. Designed for a simple copy-and-paste HTML
solution for your webpages.
For merchants and developers who want detailed information about
integrating their website with Checkout by Amazon using HTML-based
buttons and shopping carts. Designed for HTML-based integration.
For merchants and developers who want detailed information about
integrating their website with Checkout by Amazon using XML-based
buttons and shopping carts. Designed for XML-based integration.

For merchants who want an overview of Seller Central.
Contains the best tips for merchants who want to set up their websites to
use Amazon Payments, with advice for planning, setting up, and day-to-day
operations.
Launch Checklist (PDF)
For merchants and developers planning to set up and use Checkout by
Amazon on their site.
Callback API Guide (PDF)
For developers who want to build their own applications to calculate
shipping and tax rates as well as promotional discounts and then send these
results to Checkout by Amazon.
Developer Cheat Sheet for For developers who want a quick, 1-page summary of how to enable
the Callback API (PDF)
callbacks.
Instant Order Processing
For developers who want to automate order notifications with Amazon
Notifications API Guide
Payments.
(PDF)
Using Custom Data Fields For merchants and developers who want to include custom data fields in
(PDF)
their carts.
The Checkout by Amazon For merchants and developers who want to use the Checkout by Amazon
Shopping Cart Guide
Shopping Cart on their site.
(PDF)
Using Checkout by
For developers interested in Checkout by Amazon as an alternate payment
Amazon as a Payment
method on their site.
Option (PDF)
Open-Source Shopping
For developers interested in open-source carts that support Checkout by
Cart Solutions (PDF)
Amazon (currently osCommerce 1.x and Zen Cart).

Audience, Purpose, and Goals
For developers interested in the osCommerce open source cart, v. 2.0 and
greater.

1.4

What’s New in This Document

Ver
1.8
1.7
1.0

Date
2011-10-31
2010-05-30
2009-02-01

Changes
Updated to reflect current functionality
Update for Implementation Guide
Initial Release

The Instant Order Processing Notification API Guide

Specifications

The following section specifies the content and type of order notifications you can receive.

2.1

Order Notifications Content

This is general format for the content of an order notification. For details of these parameters, please
see Appendix A - The Instant Order Processing Notification API Schema.

2.2

Order Notification Types

Order notifications are HTTPS POST requests containing the notification data formatted as XML. You
can receive one of three types of notifications:
1. New Order Notification
2. Order Ready-to-Ship Notification
3. Order Canceled Notification
2.2.1

1. New Order Notification
We send you this notification when a new order is placed. Generally, this notification is sent
immediately when the order is first created; however, there is a 90-minute delay for 1-Click®
or Express Checkout orders.

Note
Do not ship an order when you receive the New Order notification. Please wait until you
receive the Order Ready-to-Ship notification.
2.2.2

2. Order Ready-to-Ship Notification
We send you this notification when we authorize the buyer’s payment method. This
notification indicates that you can fulfill the order (send the items to the buyer).

Note
Do not ship an order until you receive this Order Ready-to-Ship notification.
2.2.3

3. Order Canceled Notification
We send you this notification when the order is canceled. An order can be canceled by the
seller, the buyer, or Amazon Payments.

© 2009-11 Amazon.com, Inc. or its Affiliates
Note
No other details of the cancellation beyond this notification are provided.

2.3

The Order Notification Flow

This image shows the notification flow; that is, the order you can expect notifications to arrive in.
Note that the state changes shown in yellow result in notifications.

In some cases, the New Order notification might arrive after the Order Ready-to-Ship or Order
Canceled notifications. See Why Did I Receive an Order Canceled Notification or Order Ready-to-Ship
Notification Before the New Order Notification for the Same Order? for more information about
these issues.

2.4 Notifications and Multiple Checkouts
For multiple checkouts that are consolidated into a single Amazon Order ID, merchants will receive
only one NewOrderNotification and OrderReadyToShipNotification Instant Order
Processing Notification message. Each checkout has distinct CartId, and for the consolidated

The Instant Order Processing Notification API Guide
orders, there will be multiple distinct CartIds in new and ready-to-ship Instant Order Processing
Notification messages.

Enabling the Instant Order Processing Notification API

To enable the Instant Order Processing Notification API, log in to Seller Central and specify your
Merchant URL endpoint (on your web service), your Integrator’s endpoint (on your Integrator’s web
service), or both. You must enter at least one endpoint URL to enable Instant Order Processing
Notification API. If you do not have an Integrator, you do not need to specify the Integrator
endpoint.
The following screen shot shows the new Instant Order Processing Notifications Settings section in
the Checkout Pipeline Settings page.

To set or edit the endpoint settings, follow these instructions:
3.1.1
1.

Set or Edit Your Endpoint URL
Log in to Seller Central.

The Instant Order Processing Notification API Guide
2. Click Settings > Checkout Pipeline Settings and then click Edit.
The following screen appears:

3. In the Merchant URL box, enter the endpoint on your web service that accepts notifications.
Remember to use https:// for your Production account.
4. In the Integrator URL box, enter the endpoint on your integrator’s web service that accepts
notifications.
Remember to use https:// for your Production account.

3.2

Click Update.
The endpoint URLs appear on the Settings page:

Retries to the Endpoint

The following explains how retries are handled to the endpoint




If both the Merchant URL and Integrator URL are set, then notifications are sent to both
endpoints.
If only one endpoint is set, then notifications are sent only to that endpoint.
If a specified endpoint is down (not available), then retries are done only for that endpoint.

If an endpoint URL is not available or not responding to the notification request, then the
notification is re-sent to the URL according to the Retry Policy.
Note
You must specify at least one endpoint when you use the Instant Order Processing
Notification API.

The Instant Order Processing Notification API Guide

Receiving and Processing Notifications

To enable the Instant Order Processing Notification API, you must establish a web service that
receives and processes Checkout by Amazon notifications. Your web service must be secured by SSL
v3 or TLS and must use a valid SSL certificate. The URL you use for your Production account must use
HTTPS and the default secure port 443. The URL you use for your Sandbox account can use either
port 443 (for secure HTTPS requests) or port 80 (for unsecure HTTP requests).
Notes
If your receiver end point is down, Checkout by Amazon will retry sending the notification for
14 days. For information on the frequency of these notification retries, please see the Retry
Policy.
To view a complete list of acceptable SSL certificate providers, please see “Accepted SSL
Certificates” in the Callback API Guide (PDF).
Checkout by Amazon authenticates the notification by calculating a Signature using the
merchant’s Seller Central AWS Secret Access Key. The following sections explain the contents of the
notification.
Notes
You cannot use your X.509 key pair to calculate your signature—you must use your Seller
Central AWS Secret Access Key.
You might have a separate AWS account with its own public-private key pair. Be sure you use
the Seller Central AWS Secret Access Key to validate and generate signatures for requests
and responses – this is the key you find in Seller Central on the Integration > Access Key
page.

4.1

The Notification Content

The notification we send you is a simple string, URL-encoded and formatted using UTF-8. The request
contains following six sections.
Entry
1. The UUID

2. The Timestamp

3. The Signature
4. The NotificationType
10

Definition
A Universally Unique Identifier, unique for each
notification, whether it’s the original notification
or a retried notification.
The request time using GMT, unique for each
notification, whether it’s the original notification
or a retried notification.
Calculated using the UUID, the Timestamp, and
your Seller Central AWS Secret Access Key.
The notification type, which can be

Inclusion
Only for signed carts

Only for signed carts

Only for signed carts
Always included

5. The NotificationData
6. The AWSAccessKeyId

NewOrderNotification,
OrderReadyToShipNotification, or
OrderCancelledNotification.
The content (body) of the request
The Seller Central AWS Access Key ID used to sign
the cart.

Always included
Only for signed carts

Note that Signature and Timestamp have an initial capital letter. UUID is all capital letters.
NotificationData, and NotificationType are “camel-capped.”
This request is a set of key-value pairs, concatenated as one string, with each key-value pair delimited
using the standard “&” character. The key is in plain text, and the value is URL-encoded.
The request contains the following key-value pairs. The order is not important (the spaces are for
clarity):
UUID=[UUID_value] & Timestamp=[Timestamp_value] & Signature=[Signature_value] &
NotificationType=[notification_type] & NotificationData=[notification_data_value] &
AWSAccessKeyId=[ AWSAccessKeyId_value]

Here is an example of a New Order Notification:
UUID=5d1769d2-b217-4981-a499-fbad1b9acf15&Timestamp=2009-01-20T06%3A41%3A20.471Z&AWSAccessKe
yId=AKIAJC2EVPPNIFRXIVKQ&Signature=Ltu1alXSqkyZRqzVSjI%2BDPuWQms%3D&NotificationType=NewOrde
rNotification&NotificationData=%3C%3Fxml%20version%3D%221.0%22%20encoding%3D%22UTF-8%22%3F%3
E%0A%3CNewOrderNotification%20xmlns%3D%22http%3A%2F%2Fpayments.amazon.com%2Fcheckout%2F200905-15%2F%22%3E%0A%20%20%3CNotificationReferenceId%3Eae51d3a6-7843-4cbb-ad1d-ee8cc591e10d%3C%
2FNotificationReferenceId%3E%0A%20%20%3CProcessedOrder%3E%0A%20%20%20%20%3COrderChannel%3EAm
azon%20Checkout%20%28Live%29%3C%2FOrderChannel%3E%0A%20%20%20%20%3CAmazonOrderID%3E101-12345
67-9876543%3C%2FAmazonOrderID%3E%0A%20%20%20%20%3COrderDate%3E2009-08-31%3C%2FOrderDate%3E%0
A%20%20%20%20%3CBuyerInfo%3E%0A%20%20%20%20%20%20%3CBuyerName%3EKelly%20Green%3C%2FBuyerName
%3E%0A%20%20%20%20%20%20%3CBuyerEmailAddress%3Esomeone%40amazon.com%3C%2FBuyerEmailAddress%3
E%0A%20%20%20%20%3C%2FBuyerInfo%3E%0A%20%20%20%20%3CShippingAddress%3E%0A%20%20%20%20%20%20%
3CName%3EKelly%20Green%3C%2FName%3E%0A%20%20%20%20%20%20%3CAddressFieldOne%3E123%20Oak%20Ave
nue%20SE%20%3C%2FAddressFieldOne%3E%0A%20%20%20%20%20%20%3CAddressFieldTwo%3EApt.%20221-B%20
%3C%2FAddressFieldTwo%3E%0A%20%20%20%20%20%20%3CCity%3ESeattle%3C%2FCity%3E%0A%20%20%20%20%2
0%20%3CState%3EWA%3C%2FState%3E%0A%20%20%20%20%20%20%3CPostalCode%3E98104-1234%3C%2FPostalCo
de%3E%0A%20%20%20%20%20%20%3CCountryCode%3EUSA%3C%2FCountryCode%3E%0A%20%20%20%20%3C%2FShipp
ingAddress%3E%0A%20%20%20%20%3CShippingServiceLevel%3EStandard%3C%2FShippingServiceLevel%3E%
0A%20%20%20%20%3CProcessedOrderItems%3E%0A%20%20%20%20%20%20%3CProcessedOrderItem%3E%0A%20%2
0%20%20%20%20%20%20%3CAmazonOrderItemCode%3E12345%3C%2FAmazonOrderItemCode%3E%0A%20%20%20%20
%20%20%20%20%3CMerchantId%3EAEIOU1234AEIOU%3C%2FMerchantId%3E%0A%20%20%20%20%20%20%20%20%3CS
KU%3EABC123%3C%2FSKU%3E%0A%20%20%20%20%20%20%20%20%3CTitle%3ERed%20Fish%3C%2FTitle%3E%0A%20%
20%20%20%20%20%20%20%3CDescription%3EA%20red%20fish%20packed%20in%20spring%20water.%3C%2FDes
cription%3E%0A%20%20%20%20%20%20%20%20%3CClientRequestId%3E12345%3C%2FClientRequestId%3E%0A%
20%20%20%20%20%20%20%20%3CCartId%3Emiq%3A%2F%2Frose%3A1.0%2Fcart%2Fcba%3A1.0%2Fcart%3A2.0%2F
AZ4B0ZS3LGLX%2FA3DBMG2ZGA2JEQ%2F1-1232431180394-57EEF607E6D40DB5%3C%2FCartId%3E%0A%20%20%20%
20%20%20%20%20%3CIntegratorId%3EVWXYZ98765VWXYZ%3C%2FIntegratorId%3E%0A%20%20%20%20%20%20%20
%20%3CIntegratorName%3Ewww.IntegratorWorld.com%3C%2FIntegratorName%3E%0A%20%20%20%20%20%20%2
0%20%3CPrice%3E%0A%20%20%20%20%20%20%20%20%20%20%3CAmount%3E5.0%3C%2FAmount%3E%0A%20%20%20%2
0%20%20%20%20%20%20%3CCurrencyCode%3EUSD%3C%2FCurrencyCode%3E%0A%20%20%20%20%20%20%20%20%3C%
2FPrice%3E%0A%20%20%20%20%20%20%20%20%3CQuantity%3E1%3C%2FQuantity%3E%0A%20%20%20%20%20%20%2
0%20%3CWeight%3E%0A%20%20%20%20%20%20%20%20%20%20%3CAmount%3E1.0%3C%2FAmount%3E%0A%20%20%20%
20%20%20%20%20%20%20%3CUnit%3Elb%3C%2FUnit%3E%0A%20%20%20%20%20%20%20%20%3C%2FWeight%3E%0A%2
0%20%20%20%20%20%20%20%3CFulfillmentNetwork%3EMERCHANT%3C%2FFulfillmentNetwork%3E%0A%20%20%2
0%20%20%20%20%20%3CItemCharges%3E%0A%20%20%20%20%20%20%20%20%20%20%3CComponent%3E%0A%20%20%2

The Instant Order Processing Notification API Guide
0%20%20%20%20%20%20%20%20%20%3CType%3EPrincipal%3C%2FType%3E%0A%20%20%20%20%20%20%20%20%20%2
0%20%20%3CCharge%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CAmount%3E5.0%3C%2FAmount%
3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCurrencyCode%3EUSD%3C%2FCurrencyCode%3E%0A
%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FCharge%3E%0A%20%20%20%20%20%20%20%20%20%20%3C%2FCo
mponent%3E%0A%20%20%20%20%20%20%20%20%20%20%3CComponent%3E%0A%20%20%20%20%20%20%20%20%20%20%
20%20%3CType%3EShipping%3C%2FType%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%3CCharge%3E%0A%2
0%20%20%20%20%20%20%20%20%20%20%20%20%20%3CAmount%3E0.0%3C%2FAmount%3E%0A%20%20%20%20%20%20%
20%20%20%20%20%20%20%20%3CCurrencyCode%3EUSD%3C%2FCurrencyCode%3E%0A%20%20%20%20%20%20%20%20
%20%20%20%20%3C%2FCharge%3E%0A%20%20%20%20%20%20%20%20%20%20%3C%2FComponent%3E%0A%20%20%20%2
0%20%20%20%20%20%20%3CComponent%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%3CType%3ETax%3C%2F
Type%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%3CCharge%3E%0A%20%20%20%20%20%20%20%20%20%20%
20%20%20%20%3CAmount%3E0.0%3C%2FAmount%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCur
rencyCode%3EUSD%3C%2FCurrencyCode%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FCharge%3E%0
A%20%20%20%20%20%20%20%20%20%20%3C%2FComponent%3E%0A%20%20%20%20%20%20%20%20%20%20%3CCompone
nt%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%3CType%3EShippingTax%3C%2FType%3E%0A%20%20%20%2
0%20%20%20%20%20%20%20%20%3CCharge%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CAmount%
3E0.0%3C%2FAmount%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCurrencyCode%3EUSD%3C%2F
CurrencyCode%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FCharge%3E%0A%20%20%20%20%20%20%2
0%20%20%20%3C%2FComponent%3E%0A%20%20%20%20%20%20%20%20%20%20%3CComponent%3E%0A%20%20%20%20%
20%20%20%20%20%20%20%20%3CType%3EPrincipalPromo%3C%2FType%3E%0A%20%20%20%20%20%20%20%20%20%2
0%20%20%3CCharge%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CAmount%3E0.0%3C%2FAmount%
3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CCurrencyCode%3EUSD%3C%2FCurrencyCode%3E%0A
%20%20%20%20%20%20%20%20%20%20%20%20%3C%2FCharge%3E%0A%20%20%20%20%20%20%20%20%20%20%3C%2FCo
mponent%3E%0A%20%20%20%20%20%20%20%20%20%20%3CComponent%3E%0A%20%20%20%20%20%20%20%20%20%20%
20%20%3CType%3EShippingPromo%3C%2FType%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%3CCharge%3E
%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3CAmount%3E0.0%3C%2FAmount%3E%0A%20%20%20%20%2
0%20%20%20%20%20%20%20%20%20%3CCurrencyCode%3EUSD%3C%2FCurrencyCode%3E%0A%20%20%20%20%20%20%
20%20%20%20%20%20%3C%2FCharge%3E%0A%20%20%20%20%20%20%20%20%20%20%3C%2FComponent%3E%0A%20%20
%20%20%20%20%20%20%3C%2FItemCharges%3E%0A%20%20%20%20%20%20%3C%2FProcessedOrderItem%3E%0A%20
%20%20%20%3C%2FProcessedOrderItems%3E%0A%20%20%3C%2FProcessedOrder%3E%0A%3C%2FNewOrderNotifi
cation%3E

The key is in plain text (in red) and the value is URL-encoded; each key-value pair is delimited using
the “&” character.
The following section explains the six components in the Instant Order Processing Notification API
request you receive and how you can use them to build your response.
4.1.1
1. The UUID
The UUID (Universally Unique Identifier) is a string created by AWS (Amazon Web Services).
Here is an example of the UUID in the request you receive:
UUID=d6a58609-d9ea-415c-95c6-d7c2528fca09

You’ll use this UUID later when you calculate the Signature to validate the request. (If you did not
specify that you accept only signed carts, you will not receive the UUID in your merchant request.)
4.1.2 2. The Timestamp
The Timestamp is the date and time the request was sent from our servers.
Here is an example of the Timestamp in the request you receive:
Timestamp=2008-11-14T20%3A57%3A07.146Z

© 2009-11 Amazon.com, Inc. or its Affiliates
This evaluates to 14-Nov-2008 at 20:57:07.146 Greenwich Mean Time, or 14-Nov-2008 12:57:07.146
Pacific.
You’ll use this Timestamp later when you calculate the Signature to validate the request. (If you
did not specify that you accept only signed carts, you will not receive the Timestamp in your
merchant request.)
4.1.3 3. The Signature
To create the Signature, we concatenate the UUID and Timestamp, apply a standard signature
algorithm using your Seller Central AWS Secret Access Key, and then URL encode it. (If you did not
specify that you accept only signed carts, you will not receive the Signature in your merchant
request.) See Manage Your Security Keys in Seller Central online help for information on generating
and viewing your Seller Central Secret Access Key.
Here is an example of the signature in the request you receive.
Signature=MRYUB4bk%2B3ehw0BAbzk6mp6SxXw%3D

You’ll use this Signature later when you calculate the Signature using your Seller Central AWS
Secret Access Key to validate the request.
4.1.4 4. The NotificationType
The NotificationType identifies the type of notification. Its values are:


4.1.5

NewOrderNotification
OrderReadyToShipNotification
OrderCancelledNotification

Here is an example of the NotificationType in the request you receive:
NotificationType=NewOrderNotification

4.1.6 5. The NotificationData
The NotificationData is the URL-encoded content of the cart.
Here is an example of the order notification data using URL encoding.
NotificationData=%3c%3fxml+version%3d%221.0%22+encoding%3d%22UTF-8%22%3f%3e%3cNewOrderNotifi
cation+xmlns%3d%22http%3a%2f%2fpayments.amazon.com%2fcheckout%2f2009-05-15%2f%22%3e%3cNotifi
cationReferenceId%3eae51d3a6-7843-4cbb-ad1d-ee8cc591e10d%3c%2fNotificationReferenceId%3e%3cP
rocessedOrder%3e%3cOrderChannel%3eAmazon+Checkout+(Live)%3c%2fOrderChannel%3e%3cAmazonOrderI
D%3e101-1234567-9876543%3c%2fAmazonOrderID%3e%3cOrderDate%3e2009-08-31%3c%2fOrderDate%3e%3cB
uyerInfo%3e%3cBuyerName%3eKelly+Green%3c%2fBuyerName%3e%3cBuyerEmailAddress%3esomeone%40amaz
on.com%3c%2fBuyerEmailAddress%3e%3c%2fBuyerInfo%3e%3cShippingAddress%3e%3cName%3eKelly+Green
%3c%2fName%3e%3cAddressFieldOne%3e123+Oak+Avenue+SE%3c%2fAddressFieldOne%3e%3cAddressFieldTw
o%3eApt.+221-B%3c%2fAddressFieldTwo%3e%3cCity%3eSeattle%3c%2fCity%3e%3cState%3eWA%3c%2fState
%3e%3cPostalCode%3e98104-1234%3c%2fPostalCode%3e%3cCountryCode%3eUSA%3c%2fCountryCode%3e%3c%

The Instant Order Processing Notification API Guide
2fShippingAddress%3e%3cShippingServiceLevel%3eStandard%3c%2fShippingServiceLevel%3e%3cProces
sedOrderItems%3e%3cProcessedOrderItem%3e%3cAmazonOrderItemCode%3e12345%3c%2fAmazonOrderItemC
ode%3e%3cMerchantId%3eAEIOU1234AEIOU%3c%2fMerchantId%3e%3cSKU%3eABC123%3c%2fSKU%3e%3cTitle%3
eRed+Fish%3c%2fTitle%3e%3cDescription%3eA+red+fish+packed+in+spring+water.%3c%2fDescription%
3e%3cClientRequestId%3e12345%3c%2fClientRequestId%3e%3cCartId%3emiq%3a%2f%2frose%3a1.0%2fcar
t%2fcba%3a1.0%2fcart%3a2.0%2fAEIOU1234AEIOU%2fAEIOU1234AEIOU%2f1-1232431180394-57EEF607E6D40
DB5%3c%2fCartId%3e%3cIntegratorId%3eVWXYZ98765VWXYZ%3c%2fIntegratorId%3e%3cIntegratorName%3e
www.IntegratorWorld.com%3c%2fIntegratorName%3e%3cPrice%3e%3cAmount%3e5.0%3c%2fAmount%3e%3cCu
rrencyCode%3eUSD%3c%2fCurrencyCode%3e%3c%2fPrice%3e%3cQuantity%3e1%3c%2fQuantity%3e%3cWeight
%3e%3cAmount%3e1.0%3c%2fAmount%3e%3cUnit%3elb%3c%2fUnit%3e%3c%2fWeight%3e%3cFulfillmentNetwo
rk%3eMERCHANT%3c%2fFulfillmentNetwork%3e%3cItemCharges%3e%3cComponent%3e%3cType%3ePrincipal%
3c%2fType%3e%3cCharge%3e%3cAmount%3e5.0%3c%2fAmount%3e%3cCurrencyCode%3eUSD%3c%2fCurrencyCod
e%3e%3c%2fCharge%3e%3c%2fComponent%3e%3cComponent%3e%3cType%3eShipping%3c%2fType%3e%3cCharge
%3e%3cAmount%3e0.0%3c%2fAmount%3e%3cCurrencyCode%3eUSD%3c%2fCurrencyCode%3e%3c%2fCharge%3e%3
c%2fComponent%3e%3cComponent%3e%3cType%3eTax%3c%2fType%3e%3cCharge%3e%3cAmount%3e0.0%3c%2fAm
ount%3e%3cCurrencyCode%3eUSD%3c%2fCurrencyCode%3e%3c%2fCharge%3e%3c%2fComponent%3e%3cCompone
nt%3e%3cType%3eShippingTax%3c%2fType%3e%3cCharge%3e%3cAmount%3e0.0%3c%2fAmount%3e%3cCurrency
Code%3eUSD%3c%2fCurrencyCode%3e%3c%2fCharge%3e%3c%2fComponent%3e%3cComponent%3e%3cType%3ePri
ncipalPromo%3c%2fType%3e%3cCharge%3e%3cAmount%3e0.0%3c%2fAmount%3e%3cCurrencyCode%3eUSD%3c%2
fCurrencyCode%3e%3c%2fCharge%3e%3c%2fComponent%3e%3cComponent%3e%3cType%3eShippingPromo%3c%2
fType%3e%3cCharge%3e%3cAmount%3e0.0%3c%2fAmount%3e%3cCurrencyCode%3eUSD%3c%2fCurrencyCode%3e
%3c%2fCharge%3e%3c%2fComponent%3e%3c%2fItemCharges%3e%3c%2fProcessedOrderItem%3e%3c%2fProces
sedOrderItems%3e%3c%2fProcessedOrder%3e%3c%2fNewOrderNotification%3e

Here is the same information expressed as readable XML for a NewOrderNotification. Please see
Appendix A – The Instant Order Processing Notification API Schema for OrderReadyToShip and
OrderCancelled notifications.

ae51d3a6-7843-4cbb-ad1d-ee8cc591e10d

Amazon Checkout (Live)
101-1234567-9876543
2009-08-31

Kelly Green
someone@amazon.com

Kelly Green
123 Oak Avenue SE
Apt. 221-B
Seattle
WA
98104-1234
USA

Standard

12345
AEIOU1234AEIOU
ABC123
Red Fish
A red fish packed in spring water.
12345
miq://rose:1.0/cart/cba:1.0/cart:2.0/
AEIOU1234AEIOU/AEIOU1234AEIOU/1-1232431180394-57EEF607E6D40DB5
VWXYZ98765VWXYZ
www.IntegratorWorld.com

5.0
USD

1.0
lb

MERCHANT

Principal

5.0
USD

Shipping

0.0
USD

Tax

0.0
USD

ShippingTax

0.0
USD

PrincipalPromo

0.0
USD

ShippingPromo

0.0
USD

The NotificationData contains the NotificationReferenceId (a unique ID generated for each
Notification request), and ProcessedOrders (order details for the current order for which
notification is sent).
15

The Instant Order Processing Notification API Guide
The ProcessedOrders includes details (for example, SKU, Title, Description, Quantity,
Price, and so on) from the order XML submitted from your website. The ProcessedOrders also
includes the charges calculated at the Item level. The charges are Principal (Item Price
multiplied by Quantity), Shipping (shipping charge attributed to a single Item), Tax (sales tax
calculated on the Principal after the promotion discount is applied), ShippingTax (sales tax
calculated on the shipping charge after the promotion discount is applied), PrincipalPromo, and
ShippingPromo (discounts applied to Principal and Shipping charges).
Notes
We generate a new NotificationReferenceId each time we send a request with a new
order. When we send a request retry for the same order, we use the same
NotificationReferenceId.
Do not ship an order until you receive the Order Ready-to-Ship notification.
4.1.7 6. The AWSAccessKeyId
The AWSAccessKeyId is the other part of your access key pairs (Secret Access Key and Access Key
ID). This access key is returned in the notification. See Manage Your Security Keys in Seller Central
online help for information on generating and viewing your Seller Central Access Key ID.

Processing the Notification Request

You use the information in the notification request (the XML content as well as the other
information in the request) to perform the following actions:
1.
2.
3.
4.

Parse the request data.
Verify that the notification request is valid.
Process the data.
Respond to the request

Your application must parse this request to verify that the notification is genuinely from Amazon
Payments, process the information for the merchant calculation, and prepare a response.
5.1.1
1. Parse the Request Data
Your first step is to parse the request data. Note that the ampersand “&” character separates the
values, and that request is URL-encoded.
5.1.2 2. Verify that the Notification Request Is Valid
After you receive the data and parse it, you should verify that the request is valid by verifying the
Signature and the Timestamp. Verifying the data helps to prevent responding to requests that might
incorrectly claim to be from Amazon Payments.
Notes
You can skip this step if you did not specify in Seller Central that you accept only signed carts.
We recommend you accept only signed carts to prevent spoofed or invalid orders.
5.1.2.1
2a. Verify the Signature
To verify that the request is genuine, you compare the Signature we generate with the Signature
you generate. To calculate the Signature, you decode the URL-encoded UUID and Timestamp from
the original request; concatenate the UUID and Timestamp; then use a standard HMAC SHA1
algorithm and your Seller Central AWS Secret Access Key (your private key). See Manage Your
Security Keys in Seller Central online help for information on generating and viewing your Seller
Central Secret Access Key.
Notes
You cannot use your X.509 key pair—you must use your Seller Central AWS Secret Access
Key.
You might have a separate AWS account with its own public-private key pair. Be sure you use
the Seller Central AWS Secret Access Key to validate and generate signatures for requests
and responses – this is the key you find in Seller Central on the Integration > Access Key
page.
17

The Instant Order Processing Notification API Guide
5.1.2.2 2b. Verify the Timestamp
To avoid replay attacks, compare the Timestamp in the notification you receive with your system
clock. If the difference is more than 15 minutes, do not process the notification.
Notes
We recommend that you synchronize your system clock with a standard clock, such as the
NIST clock (http://www.time.gov/). If you system clock is not synchronized, you might drop
valid requests.
We recommend you record the notifications you receive so that you can compare the UUID
and Timestamp to verify the uniqueness of the notification.
After you verify the Timestamp, you can proceed with processing the XML document.
5.1.3 3. Process the Data
Now that you have the notification data, you can log it, pass it to inventory management, and use it
for your internal order fulfillment systems.
If you receive an OrderReadyToShip notification, you must confirm shipment with Amazon.
5.1.4 4. Respond to the Request
For successful notification reception, Checkout by Amazon expects the HTTP response status code
“200 OK.” Other responses result in retries of the notification request.

Using Custom Data Fields

You can use your own data definitions and data fields in your Order XML feed. For example, if you
want to allow customers to personalize the mugs and cups you sell, you can pass the custom text
field “cust_name” in your Order XML. When we send the notification to you, we will include this
information.

6.1

Prerequisites for Using Custom Data Fields

To use custom data fields in your feeds, your XML-based applications must meet the following
conditions:
1.

You must be using the XMLNS named “http://payments.amazon.com/checkout/2009-05-15/”
or later.
2. You must be using the order.xsd version with a file date of 2009-03-04 or later. (Download
the latest version here.)
3. You must be using the iopn.xsd version with a file date of 2009-03-04 or later. (Download
the latest version here.)

6.2 How We Process the Custom Data Fields
When we receive your order XML, your order notification response, or your callback response which
contains your custom data, we simply store it until we return it to you as part of the Instant Order
Processing Notification.
We do not parse the data or attempt to interpret it. As long as the content is syntactically correct
(tags spelled the same for both opening and closing tags, no tags improperly nested, and so on), we
accept the content as-is, and return it to you in the same way.
Because we do not parse the custom data you send that’s marked with the ItemCustomData or
CartCustomData tags, you do not need to send us an XSD or otherwise define your custom data
fields.

6.3 Modifying Your Order XML to Use Custom Data Fields
To use custom data fields in your order, you add a new section in your order XML tagged with
ItemCustomData or CartCustomData, as shown in the following example:

JKL909
AEIOU1234AEIOU
Calvin and Hobbes Reliquary

29.99
USD

The Instant Order Processing Notification API Guide

8.5
lb

Books

Charles River Sports Academy
Malachite
10090

0525470948

...

Now, depending on how you want to use this data, we can return it to you as part of the Callback
API, or as part of the Instant Order Processing Notification API.

6.4 Using Custom Data Fields with the Instant Order Processing Notification API
To use custom data fields with order notifications, you enter the information (as shown above) in the
ItemCustomData or CartCustomData areas.
When we send you the order notification XML, we include this information in the file, as shown in the
example below:

6e5fdbca-e5c1-4353-9942-87210203378d

Amazon Checkout
102-4788713-2074908
2009-09-11T02:19:01.000Z

KC Brown
someone@amazon.com

KC Brown
22 Twain Ave. South
Northampton
MA
01065
US

Standard

44837685294413
AEIOU1234AEIOU
JKL909
Calvin and Hobbes Reliquary
By Bill Watterson

123457
miq://rose:1.0/cart/cba:1.0/cart:2.0/
AEIOU1234AEIOU/VWXYZ98765VWXYZ/
2-1328561625299-323F62C3E26F95E9

29.99
USD

8.5
lb

Books
MERCHANT

Principal

2.5
USD

...

0525470948

Charles River Sports Academy
Malachite
10090

When you receive this data, you can manipulate it using your own application logic.

6.5 Using a Custom Namespace as Part of the Custom Data Entry
You can provide your own namespace as part of your custom data entry.
Note the added XMLNS in the example below, listed as CustomText
xmlns="http://mydomain.com":

JKL909
AEIOU1234AEIOU
Calvin and Hobbes Reliquary

29.99

The Instant Order Processing Notification API Guide

USD

8.5
lb

Books

Charles River Sports Academy
Malachite
10090

0525470948
Customer John Smith wants delivery only in the evenings

...

Because you added this custom XMLNS, the responses are modified, too.
Here’s an example of the resulting order notification:

6e5fdbca-e5c1-4353-9942-87210203378d

Amazon Checkout
102-4788713-2074908
2009-09-11T02:19:01.000Z

KC Brown
someone@amazon.com

KC Brown
22 Twain Ave. South
Northampton
MA
01065
US

Standard

44837685294413
AEIOU1234AEIOU
JKL909
Calvin and Hobbes Reliquary
By Bill Watterson
123457
miq://rose:1.0/cart/cba:1.0/cart:2.0/
AEIOU1234AEIOU/VWXYZ98765VWXYZ/
2-1328561625299-323F62C3E26F95E9

29.99

USD

8.5
lb

Books
MERCHANT

Principal

2.5
USD

...

0525470948
Customer John Smith wants delivery only in the evenings

Charles River Sports Academy
Malachite
10090

The Instant Order Processing Notification API Guide

Appendix A—the Instant Order Processing Notification API Schema

Here is the schema for Instant Order Processing Notification API. You can also download the
iopn.xsd file.

The Instant Order Processing Notification API Guide

8
8.1

Appendix B—Frequently Asked Questions
What is the Instant Order Processing Notification API?

With the Instant Order Processing Notification API, you can get instant updates when you get a new
new orders; you can reserve your inventory (remove it from availability to be sold) as soon as you get
an Order Ready-to-Ship notification; and you can release your inventory (make it available to be sold)
when you receive an Order Canceled notification.

8.2 What are order notifications?
Order notifications are HTTP requests that inform merchants about new orders or status changes in
existing orders placed using Checkout by Amazon. These notifications can be passed to merchant’s
internal order management system (OMS).

8.3 How does the Instant Order Processing Notification API benefit me?
Instead of going to Seller Central to see order status changes, you can use Instant Order Processing
Notification API to receive instant updates and then automatically process them using your order
management system (OMS). With the Instant Order Processing Notification API, you can be instantly
notified of new orders; you can reserve your inventory (remove it from availability to be sold) as
soon as you get an Order Ready-to-Ship notification; and you can release your inventory (make it
available to be sold) when you receive an Order Canceled notification.

8.4 What are the prequisites for using the Instant Order Processing Notification
API?
Before you can use the Instant Order Processing Notification API, your systems must meet the
following prerequisites.
5. You must be using the order.xsd version 2009-05-15 or later. (Download this version here.)
6. You must be using the iopn.xsd version 2008-11-30 or later. (Download this version here.)
7. You must be running a web service that can receive HTTPS POST requests made to your
endpoint using port 443.
8. Your HTTPS must use valid SSL certificates from a trusted certificate provider. To view a
complete list of acceptable SSL certificate providers, please see “Accepted SSL Certificates”
in the Callback API Guide (PDF).
To learn more about enabling Instant Order Processing Notification API, please see Enabling Order
Notifications, above.

8.5 Where are Instant Order Processing Notification API messages sent?
Instant Order Processing Notification API messages go to the Merchant URL or Integrator URL
endpoint you specified in Seller Central.

The Instant Order Processing Notification API Guide
The Merchant URL is the URL on your website where you (the merchant) want to receive
notifications as the orders are processed. Your web service must read and process notifications at
this URL. If you leave the Merchant URL blank, you (the merchant) will not receive notifications.
If you provide the Integrator URL, the notification will go to that URL.
You must enable at least one URL endpoint, whether it is the Merchant URL or the Integrator URL.
You set the endpoint URLs in Seller Central.

8.6 What messages can I receive and when will I receive them?
You can receive three type of notifications:
NewOrderNotification You receive this notification when a new order is placed from
your site. This notification means that the Amazon Payments internal order processing has
started.
2. OrderReadyToShipNotification You receive this notification when the order is ready to
be shipped according to Checkout by Amazon order pipeline.
3. OrderCancelledNotification You get this notification when the order is canceled
during the order processing, whether by the buyer or the merchant. You also receive this
notification if Amazon Payments cancels the order due to buyer fraud, order expiration,
failed authorization, and so on.
1.

8.7 Why am I not receiving an Instant Order Processing Notification API message?
To enable Instant Order Processing Notification API messages, you must provide the endpoint URL in
Seller Central. Please see Enabling Order Notifications, above.
If you provide the Merchant URL (endpoint), verify that the URL is using https:// for Production
accounts, using port 443. You can use either http:// or https:// for Sandbox accounts.
If you provide the integrator URL (endpoint), please verify that URL is using https:// for Production
accounts, using port 443. You can use either http:// or https:// for Sandbox accounts.

8.8 Why did I receive an Order Canceled Notification or Order Ready-to-Ship
notification before the New Order notification for the same order?
If the endpoint is unavailable when we send the initial New Order notification but is available soon
after when we send an Order Canceled notification or Order Ready-to-Ship notification, then the
notifications are unsynchronized.
If this happens you can follow one of these procedures:
1.

Do not acknowledge the Order Canceled or Order Ready-To-Ship notification until you
receive the New Order notification message. Instead, send an INTERNAL_ERROR (500)
message, as the message is out of sequence. If you do not acknowledge a notification,

© 2009-11 Amazon.com, Inc. or its Affiliates
Amazon Payments keeps retrying the notification request; notifications will synchronize after
you get the New Order notification.
2. Because each notification contains the full cart and order detail, you can update your order
management system (OMS) with the order information sent in the Order Canceled or Order
Ready-To-Ship notification and ignore the New Order notification message you receive later.

8.9 Why did I receive an Order Canceled notification before an Order Ready-toShip notification for the same order?
If endpoint is unavailable when we send the initial Order Ready-to-Ship notification but is available
soon after when we send an Order Canceled notification, then the notifications are unsynchronized.
If it happens, please ignore the OrderReadyToShip Notification as OrderCancelled notification is
the final state for an order.

8.10 What do I do if I get a notification request with a duplicate UUID?
The UUID is unique for each request. If you get a second notification with a duplicate UUID, please
ignore it as the notification might be due to external replay attacks.
Note that the NotificationReferenceID is the same for each retried notification, even though
we create a new UUID.

8.11 What happens if my service or endpoint is unavailable?
If the notification fails because the endpoint URL is unavailable or the merchant discards the request,
Checkout by Amazon follows a 14-days Exponential Back-off Retry Policy.

8.12 What is the 14-day Exponential Back-off Retry Policy?
If the notification fails because the merchant endpoint URL is unavailable or the merchant discards
the request, Checkout by Amazon follows a 14-day Exponential Back-off Retry Policy, where the time
interval between two retries doubles after every retry. For example, we make the first retry after
one minute. We make the second retry after 2 minutes, the third after 4 minutes, and so on. We retry
sending these notification for 14 days. If the request does not get through in 14 days, the request is
dropped.

8.13 What should I do if I cannot process the notification I receive?
If you cannot process the received notification, you must respond with proper error codes, as listed
below:
Name
INTERNAL_ERROR (500)

SERVICE_UNAVAILABLE
(503)

Use
Respond with this code when the
internal service handling the
notification cannot process the
request.
Respond with this code when your
internal service cannot process the

W3C Definition
The server encountered an
unexpected condition which
prevented it from fulfilling the
request.
The server is currently unable to
handle the request due to a
29

The Instant Order Processing Notification API Guide
Name

PERMISSION_DENIED
(403)

Use
request or when you want Amazon
Payments to retry sending the
notification. Retries are sent following
the Exponential Back-off Retry Policy.
Respond with this code when you are
not able to verify the signature

W3C Definition
temporary overloading or
maintenance of the server.

The server understood the
request, but is refusing to fulfill it.

Definitions from Hypertext Transfer Protocol – HTTP/1.1 definitions (RFC2616 Fielding, et al.).

8.14 How do I authenticate order notifications?
After you receive the data and parse it, you should verify that the request is valid by verifying the
Signature and the Timestamp. Please see Verify that the Notification Request Is Valid, above.

8.15 Why did I receive an order notification with items referring to multiple carts?
Amazon consolidates 1-Click orders that are placed within 90-minute window into a single order.
When consolidation occurs, you receive a single notification of the consolidated order. The items in
the consolidated order originate from the multiple 1-Click order submissions. Each item, therefore,
refers to its originating cart.

8.16 Why did I receive an order notification with fewer items than were in the
submitted cart?
If the submitted cart contains items with different shipping method or if merchant-fulfilled items are
combined with Fulfillment by Amazon items, the cart is split into multiple Amazon orders. When this
occurs, you receive a separate notification for each Amazon order. Each notification includes the
different set of items (that is, items grouped based on the common shipping method) from the same
cart.

8.17 I received a New Order Notification. Should I ship the order now?
No, do not ship the order when you receive the New Order notification. This notification lets you
know that the order has been placed, but payment for the order might still be processing. Wait until
you receive the Order Ready-to-Ship notification before you ship the order.

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.6
Linearized                      : Yes
Author                          : Steve Matlock
Create Date                     : 2011:10:21 09:34:43-07:00
Modify Date                     : 2011:10:21 09:34:50-07:00
Subject                         : A reference guide for developers who want to automate order notifications with Amazon Payments.
Has XFA                         : No
Language                        : en-US
Tagged PDF                      : Yes
XMP Toolkit                     : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:08:04
Web Statement                   : www.amazonpayments.com
Marked                          : True
Format                          : application/pdf
Rights                          : Copyright (c) 2009-11 Amazon.com, Inc. or its affiliates
Title                           : The Instant Order Processing Notification API Guide
Description                     : A reference guide for developers who want to automate order notifications with Amazon Payments.
Creator                         : Steve Matlock
Keywords                        : 
Metadata Date                   : 2011:10:21 09:34:50-07:00
Document ID                     : uuid:7dc30801-6a49-46e9-b4b8-53ac2014ef5a
Instance ID                     : uuid:7cb2146c-ff75-442d-aecb-8cfee1d4e2e8
Page Count                      : 34
Signing Date                    : 2011:10:21 09:34:50-07:00
Signing Authority               : ARE Acrobat Product v8.0 P23 0002337
Annotation Usage Rights         : Create, Delete, Modify, Copy, Import, Export

EXIF Metadata provided by EXIF.tools

The Instant Order Processing Notification API Guide

Navigation menu

Versions of this User Manual:

Views

Navigation