As a caller offering marketplace services, you must provide a way to register recipients so that they can use your services, which include uploading product information for you to display on your web site and facilitating the sale of this merchandise. You must collect enough information to identify each recipient so they can get paid for products purchased by buyers. You must handle the upload of product information to your web site. Amazon FPS Advanced Quick Start can handle the registration of your recipients and the exchange of money from sender to recipient.
Reserve, which initiate payment
transactions, require parameter values that identify the sender and the recipient. In the API, these
identifiers are called tokenIDs. There is a
SenderTokenId, which identifies the
sender (who sends the money), and a
RecipientTokenId, which identifies the
recipient (who receives the money). Because you, the caller, send
Pay requests on
behalf of the others, you must obtain those identifiers.
These identifiers are generated by the Amazon Co-Branded service at the request of the Co-Branded
User Interface code (CBUI), which is a series of web pages that, among other things, identifies the
recipient or sender. This means that your web site must have an interface that sends a Co-Branded
service request for the sender and a different one for the recipient. The procedures for sending both
requests are the same; the only difference is that they use different Co-Branded service APIs. The API
used for recipient requests returns a
RecipientTokenId, and the API used for
the sender requests returns a
This section describes how to use the Co-Branded service to register the recipient.
The following figure represents the first step in the workflow: recipient registration on your web site. Merchants must register with you for the following reasons:
The recipient must accept your business terms, in particular, the marketplace fee you will charge them.
The recipient must be able to upload and otherwise manage the item information to your web site.
You must have a
RecipientTokenId for each recipient so that you
can pay them using that parameter in a
Implement a recipient account system on your web site.
For example, enable each recipient to sign in to their account with a sign-in name and password.
|2||As the final stage of your registration process, implement a Register button to send a recipient Co-Branded service request. For more information, see Recipient Token API.|
|3||The recipient enters the required information on the Amazon CBUI pages.|
|4||After confirming his or her choices, the recipient is redirected back to your
web site with information, such as the |
The Co-Branded API you use for registering a recipient is the Recipient Token API. For more information, see Recipient Token API.
To register a recipient
On your web site, enable a recipient to register with you.
In this step you collect information about the person or company using your services.
Direct each recipient to https://payments.amazon.com/sdui/sdui/premiumaccount to create a business payment account so they can get paid.
On your web site, display your business policies, including your marketplace fee structure, and obtain the recipient's acknowledgment.
Your marketplace fee might include a flat fee, a percentage of the purchase price, or both. You implement your fee structure using the parameters in the Co-Branded service request.
Implement a button that issues a Co-Branded service request that registers the recipient.
For more information, see Sending a Co-Branded Service Request.
Parse the response.
In particular, store the
tokenID, which is the recipient's. You
use this value in
Reserve requests. You
also need to store the
RefundTokenID to use in case you need to
refund a future transaction.