|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
When senders are ready to authorize the purchase of a prepaid balance or sign up for a postpaid
service, they click the equivalent of a Pay Now button, for prepaid, or
Authorize Now for postpaid to authorize the creation of a prepaid
instrument or postpaid credit instrument. To implement the button, you typically use an HTML form
element to redirect the buyer from your website to the Co-Branded User Interface (CBUI). You
cannot issue an Amazon FPS
SettleDebt request until the buyer has successfully completed the CBUI
web pages. Once senders set up a prepaid or postpaid instrument, they can use the instruments to
make purchases without having to return to the CBUI.
The CBUI is a series of web pages that ask the buyer to sign in, specify a personal payment instrument (like a credit card) and authorize either the purchase of a prepaid balance or the set up of a postpaid credit instrument.
The CBUI enables you to include your company's branding on the CBUI web pages. This makes for a better buying experience. By including your branding on Amazon's CBUI web pages, buyers don't feel as if they've completely left your website.
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
SettleDebt. The other endpoint is for Co-Branded service requests
that redirect a buyer to a series of Amazon-hosted Co-Branded web pages where the buyer
authorizes a payment or sets up a prepaid instrument or postpaid credit instrument.
Amazon FPS API and Co-Branded service requests differ:
API requests carry out actions using the Amazon FPS web service. The CBUI uses the Co-Branded service to 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 Co-Branded service request.
The requests have different endpoints, as follows.
Amazon FPS API— https://fps.amazonaws.com
Amazon Co-Branded service— 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.