 | Documentation Feedback |  |
Every Amazon FPS payment transaction requires a payment token. When someone successfully completes the CBUI web pages, the Co-Branded service creates a payment token. A payment token represents purchase information, including the amount of the purchase, the buyer, and the authorization to use the token as a means of making a purchase. Before you can initiate any Amazon FPS payment transaction, such as a Pay request, you must obtain a token.
There are a number of different kinds of payment tokens and each one has different characteristcs. Each Amazon FPS Quick Start implementation provides a set of token types. This Quick Start covers the following:
Single-use—Authorized to make a single purchase of a specified amount where the money is sent from the buyer to you
Available for: Amazon Flexible Payments Service Basic Quick Start Developer Guide
Recurring-use—Authorized to make payments at regular intervals for such as for subscriptions
This token can have usage limitations, for example, an expiration date. The payment can be made to you or a third party. In this case, you broker the deal and collect a marketplace fee for doing so. This scenario, in which there are three parties involved, buyer, merchant, and you, is called a marketplace scenario, and is intended for use with physical products which are shipped to the customer.
This token can be used in a marketplace scenario.
Available for: Amazon Flexible Payments Service Advanced Quick Start Developer Guide
Multi-use—Authorized to be used one or more times within its specified limitations, for example, the total amount it can be used for, how long it can be used, or how little or how much any single payment can be
This token can be used in a marketplace scenario.
Available: Amazon Flexible Payments Service Advanced Quick Start Developer Guide
Prepaid—Authorized to be used one or more times within its specified limitations. For example, it can be limited for total amount, how many days, months, or years it can be used, and the size of any single payment.
The prepaid token must be funded before it can be used.
Available for: Amazon Flexible Payments Service Aggregated Payments Quick Start Developer Guide
Postpaid—Like the Prepaid token, the Postpaid token is authorized four use within its specified limitations. It too can be limited for total amount, how many days, months, or years it can be used, and the size of any single payment.
This token is like a credit card by which you agree to pay for purchases you make at some time after the actual sale. Unlike the Prepaid token, it is not funded before use.
Available for: Amazon Flexible Payments Service Aggregated Payments Quick Start Developer Guide
Editing—Authorizes the change of an existing token
You can edit the multiuse, recurring, and settlement tokens IDs. This enables you to change information in an existing token, for example, the credit card number. If a credit card expires or is replaced, you can use the edit token to modify the recurring token information without having to require the buyer to cancel and re-purchase the item or service.
Available for: Amazon Flexible Payments Service Advanced Quick Start Developer Guide, Amazon Flexible Payments Service Aggregated Payments Quick Start Developer Guide
Buyers, and, in Amazon FPS Quick Start implementations that support the marketplace scenario, merchants, can go through the CBUI to create tokens. Each one does so for a different purpose. The buyer uses a Buy Now button to go through the CBUI to authorize a purchase with a sender token. The recipient uses a Register Now button to authorize the payment of marketplace fees to you for hosting his or her e-commerce store. (For information on marketplace applications, see Amazon Flexible Payments Service Marketplace Quick Start Developer Guide.)
In both cases, it is your web site that implements the button that redirects the person to the CBUI.
All of the token types can be associated with a sender, that is, a buyer who is authorizing a purchase. So, there can be a sender single use payment token, sender recurring use payment token, sender postpaid payment token, and so on. This guide sometimes shortens these names to sender token. The value returned in TokenId from the CBUI is used as the value for SenderTokenId in subsequent Amazon FPS requests.
The token types that can be used in the marketplace scenario can also be associated with a recipient. In this scenario, you host the e-commerce store of a merchant, called a recipient (the person who receives the money). You charge the recipient a fee (called a marketplace fee) for hosting their e-commerce store and brokering the money transactions. On your web site, you implement a button that makes the recipient go through the CBUI and authorize the payment of marketplace fees for your service. The value returned by the CBUI in the tokenId parameter is used as the value for RecipientTokenId in subsequent Amazon FPS requests. The following token types can be associated with a recipient: recurring-use, multiple-use, and single-use.
The Co-Branded service creates a token in two cases: when a buyer successfully completes the CBUI web pages, thereby authorizing a purchase, and when a merchant authorizes the payment of marketplace fees to you, as shown in the following figure. The CBUI returns to your web site references to the created tokens in the tokenID parameter. This value is either used as a SenderTokenID or RecipientTokenID (depending on the
implementation) in subsequent Amazon FPS requests.
The token type you create depends on the parameters included in your Co-Branded service request. This guide presents the API for each token type available in this Amazon FPS Quick Start. For more information about sending a Co-Branded service request, which can result in token creation, see Getting Authorization.
