Create Stock Photo site like Shutterstock (from scratch). Got Reseller API.

IMP NOTE: We will be sourcing images from the main agency via API. But customers won't need to be redirected. They can purchase from our site itself. We won't be having our own contributors. So submission facility like other stock sites is not needed.

General information for the website: We are a Reseller. Got Reseller API from the agency to sell 60 Million Images.
Kind of development: New website from scratch
Description of every page/module: Like any established stock photo agency (Shutterstock, iStock, Fotolia, etc.)
Description of requirements/features: Like any established stock photo agency (Shutterstock, iStock, Fotolia, etc.)

That's the best reference really. Search system, gallery, credit and subscription system, cart, review page, different sizes for different prices, different payment options, multiple languages, etc.
Payment methods: Credit Card, Paypal, Specific Payment Gateway, Other
Extra services needed: Installation, Customization, 3rd party integration, Optimization, Security, Other
Similar urls: shutterstock.com

Extra notes: Check out Picflux.com. They are a reseller and exactly what we are attempting to do.

Documentation:

Reseller API
The Reseller API enables selling files from our database on your website at your prices. Your customers are not redirected for browsing or payment; your site handles all the transactions just like any other stock photo database. We will be your silent supplier of files at our standard prices, and you set the prices for your customers.

General information:

Once you activate a particular API key, you have to add credits to your account in order for the API to function. When files are purchased through your account, either by you or one of your clients, the payment will automatically be deducted from the balance of your account.

Watermarks
The API interface will display two different images; a small thumbnail preview and a larger version for reviewing the details. The thumbnail version is free of any distinguishing emblems or logos, but the larger version is protected by a watermark. The watermark itself is anonymous and neutral – it will not identify us as your image source to your customers – but it helps protect the copyright of the image without obstructing your client‟s view of the picture.

General principles
All API calls are made through HTTP messages with an appropriate set of GET or POST parameters. A response of API methods is converted into JSON format. This scheme allows using API not only from the site but also with the help of AJAX requests directly from a browser. Combination of API functionality with AJAX technology opens wider horizons for user interface developers.

There are two obligatory parameters for all API methods:

'dp_apikey' – an API key, issued to the user
'dp_command' – a requested API method identifier.
The following obligatory parameter is necessary for the methods which require user session control:

'dp_sessionid' – a unique session identifier, returned by the login method.
The session identifier remains valid during three hours. So to ensure the continuous operation, it is necessary to set up the automatic API user login once in three hours and new session identifier acceptance by all other methods.

All API methods can return two different results: success and failure.A “success” result contains parameters that are specific to a particular API method, but the parameters below are common to all the API methods:

'timestamp' – the current date and time in "YYYY-MM-DD HH:MI:SS" format
'version' – current API version, which is "1.3" for now
'type' – "success" for successfull requests, "failure" if some errors occur
In case of error call outcome will contain following fields in addition:

'errormsg' – an error message
'errorcode' – an error code
'exception' – an error type
Parameter types notes for API methods:

bool : will be considered as TRUE for "1", "true", "on" and "yes". FALSE otherwise.
array : uri array representation (e.g. param_a[]=val1&param_a=val2&param_b[first_key]=val3&param_b[second_key]=val4)
There is 'dp_lang' optional parameter available for most methods, even if it is not described in doc. It means response language for some entities, like item meta data, legal documents, categories etc. Can be any valid value of our site language. [ 'en' | 'de' | 'fr' ... ]