120 replies to this topic

[dremhmrk2]

Zelf, could you be retained for a fee to assist in integrating this with the OPC Module we're experiencing difficulties with? Or would it be better to contact the developers of OPC? (They already sort of gave up on assisting, as well.)

OR

Is there a source for programmers that have experience with this sort of thing?

[apache510]

Any plans to add the option for Authorization only?

[amystephenson]

we just moved this site from another hosting company and now we are having problems with the VM not working.  I have check both ends and everything is correct ie: passwords, pin numbers and the like.  When I get the error email there are NO errors reported.  The orders aren't even making it to the Virtual Merchant.  

Customer ID #321
jerry@visionitnow.com
Jerry Henline
United States

Error Message(s):
Address Verification Response:
CVV2 Verification Response:

Talked with VM tech support and because they are not getting anything on their end they are not willing to help...

[sublok]

Quick question before I install this contrib:

Do the customer leave to website to input credit card / secure information?

[xtronics]

DCC how to issues:

I got them to turn on DCC,  but the payment fields Cardholder Amount, Cardholder Currency, and Conversion Rate are missing from the order section of the Payment field setup. There is a way to add them - but that involves even more setup options:

[img]http://xtronics.com/uploads/add_payment_field.png[/img]

This leads me to two key questions:

Do we need to create theses Payment Fields in the VM Payment Fields setup?

If so what should the settings be in add_payment_field?  (I'm thinking that these settings mostly control what happens if one is using the VM website to manually enter an order?)


,.,.,.

Also - how do we test DCC? there isn't a special test card number. What will we see if it is working?

Edited by xtronics, 19 January 2010 - 08:09 PM.

[warpt093]

Thank you for the module.

I created a new OScommerce install to test the module, and followed your clear install instructions meticulously.  The sales are not being sent to Elavon.  I've added the referrer and triple checked the three ID#s.  No error messages.  Am I missing something?
Thx

[warpt093]

Now receiving an error message:


Credit Card Error

The card entered is being declined. This most often is due to incorrectly entered information. Please try re-entering your information. For help processing this order call customer service at XXXXXXXXXX and we will quickly process your order.
Name & Expiration Date Entered: name- Expiration Date Entered: #### (MMYY)

[dkinzer]

I'd be interested in hearing from anyone that switched from using the viaKlix contribution (http://addons.oscommerce.com/info/1896) to this contribution.  Firstly, why did you switch and were there any issues?

Edited by dkinzer, 06 February 2010 - 12:54 AM.

[dkinzer]

Thanks for producing this module.  I had been using the viaKlix module and I recently received a letter from Elavon indicating that they will will be discontinuing viaKlix in June.  After calling Elavon to activate a VirtualMerchant account for me, I installed this VirtualMerchant module on a test site to confirm that it works as advertised.  After a couple of minor details were adjusted, it seems to be working properly.

Since this is fresh in my mind, I thought I'd point out a couple of issues and/or suggestions for improvement.

- After you get the files in place and go to the admin control panel to activate the Virtual Merchant module, the title for the module is shown as "Credit Card: (MODULE_PAYMENT_CHARGEIT_CC_ACCEPTED)".  I recognized the all-caps identifier as one that should have been defined so I thought that I had made an error when putting the files in place.  After some searching about, I realized that the reason that MODULE_PAYMENT_CHARGEIT_CC_ACCEPTED was undefined was because the module hadn't yet been installed.  It may be useful to modify the code slightly so that the entry in the module list does not include the undefined identifier prior to the module being installed.

- I saw the list of fields on the first page of this support thread so I went to my VirtualMerchant login and verified that all of the entries were present.  On my first test charge (using the production server) I got an error code back.  Since I had set up the email for transaction errors, I shortly received an email indicating that ssl_salestax was required but not present in the post.  I had overlooked the fact that status for ssl_salestax is 'required' by default but is listed as not required in the field list.  It might be a good idea to include the field list in the installation instructions and to point out that one should confirm that the required/not required status is set as indicated.

- I did not enable DCC so I didn't bother to try to add the fields ssl_cardholder_amount, ssl_cardholder_currency and ssl_conversion_rate.  Consequently, I didn't have the problem that others have had as noted in other posts in this thread.  It is probably worthwhile to add a note to the installation instructions to the effect that those fields aren't needed if DCC isn't enabled.

- I would also be worthwhile noting in the installation instructions that the "Order ID" field must be manually added.  Unless Elavon changes the defaults and the standard fields, the only changes that need to be made are to add the "Order ID" field and to change the status of the "Sales Tax" field from required to not required.

[Dennisra]

dkinzer, on 09 February 2010 - 12:31 AM, said:

Elavon to activate a VirtualMerchant account for me

How much did they charge you to do that?

[dkinzer]

Dennisra, on 09 February 2010 - 12:56 AM, said:

How much did they charge you to do that?

Nothing.  As the letter noted, the $75 fee for conversion to VirtualMerchant is waived until the end of May 2010.

[dkinzer]

A note of caution is in order for anyone converting from the viaKlix contribution to this one.  The viaKlix contribution does not store the cardholder information in the osC orders database but this VirtualMerchant contribution does.  Storing the cardholder information will make it very difficult (perhaps impossible) to get PCI compliance certification.

I haven't looked carefully at the source for the two contributions to discover how the viaKlix contribution is avoiding storing the information.  I suspect, however, that it is not putting the information in POST variables.  It could be that the VirtualMerchant contribution won't work without the cardholder information being placed in POST variables.  I didn't try to fix the problem that way.  Rather, I modified checkout_process.php so that it no longer places the cardholder information in the array used to create the new record in the orders database.

Unfortunately, I can't easily describe how to make such a change because my osC is heavily modified.  That said, you can load up checkout_process.php and look for this code sequence:

						  'cc_type' => $order->info['cc_type'], 
						  'cc_owner' => $order->info['cc_owner'], 
						  'cc_number' => $order->info['cc_number'], 
						  'cc_expires' => $order->info['cc_expires'], 
						  'date_purchased' => 'now()', 
						  'orders_status' => $order->info['order_status'], 
						  'currency' => $order->info['currency'], 
						  'currency_value' => $order->info['currency_value']);
  tep_db_perform(TABLE_ORDERS, $sql_data_array);

Once you find that, change it so that it looks like this:

//						  'cc_type' => $order->info['cc_type'], 
//						  'cc_owner' => $order->info['cc_owner'], 
//						  'cc_number' => $order->info['cc_number'], 
//						  'cc_expires' => $order->info['cc_expires'], 
						  'cc_type' => '', 
						  'cc_owner' => '', 
						  'cc_number' => '', 
						  'cc_expires' => '', 
						  'date_purchased' => 'now()', 
						  'orders_status' => $order->info['order_status'], 
						  'currency' => $order->info['currency'], 
						  'currency_value' => $order->info['currency_value']);
  tep_db_perform(TABLE_ORDERS, $sql_data_array);

As you can see, this "fixes" the problem by storing empty strings instead of the cardholder information.  You could modify the code so that it avoids storing only the cc number.  I chose to remove all cardholder information because I plan to eventually delete those columns from my database.

I would highly recommend that zelf modify this contribution to make the storing of cardholder information optional or just avoid it altogether.

Edited by dkinzer, 10 February 2010 - 09:09 PM.

[xtronics]

dkinzer, on 10 February 2010 - 09:08 PM, said:

Wrote:
The viaKlix contribution does not store the cardholder information in the osC orders database but this VirtualMerchant contribution does.  Storing the cardholder information will make it very difficult (perhaps impossible) to get PCI compliance certification.

Serious issue - BUT I took a look at my actual data base and this is not stored?  Can someone else confirm this?

Could be one of your mods is storing the CC number - I don't think OSC did with out being modified.

[dkinzer]

xtronics, on 13 February 2010 - 10:04 PM, said:

Could be one of your mods is storing the CC number - I don't think OSC did with out being modified.

I think not.  Does your checkout_process.php have the lines that I showed which clearly provide data for the cardholder information columns of the database?  I haven't looked in detail at any of the CC payment modules other than this one and the viaKlix module but I have read that the generic CC payment module does store cardholder information and I thought that I read that the authorize.net module does as well.

In any event, if you have no data in the cardholder information columns of the orders database then you're in good shape.  I was shocked to find the data there in my orders database and took steps to remove it and prevent it from happening in the future.

[xtronics]

dkinzer, on 14 February 2010 - 08:46 PM, said:

In any event, if you have no data in the cardholder information columns of the orders database then you're in good shape.  I was shocked to find the data there in my orders database and took steps to remove it and prevent it from happening in the future.

I have looked at the database dump - the columns exist in my data base - they have no data for any transaction.  I'm pretty sure those columns were added with a contribution.

One saves a lot of headaches by not storing any such information (IMHO PCI exists to push the responsibility back onto the merchant - instead of fixing 1960's technology).

[sacarius]

Hi,

Has anyone gotten this to work with the latest CRE Loaded 6.4.1? I just get knocked back to the payment information page every time I submit the credit card info.

Thanks!

[chriswest]

Everything my mastercards, and amexs work.  Tried three visa and all give errors.  Does anyone have a clue why this could be or where I should look for fix?

I was able to put through a visa on the VM site so this is something with the contribution.  I was installed by two different developers on 4 different sites, all have same issues.

zelf, on 29 July 2009 - 06:28 AM, said:

AMEX, Visa, MC, and Discover work perfectly in this module.  Would be pretty ridiculous to release a credit card module that did not accept Visa.  Something must be wrong with your installation.

[MrE03]

i contacted elavon to ask if theres an option to have any mismatches to automatically decline and have the customer re input the information on the oscommerce site, however they told me that its on the developers end to somehow code it where if any address digit or zip code number is off that it will decline and not process until the correct information is inputted. I was wondering if this is something that can be easily implemented?

thanks

[Certek]

dkinzer, on 09 February 2010 - 12:31 AM, said:

Thanks for producing this module.  I had been using the viaKlix module and I recently received a letter from Elavon indicating that they will will be discontinuing viaKlix in June.  After calling Elavon to activate a VirtualMerchant account for me, I installed this VirtualMerchant module on a test site to confirm that it works as advertised.  After a couple of minor details were adjusted, it seems to be working properly.

Since this is fresh in my mind, I thought I'd point out a couple of issues and/or suggestions for improvement.

- After you get the files in place and go to the admin control panel to activate the Virtual Merchant module, the title for the module is shown as "Credit Card: (MODULE_PAYMENT_CHARGEIT_CC_ACCEPTED)".  I recognized the all-caps identifier as one that should have been defined so I thought that I had made an error when putting the files in place.  After some searching about, I realized that the reason that MODULE_PAYMENT_CHARGEIT_CC_ACCEPTED was undefined was because the module hadn't yet been installed.  It may be useful to modify the code slightly so that the entry in the module list does not include the undefined identifier prior to the module being installed.

- I saw the list of fields on the first page of this support thread so I went to my VirtualMerchant login and verified that all of the entries were present.  On my first test charge (using the production server) I got an error code back.  Since I had set up the email for transaction errors, I shortly received an email indicating that ssl_salestax was required but not present in the post.  I had overlooked the fact that status for ssl_salestax is 'required' by default but is listed as not required in the field list.  It might be a good idea to include the field list in the installation instructions and to point out that one should confirm that the required/not required status is set as indicated.

- I did not enable DCC so I didn't bother to try to add the fields ssl_cardholder_amount, ssl_cardholder_currency and ssl_conversion_rate.  Consequently, I didn't have the problem that others have had as noted in other posts in this thread.  It is probably worthwhile to add a note to the installation instructions to the effect that those fields aren't needed if DCC isn't enabled.

- I would also be worthwhile noting in the installation instructions that the "Order ID" field must be manually added.  Unless Elavon changes the defaults and the standard fields, the only changes that need to be made are to add the "Order ID" field and to change the status of the "Sales Tax" field from required to not required.

DK,
I want to thank you for your posts regarding installing the Virtual Merchant contribution.  I also am currently running with ViaKlix and got the same change notice.  I have a question regarding your install.  Did you uninstall the ViaKlix contribution prior to installing the VM?  You also mention adding the "Order ID" field when making this install.  I know enough to be dangerous and it would go a long way if you could show me the code that did this.  Thanks in advance for your reply.

[dkinzer]

Quote

You also mention adding the "Order ID" field when making this install. I know enough to be dangerous and it would go a long way if you could show me the code that did this.

There is no code involved.  This operation is done at the VirtualMerchant site after you log in as a client.