lib/db.mv: Line 150: MvADD: Runtime Error: Error writing to 'store/00000001/basklist.dbf':
This is a credit card module which prompts the customer for the usual information: name on card, card number, and expiration date. However, it also permits up to 4 extra fields to be configured to collect whatever payment data the shop owner desires. This data is then provided to the administrator with the other credit information when processing orders. Each extra field may be designated as required/not required.
There is an option for "mod10" checking of the credit card number, thus making the module suitable as a replacement for both Miva's Simple Validation module and for users in U.K (such as Switch and Delta) and other countries where mod10 is not applicable. The module also supports limiting the payment methods to certain Price Groups or Availability Groups.
This module is a replacement for the Credit Card Payment with Extra Fields/mod10 modules (BROK_XTRACARD / BROK_XTRACARD2_MOD10). It also replaces the versions of those modules that had price group/availability group support.
NOTE: Can this module be used to collect the 3 or 4 digit security codes from customers?
Yes. Should you do so? NO! The security codes on a credit card may not be collected and stored on a server. Doing so contravenes the agreement you have entered into with Visa, Mastercard, American Express, etc. Not only are there are hefty fines associated with this but it is a practice that will further erode confidence in online commerce, damaging your business and threatening the security of your own financial data. The only valid way to collect security codes from customers is to use a realtime gateway, where the code is collected, verified, but not stored. Miva Merchant supports several realtime gateways with the ability to verify CVV codes. Please check with Miva for more information on those gateways.
No reviews added yet. Add Your Review