This is a REPOST. The coder we chose is in abitration right now because he did not respond to start working on this project. We will award a $10 bonus if the coder we choose does a good job, and creates a nice interface: We first need you to create a [url removed, login to view] file. The script will be fed the following information through a "form post" query string: PlanName - value: Contains the plan name (text) EMailQty - value: Number of e-mails included with plan (Integer) Price - value: Price of plan ([url removed, login to view] integer type) SetupFee - value: Setup Fee ([url removed, login to view] integer type) MonthsFree - value: Months Free (integer) HoursFree - value: Hours Free (integer) SoftwareFree - value: Software included (text) ContractType - value: Contract Type (text) Acceleration - value: On or Off (boolean) The script must do the following: - Check to see if the referring URL is allowed. The list of allowed URL's (there will only be 2 or 3. We will comment out any un-needed ones) will need to be statically coded into the script, and needs to be commented to that we can easily find the list of allowed URL's and modify and/or comment them out. - If the referring URL is not allowed, the user needs to be redirected to another URL which will also be statically coded into the script, and also needs to be commented for easy location. - the [url removed, login to view] script must then ask the user for a user name and password. After doing this, the script must have a checkbox that the user has to check. If not, the user should be returned with an error telling them they must check the box to proceed if they click the submit button. The checkbox will state "I agree to GSOLConnect's Terms Of Service, Refund Policy, and Acceptable Use Policy.". - the signup script must then an API to determine if the user name is in use: (DESCRIPTION CONTINUED IN DELIVERABLE SECTION). . .
(Continued). . . API will be provided. . . - Ask the user how they want to make payment: - If the user chooses "check", the script should accept the customer's full bank details (we will provide the needed information), and save it in a mySQL database where we can access the information from an admin back-end. The account should then be activated, as the information will be authenticated by a live human on our end. - If the customer chooses "PayPal", the script should direct the customer to a PayPal page with a subscription paypal payment setup for the user. The script should use Paypal's IPN to verify that the user made payment so that activation can continue. We can help with this, as we have a script that was developed in-house to connect to PayPal's IPN. If you choose to build this function into this script, instead of using ours, we will award an additional $10 bonus. - If the customer chooses Credit Card, the script should then accept the customer's credit card information, and connect to [url removed, login to view] using our account information to obtain an authorization (we need to be able to change the settings from AUTH_CAPTURE to AUTH_ONLY and vice versa so this can be hardcoded, or a setting built-in to an admin back-end). - If authorization fails, customer should be prompted to use another card, or select a different payment method. If authorization fails because of Address Mismatch, customer needs to be informed that address was incorrect instead. - If authorization successful, the full credit card information and details (we will provide needed information) should be saved to a mySQL database that we can access from an Admin back-end. Then, the following should occur: - Use the API below to Activate the user: form action="[url removed, login to view]" method="post" input type="hidden" name="Key" value="SecureKey" input type="hidden" name="Ref" value="willbeprovided" input type="hidden" name="User" value="NewUserName" input type="hidden" name="Password" value="Password" input type="hidden" name="Domain" value="[url removed, login to view]" input type="hidden" name="Net" value="D" input type="hidden" name="ReturnURL" value="[url removed, login to view]" input type="submit" value="Submit" name="B1" Possible return codes would be: 0|Success! 100|Failed: No WholeSale Record 110|Failed: Security failed! - Bad or missing Internet Protocol! 120|Failed: Wrong Email Domain encountered. 130|Failed: Bad Network Selector 140|Failed: Bad Username length (4-12) 150|Failed: Bad Password length (4-12) 160|Failed: Bad "When" item encountered, must be (Now) or (Cycle). 300|UserName not available, click back and try again. 301|Email Address not available, click back and try again 400|Error debiting balance, wholesaler not found! 401|Sorry, you do not have enough funds in your account to add this user. - The script should not generate error 120 because the domain name is hard coded. It should not generate 130 as the network is also hard coded. It should not generate 140 as the user name/password length will be checked by the previous script. 160 is no longer possible to generate as the variable is no longer in use. 300 is what would be returned to the other script in the event the customer's user name is taken. - The script should state: "We're experiencing technical difficulties activating your account online. Please call [url removed, login to view] to activate your account by phone" in the event that error 400/401 is returned. - After the user's account has been activated (success code issued), the script should then direct the user to 1 of 4 "thankyou" pages. Each "thankyou" page will be created by us, and will correspond to one of our plan packages. The user needs to be directed to the page that corresponds to the plan they signed up for.
Deliverables: 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer 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 buyer on the site per the coder's Seller Legal Agreement). PHP/MySQL