 | Documentation Feedback |  |
As a caller offering marketplace services, you must provide recipients a way to register with you so that they can use your services. The registration process includes collecting information that identifies recipients so they can get paid for products buyers purchase. Amazon FPS Marketplace does not facilitate the upload of product information to your web site, but does facilitate recipient registration.
The actions Pay and 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 to identify the sender, and a RecipientTokenId to identify the recipient. Because you (the caller) send
Pay requests on behalf of the others, you must have those
identifiers. How do you get them?
These identifiers are generated from the Amazon Co-Branded service that, among other
things, identifies the recipient or sender. Because the Co-Branded service generates both
tokenIDs, 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 Co-Branded
service requests are the same; the only difference is that the different requests use
different actions. The action used for recipient requests returns a RecipientTokenId, and the action used for the sender requests returns a
SenderTokenId.
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 Pay or
Reserve request
Recipient Registration
| 1 |
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 API request. For more information, see Recipient Token API. |
| 3 | The recipient inputs 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 RecipientTokenId that you should store in your
database. |
The Co-Branded service API you use for registering a recipient is the Recipient 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 task you collect information about the person or company using your marketplace services.
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 Pay and Reserve requests. You also need to store the RefundTokenID to use in case you need to refund a future
transaction.
