I am wanting to use a Payment System for in store (physical shop) transactions. Where customers can log in at the shop and do the transaction as if they were at home doing it online, the only difference is there would be a new Payment System called 'Cash'. Then customer pays cash, and the shop assistant through Admin, changes the status to Paid.
But do not want this to be visible new Payment System to be visible to web users outside of the physical shop. So a Payment System only available to a specified IP address would work.
Can anyone think of a way to not display a Payment System to any non-specified IP address, or any other tricky way to have a Payment System only show when for in-store orders?
Thanks.
Five5
12 May 2010 9:33 AM
Nothing, nothing at all guys and gals?
Ned
12 May 2010 12:52 PM
Um... well I did think about this for a while but the best I could come up with was, using the multisite feature, to create a separate site, clone the products from site one to site two and then limit the payment option on site two to cash.
You will need a separate URL for the cash site but could do this with a virtual host on your server.
Does this provide a starting point?
Last modified: 12 May 2010 12:54 PM
Five5
13 May 2010 11:52 AM
Thanks for thinking it through Ned.
My first reaction to your suggestion was negative because of the complexity of our site and product range and duplicating it woudl be a PITA. But I am now thinking it through a little more and seeing if there are any advantages to this, in addition to custom payment system. I will think through further.
In the meantime, if anyone else has another suggestion - all ears are open.
Thanks.
benshanks
14 May 2010 10:19 PM
Maybe you can limit via the required's called within order_info.php not looked at it personally but should be possible to delimit via IP address somewhere or prior to the required
Initally would check available variables on offer when order_info.php is called and see if IP is an available var at that stage of checkout