MmDELPAY protects your store from stealing sensitive payment data including Credit Card numbers by removing the entire payment record from the Miva Merchant databases.

1. CC Data Removal
2. Compatibility
3. Installation
4. Support
5. FAQ
6. Troubleshooting
7. Change Log

top

Many Miva Merchant standard and 3rd party payment modules allow you to set them into a pre-authorization / post-capture mode. Experienced Merchant owners not having any anti-fraud insurance usually prefer routine scanning of all orders before capturing the funds, to avoid fraudulent orders and the costs associated with them. And in many cases you are not even allowed to capture the funds if you do not ship the goods within 24-48 hours (check your merchant terms), so you are obliged to use the post-capture mode anyway.

To allow comfortable capturing of the pre-authorized orders, Miva Merchant stores the payment data including the CC numbers on the server and sends them to the payment gateway again at the second capture step. Unfortunately there is no simple and secure way to store the data encrypted and therefore the data are very vulnerable and can be easily stolen. Experienced store owners remove the entire orders or the payment data (i.e. in Ultra Batch ) as soon as they process them, usually on a daily basis. Others use the Secure MmPGP Notification Email that sends the data to the store owner in a secure PGP encrypted e-mail and removes the data immediately upon the checkout. Some gateways allow the pre-authorization / post-capture without storing the CC#.

If, for some reasons, none of the above possibilities is acceptable for you, you can still avoid putting the CC data of your customers in risk by deleting them immediately after capturing the transaction by the payment gateway. Most payment gateways will let you complete the order and capture the funds through their web interface, without the necessity of processing the orders in a batch report from Miva Merchant. It means that storing the CC# on the Miva Merchant server is redundant. MmDELPAY was built exactly for this task - it removes the payment data from the server irreversibly after having them authorized by the payment gateway.

Please note that when using the MmDELPAY , the order remains in your Merchant reports, but the entire payment record will be removed so you will not be able to process it through Miva Merchant, but will have to do it from the web interface of your payment gateway. MmDELPAY is not suitable to work together with the Simple CC Validation , because the payment data would be completely lost. Use the MmPGP Secure Notification instead.

top

• Miva Empresa 3.7x, 3.9x
• Miva Merchant 2.xx, 3.xx, 4.xx
• MMUI, OUI, any UI

top

Brief installation instruction follow. If you are unfamiliar with installing Modules check out the Miva documentation at: http://www.miva.com/docs/merchant/

After installing the module through Admin » Modules » Add , go to Admin » Stores » 'your store' » Order Fulfillment Configuration » truXoft CC Data Removal and select the payment method at which you wish that the payment data is removed upon the checkout process.