Amazon FPS API and Co-Branded Service Requests

Amazon FPS has two production endpoints where you send requests. One is for requests involving the Amazon FPS API. These requests implement all of the financial functionality included in Amazon FPS, such as Pay and Refund. The other endpoint is for Co-Branded service requests that redirect a buyer to a series of Amazon-hosted web pages where the buyer authorizes a payment.

Amazon FPS API and Co-Branded service requests differ in the following ways:

API requests carry out actions using the Amazon FPS web service. Co-branded service requests make the buyer interact with Amazon-hosted interface in which the buyer authorizes payments, such as when he or she authorizes the use of his or her credit card to complete a purchase.
The response to an Amazon FPS request is an XML document. The response to a co-branded service request is a URI sent to a URL specified in the request.
The requests have different endpoints, as follows.
- Amazon FPS API— https://fps.amazonaws.com
- Amazon Co-Branded service API— https://authorize.payments.amazon.com/cobranded-ui/actions/start
  For more information about Co-Branded service requests, see Getting Authorization.

You must make Co-Branded service requests before API requests because the Co-Branded service creates the payment token that you must use in API requests. The Co-Branded service returns pointers to those tokens in the form of token IDs.