Get a Freelance Job

Guys, i need this to be rectify asap, this is the error
message that appear when i tested my two website just now it have to be done within one hour and u are not allowed to change/touch/transfer/export out any of my files inside my data base. I will be online the whole night.will escrow payment to the winning bidder asap.

1.www.gambirgreatsex.com

PayPal does not allow your country of residence to deliver to the country you wish to

Unable to process payment. Please contact the merchant as the shipping address provided by the merchant is invalid, and the merchant has requested that your order must be shipped to that address.

2.www’skiyn.com

PayPal does not allow your country of residence to deliver to the country you wish to

I am looking for someone experienced with php or CS Cart to be able to redirect to CardSave’s payment page at checkout. Instructions are given below, and it should be very simple to complete. My website is www.capitalcaterers.co.uk, and it uses CS Cart for my shopping cart, so you should be able to work with this.

Instructions :

The payment page that the link points to doesn’t need to actuall “get on
to” any website. The way that it works is that the merchant’s webshop
“jumps” across to the payment page, which takes the payment and then
“jumps” back to the merchant’s webshop. The payment form is clever
enough to skin itself to whatever skin the merchant has given us, as
soon as it knows who the merchant is (determined by the data that is
present as part of the “jump” from the merchant’s webshop)

If you have a look at this page:

http://www.iridiumcorp.co.uk/Pages/Showcase/HostedPaymentForm.aspx

You can see the “jump” in action – and also the flexibility of the
merchant skin (you’ll see that eventhough both “skin” selections end up
on the same page, they are markedly different in appearance)

Here is the hosted payment page link
All you’d need to do is point them in the direction of the hosted forms
URL (it’s completely self documenting – and there is even a “helper”
page that will be useful for the developer when dealing with the fiddly
hashes that need to be created)

https://mms.cardsaveonlinepayments.com/Pages/PublicPages/PaymentForm.asp
x

We can look at changing the wording of the emails to include this URL as
well as the information about the direct connection.

All instructions are here, and it should be very quick to achieve. The skin will need to match something similar to mine.

Michael

Request for online payment script.

The following is the specification of the requested online payment script.

Client:

Registeration/Signup:
The client side will reqiure a secured registeration/signup. Clients must signin/Login with username and password on secured page. Client must use on-screen keybord for passwords during registration/signup. Client will have to create 2 passwords at the time of registration. Information required from client during registeration will include the following:

First Name
Last Name
Date of birth {dd/mm/yyyy}
email address
phone number
website* optional*
Contact Address{city, state, country}
Login password
withdrawal password

The above will be required during registeration. Numeric Username will be generated for each registered client and a copy delivered to the client email address.

Login/Signin:
Clients will use the login password and email address or numeric username to sign in. Once logged the page will automatically signout within 10mins of idleness. The login password must be typed with onscreen keybord using the cusor or pointer only. Client can perform the following option from their account:

1. Deposit
2. Withdraw
3. Send (P2P)
4. Edit
5. Summary
6. Balance
7. Merchants

1.At the deposit page, clients will be able to make deposits in 4 ways which includes: Deposit Pin, Send (p2p), Bank wire and Credit Card.

2.Moving to the Withdrawal page, Client will be able to withdraw in 4 ways which includes: Pin Generation & Print, send (p2p), Bank wire and credit card. The On-screen keybord will be used to enter the withdrawal password. There is need that each client can generate pin and print. For a client that needs to withdraw via generate and print, will enter following:

Denomination to generate
Quantity to generate

Once the above information is provided, the system will provide a 12 number pin.
example:
someone with $100 can generate: denomination $20 , quantity 5. Total $100, bal $0
or can make denomination $10 , quantity 7, Total $70 , balance $30.

Note that the generated Pin will be used for deposit by any other client account including the client who generated the pin.

3.The Send(p2p) page will help client to quickly send e-units to other accounts.

4. At the Edit page, Clients can edit Bank wire and Credit card information.

5. The summary page gives the client information about clients account statistics and activities, so every transaction details must be viewed from the summary page.

6. Clients must always view live balance at the balance section.

7. Merchant page will contain a shopping cart and api, so as to help merchant intergrate their website easily. The merchant section will also contain websites that accept the e-units. So all website that accept the e-units must be listed on the merchant sections as soon as the shopping cart and or API is integrated.

Note that shoppers with generated pin can pay merchants easily without Registeration/signup and login/signin. At checkout shoppers only need to enter pin to check out. If there should be balance, the system must automatically generate pin that is equivalent to the balance so the shopper can print. so that way shoppers can carry their balance in their pocket.

Each client must have tools to Combine, Convert, Split and send e-units, just like you would with normal cash.

Logout/Signout:
Client will have a secured logout/signout page.

ADMINISTRATION:
The admin must be able to perform the necessary functions:

Set service charge for each transaction,
block any account
delete any account
complete withdrawal for clients
view account summary
Edit
investment
lists merchants that accept e-unit at the merchant section

I have an OSCommerce site and I am trying to use an Authorize.net SIM module to interface with authorize.net to process credit card transactions. Everything goes fine to the point where i enter the credit card information and then click sibmit. Immediately I get bak an error message :

An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

This transaction has been approved.

It is advisable for you to contact the merchant to verify that you will receive the product or service.

In talking with Authorize.net the point me to the generic error 52 which when reading the reasons I have no idea why the error is occurring. I need someone to walk me the through a solution to this issue.

I am using the OSCommerce Authorize.net SIM module “Authorize.net SIM MS2.2″ from Aug 2007

Thanks

I need a php script to parse data from results of search requests similar to this:

http://www.popshops.com/v1/0yp0rj3hqei08nztbslkxco1m/products.xml?catalog_key=8dma5bktzb9bseed24byo2z3w&keywords=ipod+16gb

The results will then be displayed on our online shopping mall website (www.ShoppingMinistry.com). It should display a list of available products and allow customer to sort by name, price etc. It should also allow them to narrow the search by available parameters.

Here are more info about available parameters etc:

Request URL

http://www.popshops.com/v1/0yp0rj3hqei08nztbslkxco1m/products.xml
Required request parameters
Field Value Description
catalog_key string Unique key identifying catalog of merchants: 8dma5bktzb9bseed24byo2z3w
keywords string

A list of keywords to search across your catalog merchants.

keywords=ipod Is a basic search for products containing the keyword ‘ipod’

keywords=ipod -case is a search for products containing the keyword ‘ipod’ and NOT containing the keyword ‘case’
Optional request parameters
Field Value Description
merchant_id integer A unique PopShops merchant_id, limiting products to a single merchant
merchant_type_id integer A unique merchant_type_id limiting products to a single merchant_type.
category_id integer A PopShops category ID, limiting products to a single merchant’s category. Category ids are currently only returned in product query responses.
brand_id integer A PopShops brand_id, limiting products to a single brand
price_min decimal
10.00,19.95, etc
Price minimum product prices should not go below
price_max decimal
10.00,19.95, etc.
Price maximum product prices should not exceed
product_sort name_asc
name_desc
price_asc
price_desc Featured (default), Name (A-Z), Name (Z-A), Lowest Price, Highest Price
product_limit 1-100 Number of products to display at a time. 100 maximum.
product_offset integer Number to offset the product results by
include_deals boolean
1 or 0
Available deals can also be included in the result set that match returned products and merchants.
url_subid string Custom subid/sid to be appended in any final affiliate product urls.
Response fields
Field Description
search_results Contains all of the query responses. Attributes:

* keywords: any keywords passed in
* product_limit: any product_limit passed in
* product_offset: any product_offset passed in
* merchant_id: any merchant_id passed in
* category_id: any category_id passed in
* brand_id: any brand_id passed in
* product_sort: any product_sort passed in
* price_min: any price_min passed in
* price_max: any price_max passed in
* merchant_type_id: any merchant_type_id passed in

products Contains products matching the query parameters. Attributes:

* total_count: Total number of products matching the query parameters

product Contains an individual product. Attributes:

* name: The name of the product
* description: The description of the product
* merchant_id: The merchant_id for the merchant the product belongs to.
* large_image_url: A url for the largest sized image available for the product.
* medium_image_url: A url for a medium sized image of the product.
* small_image_url: A url for a small sized image of the product.
* merchant_price: The price offered through the merchant. Usually corresponds to the lowest price.
* retail_price: The listed retail price of the product.

price_ranges Contains price_ranges for products matching the query parameters.
price_range Contains an individual price_range. Attributes:

* max: The max dollar value in the range
* min: The min dollar value in the range
* product_count: The number of products within this price range.

merchants Contains top merchants for products matching the query parameters. In many cases the number of merchants matching the query is too many to bring back, so this will only bring back the top 50 merchant matches by product count. You may encounter results where you get a product on a page and there is no matching merchant in the merchants node.
merchant Contains an individual merchant. Attributes:

* id: A unique id for the merchant. You can pass this in as a merchant_id to filter products to this specific merchant.
* name: The name of the merchant.
* product_count: The number of products matching the query for this specific merchant.
* logo_url: If available a logo_url will be provided which is a url to small thumbnail of a logo for the merchant.
* url: If available the url will be returned, which is a landing page for this merchant.
* merchant_type_id: If the merchant belongs to a merchant_type, this will be the id for the merchant_type. This can be used to further filter products as a merchant_type_id parameter.

merchant_types Contains top merchant_types for products matching the query parameters.
merchant_type Contains an individual merchant_type. Attributes:

* id: A unique id for the merchant_type. You can pass this in as a merchant_type_id to filter products to this specific merchant_type.
* name: The name of the merchant_type.
* product_count: The number of products matching the query for this specific merchant_type.

brands Contains top brands for products matching the query parameters.
brand Contains an individual brand. Attributes:

* id: A unique id for the brand. You can pass this in as a brand_id to filter products to this specific merchant_type.
* name: The name of the brand.
* product_count: The number of products matching the query for this specific brand.

suggested_merchants If the keywords match any merchant names, or have been tagged by PopShops as belonging to a specific merchant, this node will return any merchants that may be possible matches. This node will have child merchant nodes with attributes available on normal merchant nodes.
deals Contains deals available for products,merchants, and suggested merchants matching the query. Attributes:

* restrictions: Global restrictions that apply to any deal returned.

deal Contains an individual deal. Attributes:

* name: The name of the deal.
* description: A description of the deal.
* url: The redirect url for the deal.
* image_url: If an image is available for the deal, this will be a url for that image.
* specific: This is a boolean (true/false) indicating whether the deal is specific to a product, or applies to all products from the merchant.
* start_on: The start date the deal is valid.
* end_on: The end date the deal is no longer valid.
* code: Any associated code for the deal. This is a code that would need to be used to redeem the deal.
* deal_type_ids: The deal_type id indicating what kind of deal this is.
* restrictions: Any applicable restrictions unique to this deal or merchant.
* merchant_id: A unique id for the merchant.
* merchant_type_id: The id of the merchant_type the merchant of this deal belongs to.

Project Overview

The aim of Project X is to allow users to make donations to a charitable cause whilst making their everyday online purchases.

Charities will pitch a project to the Project X team who will choose a unique project that has a financial target which becomes a tangible benefit. When a project from a chosen charity is selected all funds raised until the target is reached will go towards that project. This project will be featured on the site and users will be aware of what project their contributions will go towards.

When a user signs up to Project X, they will have a profile and become part of a community. They will be able to shop through either a merchant directory (searchable, a-z and categorized) or the special offers blog and know what percentage of their sale will be donated towards the set charitable cause. Users will have to log in to the Project X website in order to ensure their donations are recorded in their profile.

After a purchase is made with a merchant the user will be able to see in their account the amount they have donated and what cause it has gone towards.

Technical Overview

The community side of the project will be powered by a Dating Script, this has already been purchased and installed on the test domain www.jemza.com.

This script allows users to sign up, create a profile with images, music, videos, etc and provides the stable base community functionality such as instant messaging, forum integration and other social networking features.

Their will be some modifications required to the dating script to remove the dating aspect of the software during sign up and in the profiles, however this should be relatively simple and far easier than creating the base software from scratch.

—

Donations from each purchase will be eligible by signing up to each merchants affiliate scheme; each merchant will offer a different commission for sending sales their way.

A model similar to a cashback site is going to have to be integrated into the base platform. When a user signs up they will be assigned a user number by the base software. This user number will have to by dynamically inserted into the clickref tag of any external affiliate link the user clicks taking them to a merchant. This will allow us to link sales and commissions with each user.

A spreadsheet (see projectx-example-spreadsheet.xls) will be generated by the affiliate networks each day which will detail all sales made through the system along with the clickref. We will need a system that allows us to upload this spreadsheet and match the sales made against the user.

The details for each sale will then be logged in the users profile, along with the commission earned, the charitable cause it will go towards and standard info such as date, time, merchant, etc.

There will generally be four levels of status for a purchase made:

Pending: The purchase has gone through, yet merchant is still to confirm.
Confirmed: The purchase has been confirmed by the merchant.
Paid: The money has been attributed towards the charitable project.
Declined: For whatever reason the merchant has declined commission on the sale, maybe the item was returned, etc.

These status’s will need to be incorporated into the transaction part of the users profile. Also the system needs to allow for updating of a status through the uploaded spreadsheet. i.e:

A transaction has been uploaded as pending, yet a new spreadsheet is uploaded with the transaction now at confirmed, this will update the system.

We will also need to work with multiple affiliate networks who may have different setups, so the ability to add a new setup for each affiliate network is going to be a must.

The donations system will be the most complicated part of this project and we’ll have to work through problems and decisions as and how they arise.

—

The Merchant Directory may need to be custom coded as I’m not able to find any available software at present simple enough to integrate. Essentially merchants will need to be categorized, part of an A-Z directory and searchable.

All links through to the merchant website will need to be the affiliate link with the clickref corresponding to the user number so we can associate the sale with them as previously described.

The merchant directory will appear in the members area only and only available when a user is logged in.

—

The Special Offers Blog will run via wordpress and will function in typical blog format. The blog will be available to both the guests and logged in users, however is a user isn’t signed in, we should inform them that they could be donating money to charity if they were signed up so please log in, etc.

Don’t give me silly bids – I’ll pay a fair fee for quality work – paid upon completion only.

Please see attached doc and this:

In order for the ShareASale.com system to work, you will need to place a small piece of HTML code on the page where you want to reward your affiliates. Please read the this entire page before copying your specific code which is given at the bottom of this page.

These instructions may be difficult to understand for someone who has not worked with HTML or affiliate programs in the past – PLEASE do not hesitate to call us and we will be happy to explain and help you with the implementation of this code. For an experienced developer, this implementation should take no more than a few minutes.

Click here to download these instructions as a .pdf for distribution to your tech staff

Your Merchant ID: 8295
In order to complete this step of the setup, your technical staff will place the necessary Shareasale.com tracking code, and complete a test of the system.

The code given to you at the bottom of this page, should be placed in the HTML body of your

I am having an issue accepting PayPal in my Magento store. When a customer tries to check out using the PayPal website standard check out they receive an error message listed below.

Unable to process payment. Please contact the merchant as the shipping address provided by the merchant is invalid, and the merchant has requested that your order must be shipped to that address.

For the customers that are actually able to place an order using the PayPal website standard check out when their order comes through in the admin section it shows the status of PayPal pending.

What I would like done on this project is to correct the error message customers are receiving when using PayPal along with automatically updating orders to processing instead of PayPal pending when a payment has been successfully made for that order.

If you have any questions about this project please feel free to ask. I would like this to be corrected as soon as possible. Thank you