Betfair user provisioning

Provisioning a user on a certain product must follow the correct workflow: 1. User registers with the Vendor on their website (using separate credentials from their Betfair username and password) 2. On success, the user is forwarded to a secure Betfair validation service (Vendor Services API) 3. The user enters their access request token*, and then their Betfair username and password. 4. The Vendor username and the Betfair username are then mapped by a ClientId and the relationship is managed by Betfair 5. The Vendor may now interact with the Betfair account via vendor services using only the ClientId - the Betfair username shall not be used ## Deliverables **Betfair user provisioning project brief** ** ** As listed by betfair Provisioning a user on a certain product must follow the correct workflow: 1. User registers with the Vendor on their website (using separate credentials from their Betfair username and password) 2. On success, the user is forwarded to a secure Betfair validation service (Vendor Services API) 3. The user enters their access request token*, and then their Betfair username and password. 4. The Vendor username and the Betfair username are then mapped by a ClientId and the relationship is managed by Betfair 5. The Vendor may now interact with the Betfair account via vendor services using only the ClientId - the Betfair username shall not be used *The createVendorAccessRequest token is used to allow the user to verify that they want to use your software with their Betfair account. They are required to enter their Betfair password to verify the request. Our requirements Following the above information we already have part 1. But we require the rest of the process to be created for us. Details of requirements The system must be compatible with asp and interact with asp without fault this is the biggest requirement if you cannot provide an asp compatible version then please do not attempt to accept this job as you will disappointed when we refuse to pay for something we can't use. It must be flexible as a large betfair software provider we have multiple products across multiple domains so the page design must contain certain degree of flex to allow us to use it on multiple sites for multiple different products without fault. The system must be secure (we leave the method of securing to your own discretion as we understand every programmer has their own preferred methods for ensuring data security during transit) The code must be fully commented so we can edit it later in house if required (more likely than not we will just come back to you for further work but as we must be able to incorporate this in with different sites that work in different ways its important we are able to gain a good understanding of how your system works so we can interact with it correctly) Additional info **WSDL and Endpoint URLs** The API uses SOAP web services. The WSDL for the API is located at [login to view URL] The Web Services Definition Language (WSDL) file holds details of the services and associated XML objects. All services are called over a secure link (i.e. SSL) and therefore must be specified as https: in the end point URL. The endpoint URL for Vendor Services is: [login to view URL] Betfairs vendor services api documentation is available from the following url: [login to view URL]