Where the CBUI Fits in the Workflow

The following figure shows that you redirect buyers to the CBUI web pages when they are ready to purchase the items they selected on your web site. Your web site code constructs a Co-Branded service request that identifies the buyer, and sends it when you redirect the buyer to the CBUI web pages.

The following table describes the CBUI web pages, the authorization process, and the subsequent Amazon FPS request you make after receiving notification of the authorization.

Authorization and Transaction Process

1	A buyer signs into an Amazon Payments account by entering the proper email and password credentials.
2	The buyer chooses a payment instrument, such as a credit card, bank account, or Amazon Payments balance transfer, to make the purchase.
3	After reviewing the transaction details, the buyer clicks the Confirm button to authorize the payment using the specified payment instrument.
4	The Co-Branded service creates a payment token and redirects the buyer to the URL you specify in your Co-Branded service request (in the `returnURL` parameter). Typically, `returnURL` contains the URL of a Thank you page in which you invite senders to keep shopping (perhaps by showing them similar items to what they purchased). The URI contains not only the endpoint that you specified in `returnURL`, but also a reference to the payment token (such as a `tokenId`), and the status of the authorization.
5	Upon receiving the URI from the Co-Branded service, if the status of the authorization is successful, you must send Amazon FPS a `Pay` (or `Reserve`) request to actually transfer money from the buyer to the merchant. This request must include the tokenID returned by the Co-Branded service in the previous step.