Amazon Flexible Payments Service
Marketplace Quick Start (API Version 2010-08-28)
« PreviousNext »
View the PDF for this guide.Go to the AWS Discussion Forum for this product.Did this page help you?  Yes | No |  Tell us about it...

Amazon FPS Marketplace Quick Start Integration

This section describes where Amazon FPS Marketplace Quick Start fits in to your website's work flow.

Integration Points

You use Amazon FPS Marketplace to handle the following functionality in an order transaction:

  • Registering recipients

  • Authorizing payments

  • Authorizing reserves

  • Completing payments

  • Tracking status

  • Canceling payments

  • Refunding payments

Buyer's Experience

The following sequence shows the events a buyer (sender) goes through in a transaction at the fictitious DigitalDownload website.

Buyer's Experience of Marketplace Quick Start

1

John visits the DigitalDownload website, selects the MP3 audio file, Now and Forever-Richard Marx, selects Amazon Payments as the payment method and clicks Buy Now.

2

After John clicks Download Now, he is directed to the CBUI. He signs into his Amazon Payments account using his email ID and password.

3

Once he signs in, John views the Payment authorization page. This page enables him to select a personal payment instrument, such as his credit card, for the transaction.

John selects his Amazon Payments account balance (ABT) as the payment instrument, as shown, and clicks Continue.

4

After he clicks Continue, John views the Confirm payment authorization page. He reviews the payment details and clicks Confirm.

5

After John clicks Confirm, the CBUI redirects him to the DigitalDownload website, where DigitalDownload executes the payment transaction. That is, DigitalDownload sends a Pay or Reserve request to Amazon FPS, using the token and the IDs retrieved from the Co-Branded service responses. The returnURL parameter specifies the web page where John is redirected by the Co-Branded service request. Typically, this is a Thank You page with an offer to keep shopping. The sender token and a status value are returned to DigitalDownload when John is redirected to the returnURL.

Important

The payment transaction is not executed on the Amazon FPS website. DigitalDownload makes an operation web service call and executes the payment transaction. For more information, see Pay.


Recipient Experience

The following diagram depicts the marketplace workflow for the recipient.

Merchant's Experience of Marketplace Quick Start

1

The merchant lists items for sale on the developer's web site.

2

The buyer shops on the developer's website and uses the developer's ordering tools to authorize payment.

3

Amazon FPS notifies the merchant that a purchase has been authorized, and the merchant fulfills the order.

4

The merchant notifies Amazon FPS when the order is fulfilled. The payment is split between the merchant, the developer, and Amazon FPS.


Caller Experience

Payment Authorization

Another integration point is where the sender chooses Amazon FPS as the payment instrument and authorizes the purchase (as shown in the following diagram):

Process for Payment Authorization

1You website takes the sender through the checkout process, including enabling the sender to enter the shipping address, shipping speed, and payment method.
2If the sender chooses Amazon Payments, your Pay Now button sends the sender to Amazon's Co-Branded User Interface (CBUI).
3The sender selects a personal payment instrument and confirms the purchase.
4The Co-Branded service sends you a URI, specified in the returnURL in the request, which gives you the status of the payment authorization and the identification of the sender.
5You send Amazon FPS either a Pay or Reserve request to initiate the money exchange.

Settle Payment

If you made a Reserve payment (instead of a Pay payment), you must send Amazon FPS a Settle request once the recipient fulfills the order, as shown in the following diagram. For more information, see Completing the Transaction. Only then does Amazon FPS charge the sender's payment instrument and send you the money.

Settling Payment Interaction

1The caller hosts a fulfillment application on the caller's servers and when an order is fulfilled, the caller sends a Settle request to Amazon FPS.
2Amazon FPS processes the request and returns an XML notification of the success or failure of the request.

Cancel Payment

Buyers can cancel a transaction either by using your website or by using the sender's account page on Amazon FPS (payments.amazon.com), as shown in the following diagram. For more information, see Canceling a Transaction.

Canceling Interaction

1The sender clicks the Cancel button hosted on your website or the Cancel button on the Amazon Payments Refund user interface. A cancellation must be carried out before the product is shipped.
2Your Cancel button sends a Cancel request, which uses the TransactionId returned in the Pay or Reserve response.
3Amazon FPS processes the request and returns an XML notification of the success or failure of the request.

Refund Payment

Buyers can request a refund for returned goods through your website or through the sender's account page on Amazon Payments (payments.amazon.com), as shown in the following diagram. Before you can refund a reserved transaction, you must first settle it using a Settle request. For more information, see Refunding a Transaction.

Refunding Interaction

1The sender clicks the Refund button hosted on your website or the Refund button on Amazon Payments Refund.
2Your Refund button sends a Settle request and a Refund request, which uses the RefundTokenId returned in the Reserve response.
3Amazon FPS processes the request and returns an XML notification of the request's success or failure.