3 replies to this topic

[J_Fyrebird]

My client is manually processing credit cards - his preference.

Anyway, with the recent upgrade to osC v2.3.1, the credit card payment module (the 'default' module) is now no longer recognizing that an email address has been set for the option "Split Credit Card E-Mail Address". In the file cc.php, lines 164 - 173 are as follows:

function before_process() {
global $HTTP_POST_VARS, $order;

if ( (defined('MODULE_PAYMENT_CC_EMAIL')) && (tep_validate_email(MODULE_PAYMENT_CC_EMAIL)) ) {
$len = strlen($HTTP_POST_VARS['cc_number']);

$this->cc_middle = substr($HTTP_POST_VARS['cc_number'], 4, ($len-8));
$order->info['cc_number'] = substr($HTTP_POST_VARS['cc_number'], 0, 4) . str_repeat('X', (strlen($HTTP_POST_VARS['cc_number']) - 8)) . substr($HTTP_POST_VARS['cc_number'], -4);
}
}

From what I can tell, everything is correct... but it seems to have stopped working. The email entered in the Admin side, is a valid email account.

As i said, previously, this was working correctly.

[DunWeb]

@J_Fyrebird

Unless your client is PCI DSS compliant, he CAN NOT legally process credit cards. If YOU or anyone (another developer) aids him with being able to process credit cards you (and anyone else) can be held legally responsible for the illegal activity. Having said that, I don't think you will find support for your question on this forum.



Chris

[J_Fyrebird]

@DunWeb - Actually he is. There is simply a glitch that is causing an issue with the "Split Credit Card Email" that is being problematic.

[DunWeb]

@J_Fyrebird

Well, there are no differences in the mail handling function between v2.2 and v2.3.1, I would guess it is the database tables that are the issue. If you would like detailed help, please post the site URL (to verify PCI DSS compliance) and I would be happy to help you with the tables and queries.



Chris