Vbulletin and like API for new Payment Provider

My friend who is CEO of [login to view URL] just went live today after spending millions of dollars over past 3 years and setting up an unbelievable fraud protection and catch system. That said, I want to use his solution for vbulletin memberships. I saw the link: [login to view URL] but I just dont have the time to go through all that and do it. can someone do this and I would even be willing to turn this into a Product XML or plugin if you could make that-but I would want the source code? if so, please let me know cost and time frame to complete. the API info is here: Getting Started Xcoin have created the Xcoin API to facilitate simple integration of our payment platform into your own applications and websites. 1. Securely obtain all of the information required to process a transaction (including data requirements specified by Xcoin’s API documentation). 2. Initiate a secure SSL connection from the merchant’s Web server or application to the Xcoin payment gateway transaction POST location so transaction data can be passed in name/value pairs. 3. Receive and parse the transaction response from the payment gateway and display the result of the transaction to the customer. Xcoin occasionally makes available sample code and modules for common payment platforms, and if these are available for you to use, they can be found in the Xcoin API Integration section of the site. If you choose to use sample code, please be aware it must be modified with the merchant’s specific payment gateway account information to achieve a successful implementation. Data Requirements The standard payment gateway application programming interface (API) consists of required information fields, as well as additional optional fields, which can be submitted to the payment gateway for real-time transaction processing. Transaction Request To use this API request, the merchant’s web site should submit transaction requests using the POST method to the following payment gateway URL: [login to view URL] The following tables list the transaction data fields that can be submitted via the transaction request string. You may pass them either as form variables or directly within the posting URL. Fields are name/value pairs with the syntax of: name_of_field=value of the field& Merchant Parameters Field Name Description xc_login The merchant’s unique API Login ID Required - Upto 20 characters The merchant API Login ID is provided in the API Integration section of the [login to view URL] site and must be stored securely. xc_returnurl The URL to send the transaction response after completion of transaction Required – Upto 255 characters (URL format) See the Transaction Response page for details of parameters returned to this URL Transaction Parameters Field Name Description xc_amount The total amount of the transaction Required - Up to 15 digits with a decimal point (no dollar symbol) Note: This is the total amount and must include tax, shipping, and any other charges. xc_cust_id The merchant-assigned customer ID Required - Up to 20 alpha-numeric characters (no symbols) A unique identifier which represents the customer associated with the transaction. The customer ID should be provided by merchant server on a per-transaction basis. This parameter is passed back to the merchant on completion or failure of the transaction. xc_prod_id The merchant-assigned product ID Optional - Up to 20 alpha-numeric characters (no symbols) A unique identifier which represents the product(s) associated with the transaction. The product ID should be provided by the merchant server on a per-transaction basis. Customer Information Customer information can either be passed to our API interface by the merchant, or completed manually by the merchant’s customer during transaction processing. As a result of this, the fields in this section are optional, and the information passed is used to pre-fill the registration form. The customer can modify the information passed via these parameters during their registration for the Xcoin platform. Field Name Description xc_first_name The first name associated with the customer’s billing address Optional - Up to 50 characters (no symbols) xc_last_name The last name associated with the customer’s billing address Optional - Up to 50 characters (no symbols) xc_email The customer’s valid email address Optional - Up to 255 characters The email address which will receive the customer copy of transaction receipts. This email address is also used to create a new Xcoin account if they have not registered previously, but can be entered or modified manually by the customer on the registration form of the Xcoin site. xc_company The company associated with the customer’s billing address Optional - Up to 50 characters (no symbols) xc_address The customer’s billing address Optional - Up to 60 characters (no symbols) xc_city The city of the customer’s billing address Optional - Up to 40 characters (no symbols) xc_zip The ZIP code of the customer’s billing address Optional - Up to 20 characters (no symbols) Note on State and Country data The State and Country fields are not taken from the Merchant at the present time, as these are automatically filled by [login to view URL] using IP address geo-location technology on registration. The customer can choose to modify those fields themselves during registration if desired. Transaction Response The transaction response from the payment gateway is returned via a GET request to the URL specified by the merchant in the xc_returnurl parameter, as described in the Merchant Parameters section./ The following table lists the fields returned in the response from the payment gateway. Field Name Description Response Code The overall status of the transaction 1 = Approved 2 = Declined 3 = Error 4 = Held for Review Response Reason Text A brief text description of the result, which corresponds with the response reason code You can generally use this text to display a transaction result or error to the customer. Transaction ID The payment gateway assigned identification number for the transaction