Integrate PayPal Pro and Authorize.net Recurring Billing

I need someone to integrate recurring billing, cancels, refunds, and masspay with my existing ecommerce system. I have already integrated the PayPal API for DoDirectPayment and [login to view URL] for AUTH_CAPTURE. This is a multi-user platform. Credentials, such as x_login, x_tran_key, api username, password, and signature for each user are stored in a MySQL database. Recurring billing is already set up for PayPal Standard (where payments are made through the PayPal interface). Users select a payment processor and product options, including price, payment type (one-time payment or recurring billing settings) in the user interface. For PayPal Pro, a billing agreement and a recurring billing profile must be set with the PayPal API. IPN variables will post to a script on my server and update the status for each member's subscription. For [login to view URL], we will integrate the ARB service with the PHP/XML API for RBCreateSubscriptionRequest, Update, and Cancel. The last four number of the credit card must be stored for [login to view URL] refunds. Users will have the ability to refund transactions and cancel subscriptions for both [login to view URL] and PayPal. I also need to integrate PayPal's MassPay with an API call to pay affiliate commissions and record the payment. You will have access to all the scripts on a development site and a separate database. I developed the software, so I can work with you to achieve these goals. I just don't have time to figure all this stuff out myself. I have all the sample API code for [login to view URL] and PayPal Pro. It's just a matter of getting it to work with my shopping cart system. I am flexible on payment if the work exceeds your initial bid. ## Deliverables 1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's Worker Legal Agreement). 2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment. b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project. ## Platform Unix