7 replies to this topic

[nowfrustrated]

Before you say it, I am aware of the compliance issues with using this type of checkout.  This is for an intranet site that is not accessable by the outside world.  

I used the following:
http://www.oscommerce.com/community/contributions,2954

I followed the instructions, the only modification being that I changed the 'admin' folder to reflect the name of my admin folder.

I get this error from checkout_confirmation.php when I try to checkout:

1146 - Table 'MyDatabaseName.TABLE_CREDIT_CARDS' doesn't exist

select * from TABLE_CREDIT_CARDS

[TEP STOP]


I ran the SQL commands during setup, and I see a credit_cards table in the db.

[burt]

You did not define the TABLE_CREDIT_CARDS in the database_tables.php file(s).

[nowfrustrated]

burt, on 09 May 2011 - 01:35 PM, said:

You did not define the TABLE_CREDIT_CARDS in the database_tables.php file(s).

thanks... i had a typo in there

[HappyPappy]

nowfrustrated, on 09 May 2011 - 01:22 PM, said:

Before you say it, I am aware of the compliance issues with using this type of checkout.  This is for an intranet site that is not accessable by the outside world.  

PCI compliance doesn't get cancelled out because you are running an intranet site. Honestly, you run the risk of heavy fines and your business may lose the right to handle and process credit card data if you get caught.

I know I've said this before about this type of thing - just get a PCI compliant manual payment gateway, like http://e-path.com.au but there are others around.

Cheers

[DunWeb]

Peter,


Again, although useful, that link is information ONLY concerning Australia.




Chris

[HappyPappy]

DunWeb, on 07 August 2011 - 03:54 PM, said:

Peter,
Again, although useful, that link is information ONLY concerning Australia.

Hi again Chris, no, its for anyone anywhere. I found the following, quoted from: http://e-path.com.au/about_e-path.html ....

e-Path Website said:

e-Path also provides our payment gateway service to business owners outside Australia that have merchant account facilities with banks in New Zealand, United Kingdom, Europe, South Africa, United States and Canada. Just like a fax machine or a telephone e-Path knows no borders.

Cheers

[DunWeb]

Peter,

Companies that process credit card information are governed by the laws of their own state / province.  Which means, even though that company, located in Australia does not require the company to present PCI DSS compliance documents to set up an account with them, they are STILL REQUIRED by Federal and State law to be complaint within their own State and Country.



Chris

[HappyPappy]

DunWeb, on 07 August 2011 - 11:48 PM, said:

Peter,
Companies that process credit card information are governed by the laws of their own state / province.  Which means, even though that company, located in Australia does not require the company to present PCI DSS compliance documents to set up an account with them, they are STILL REQUIRED by Federal and State law to be complaint within their own State and Country.
Chris

Chris, you may not have the right take on e-Path. e-Path does not process credit card payments. It is not a credit card processor. Think receving credit card detaila by fax machine or over the phone.

e-Path actually provides the PCI compliant environment to accept cc data online for the business owner to then charge the card details into their merchant account offline - just like they would if receiving data via a fax machine or over the telephone and millions pay by credit card over the phone and to a lesser extent by fax machine every day all over the world.

When using e-Path your oscommerce site doesn't touch credit card data therefore there is no PCI compliance to even worry about for your oscommerce site. You still need to handle cc data in accordance with PCI just as you would when receving cc data over the phone, by fax or via postal mail (physical mail).

And companies/persons that handle credit card data (stores, processes or transmits) must comply with PCI. PCI is not different from one country to the next, it is a global uniform standard. For example, PCI DSS (Payment Card Industry Data Security Standard) firmly stipulates the CVV must never be stored in any shape or form under any circumstances - this is a global regulation.
Cheers

Edited by HappyPappy, 08 August 2011 - 12:28 AM.