RSS Feed
Latest Updates
Match Customer Orders by Miva, Inc.
Posted by Wayne Smith on 20 October 2016 04:12 PM


Use this module to clean up your orders not assigned to any customer account. It will match these orders based on criteria you specify.


Do you have customers that have a customer account on your Miva store but sometimes still place orders not logged in? Or maybe they place orders as a guest without a customer account for years then recently created an account? Both of these scenarios make it difficult for customers to look up order history in a single place as well as reorder past orders.

To solve this issue we developed a Match Customer Orders Module. It allows you to take any order that does not have a customer assigned to it and try an Match it to an existing customer. The module can match an order to a customer based on the following criteria:

  1. Order shipping email address matches a single customers shipping email address
  2. An orders billing email address matches a single customers billing email address
  3. An orders shipping /billing email address matches a single customers forgotten password email address.

You can select one, two or all matching criteria. Keep in mind that it must match at most 1 customer account. If a customer has multiple accounts then the module has no way of knowing which customer account is the “correct” one.

We recommend use the consolidate customers module first to ensure each customer has at most 1 account before running the Match Customer Orders utility

Once run, the module will tell you how many orders it assigned to customer accounts as well as provide you will a log file you can download to see a complete list of every order it assigned to each customer.


*You need to be on Miva 9.0006 or later to use this module.


Get it at CLICK HERE

Read more »

Miva Merchant 9.6 Bug Fix 4 has been released
Posted by Wayne Smith on 05 October 2016 11:56 AM

Miva Merchant 9.6 Bug Fix 4 Release Notes

Bugs Fixed

22795: Patches: The 9.6 Patch did not assign the 'paymentsettings' item to CPCA and CPCE which causes mivapay to fail and trigger a infinite redirect loop

22796: Module: cmp-cssui-mivapay: Item 'paymentsettings' should be assigned to the template in ComponentModule_Page_Assign

22831: Module: authnet: Modify card type prediction to support new MasterCard BIN range

22832: Module: chasepaytech: Modify card type prediction to support new MasterCard BIN range

22833: Module: cybersource: Modify card type prediction to support new MasterCard BIN range

22834: Module: fdggwsapi: Modify card type prediction to support new MasterCard BIN range

22835: Module: paypalpro: Modify card type prediction to support new MasterCard BIN range

22836: Module: qbms: Modify card type prediction to support new MasterCard BIN range

22838: Module: mod10: Modify default card configuration to support new MasterCard BIN range

22889: Payment: JavaScript error at runtime when using MivaPay for a Braintree payment method.

22891: Payment: Mivapay Input field errors should not trigger Invalid payment method

22894: Payment: Clicking reload on the CPCD after adding a card causes the same card and token to be added again.

22895: Payment: Mivapay placeholder text on screen OPAY should include the payment card type.

Read more »

MivaPay is now live on Apps.Miva.Com
Posted by Wayne Smith on 26 September 2016 01:34 PM

MivaPay is now live and being used on Apps.Miva.Com which means if you are a common repeat buyer on our App Store, you can now save a Credit Card on file and speed through checkout!


Click here to read more about MivaPay 

Read more »

Our Newest ReadyTheme Storyteller is now available from our app store
Posted by Wayne Smith on 19 September 2016 01:08 PM

Every great product starts with a great story which is why we are launching our latest Miva ReadyTheme, Storyteller!

Storyteller was designed to showcase and highlight the story behind your products to really help the customer understand why your products are so great. It uses nice visual imagery to help highlight different parts of your products.


Click here to read more about the theme.


Do more than sell products, tell your story! Storyteller is the first in a series of new ReadyThemes that heavily focus on design and usability to provide the best user experience possible. This theme was designed for someone who as a unique product to sell and a story to go along with it. This is also the first ReadyTheme to feature a right sidebar which “flys out” when you click any of the three icons at the top right for the menu, my account or shopping cart.

Features Include:

  • Right Sidebar for Mini-Basket, Navigation and Login
  • Built for speed, images on the page are “lazy loaded” in as you scroll making the site load much faster
  • Optimized Product page layout with additional images which appear on hover
  • Built in Customizable Product tabs for (overview, specification and shipping)
  • Built in support of MivaPay and Subscription Management
  • Optimized Checkout Process
  • Customizable “Story” Page which can be easily edited from ReadyTheme admin
  • All Categories page which uses category title image for graphical layout

Let the storyteller ReadyTheme communicate your story or your product's story to help sell your vision.

Supports the latest versions of Chrome, Firefox, Edge, Safari, and Internet Explorer 11

Get This Theme

Read more »

Miva Blog - How To Convert Your Entire Miva Store to HTTPS
Posted by Wayne Smith on 05 May 2016 10:18 AM

HTTPS has always been a core part of any ecommerce website. If you’re accepting personal information online, including credit cards, you must have an SSL Certificate to encrypt the data. Typically, a website was only served over securely (HTTPS) on Account and Checkout Pages. General shopping and browsing was done over unencrypted HTTP. Over the past couple of years, that is starting to change. Google now prefers the entire site to be served over HTTPS to protect the visitor. They are even giving sites that are all https a small ranking boost. 

While serving every page over HTTPS adds some additional server overhead and can cause the page to load slightly slower, the additional time should be unnoticeable to the visitor.

This tutorial will walk you through step by step how to convert your Miva store to be entirely served over HTTPS. While the actual implementation and changes are relatively simple, making sure everything is done correctly is extremely important. If done improperly there are negative customer experiences which can occur, such as getting insecure warnings on pages and negative SEO consequences which can damage your rankings – both of which you want to avoid.


Click here to read more

Read more »

End of Life Software and Non Compliance Fee Change Updates
Posted by Wayne Smith on 06 May 2015 02:54 PM

As Miva has evolved, we’ve built a unique, hybrid Software-as-a-Service (SaaS) platform that allows our customers to retain the control and independence of distributed software, while having the easy upgrades we’ve all come to expect from SaaS platforms. It’s time we refine and formalize our policies on when software is officially EOL (End of Life), and update our Non-Compliance Fee (NCF) policies accordingly.

Most Software-as-a-Service platforms don’t give you a choice when it comes to upgrades – you simply login one day and your platform has been upgraded for you, whether you like it or not, and whether it negatively impacts your business or not.

Miva has chosen a different path. While providing the type of seamless upgrades and updates people have come to expect from Software-as-a-Service, we don’t force you to upgrade before you’re ready. The downside to this path is that, often times, people will choose to run out-of-date software; and in this day and age, it’s simply not a wise, safe or prudent choice to run out-of-date software. 

We specifically created and use the Non-Compliance Fee program as an economic incentive program to encourage people to update their stores regularly.

For example, in my opinion, it is simply not safe to run any version of Miva Merchant prior to 5.5 Production Release 8 Update 7 (which was released on October 16, 2012, over two and a half years ago), yet we still have many customers who choose to run Miva Merchant 5.5 PR8 Update 6 or older (including people still running 2.x stores, which was released way back in 1999).

Going forward, Miva Merchant software will be considered EOL (End of Life) when either of these 2 circumstances are met:

1. Software has been officially Non-Compliant due to normal software releases, from the perspective of PCI software updates, for more than 12 Months. In other words, 15 months after the release of a new update, software will officially become EOL.


2. Software that is Non-Compliant due to a security release, from the perspective of PCI software updates, for more than 3 months. In other words, if we mark an update as a security-focused update, per the terms of PCI compliance, older software will be considered EOL 4 months after the security update is released.

What impact does Miva marking a product as End of Life have on you, the merchant?

First and foremost, it means we will not, under any circumstances, release a patch, update or upgrade for that version. The most common use cases would be either an API change by a provider (say for example USPS changes its rating API, we will not be releasing an updated USPS module to work on any EOL version of Miva Merchant).

Second, when there are system-level security changes (such as POODLE in 2014), we will not be releasing a patch or engine upgrade to keep EOL software fully operational on modern Operating Systems.

Non-Compliance Fee program changes:

Currently, we have a varied Non-Compliance Fee program that means you pay a different fee depending on if you’re hosted by a third party or directly with us; and, if you’re hosted with us, your fee varies based on the plan you have.

Going forward, we’re standardizing our Non-Compliance Fee program to a flat rate program. Your NCF will be $50 per month, if you’re running Non-Compliant but non-EOL’d software; or, it will be $100 per month, if you’re running Non-Compliant and EOL’d software.



Click here for the original blog post.

Read more »

ReadyTheme Developer Videos
Posted by Wayne Smith on 27 October 2014 09:30 AM

For anyone looking to build ReadyThemes (or you just want to learn more about how the new ReadyThemes works) We just released 5 new developer videos which walk through the Base Developer Framework as well as a overview of the main ReadyTheme features and functionality

We'll be continuing to add new ReadyTheme videos however, if you have any areas you would like to see more video content (or written documentation) on let me know and I can add it to our queue.

Some other helpful links:

ReadyTheme Documentation -

Base ReadyTheme Framework -

Read more »

4 is NOW LIVE!
Posted by Wayne Smith on 04 February 2011 08:51 AM
Miva Script is the server side scripting language of the MivaMerchant shopping cart, but it's uses go much further. It is is especially well suited for web development having built in support for MySQL, MivaSQL and xBase3 databases.

Click here to begin learning more about Miva Script
Read more »

Miva Merchant 4.x PA-DSS Update and End Of Life Announcement
Posted by Wayne Smith on 13 July 2010 07:35 AM
Dear Miva Merchant 4.x Customers,

As many of you already know, July 1, 2010 was the mandatory deadline for all payment applications to become PA-DSS Validated. This requirement impacts all payment gateway providers, swipe terminals, and shopping cart vendors like Miva Merchant.

PA-DSS Validation is different from PCI-DSS Compliance. Both are implemented and governed by the PCI Security Council, but in order to maintain your PCI-DSS Compliance as a merchant, you must be running PA-DSS Validated (and properly configured) software.

Miva Merchant recently completed its PA-DSS Audit and has received its Attestation of Validation (AOV) for Miva Merchant 5.5 Production Release 7. However, Miva Merchant 4.x is not and will not be PA-DSS Validated.

There are a number of reasons why we’ve been unable to validate Miva Merchant 4.x. The bottom line is that due to the complexity of the software code, it would be impossible to maintain compatibility with existing 4.x stores while still achieving validation.

So here is what we are providing for you, our valued Miva Merchant 4.x customers, to enable you to be fully PA-DSS Validated: an absolutely FREE (yes free) upgrade license to Miva Merchant 5.5. This upgrade license previously cost $399. But it is now available free of charge to every Miva Merchant 4.x user with an eligible license. Please contact your Host or Miva Merchant at (858) 490-2570 for information on your upgrade license.

We’ve also developed three new tools (also free) to make it easier to upgrade to 5.5.

1. OpenUI/MMUI Framework Exporter
2. Order History Exporter
3. Catalog Exporter (Products, Categories, etc...)

You can get information and to download the tools here:

In addition, for any Miva Merchant 4.x storeowners whose merchant account providers are not providing a grace period for running PA-DSS Validated software, we’ve cut a deal with PayPal to provide you a reduced rate on PayFlow Link. Utilization of PayFlow Link provides a workaround that, though less than ideal, will fully integrate with Miva Merchant 4.x as it exists today and handle all of your PA-DSS and PCI-DSS requirements. For more info or to sign up

Finally, you need to be aware that Miva Merchant 4.x will formally reach End Of Life on December 31st, 2011.

Until then, we will continue to maintain existing critical shipping and payment updates to ensure your 4.x store operates as it does today. But as stated above, PA-DSS Compliance will only be available through the PayFlow Link workaround. And on January 1st, 2012 all support and updates will cease for those who have not upgraded to Miva Merchant 5.5.

We want you and your store to continue to succeed. That’s why the Miva Merchant team is providing you with this free upgrade to 5.5. We encourage you to begin the upgrade process immediately in order to maintain the best experience for you and your customers – as well as robust compliance and validation with all PCI security issues.

Community Forum post regarding Miva Merchant 4.x PA-DSS Update and End Of Life Announcement

Click Here

Read more »

Credit Card Security Code ( CVV2 ) explained
Posted by Jim McCormick on 21 July 2009 10:11 AM

Credit Card Security Code ( CVV2 ) explained

What is the CVV2?

The CVV2, Credit Card Security Code is the number found on the back of most cards. It's usually a three digit code, and it's purpose is to ensure that the person using the card for a purchase actually has that card IN THEIR HAND.

Why ask for the CVV2?

There are LOTS of ways that criminals can get their hands on lists of stolen credit card numbers. Getting hold of matching CVV2 numbers is much more difficult. Because of that, if your store verifies the CVV2 at checkout then it is much more likely that the purchase is genuine.

How can I accept CVV2?

Miva Merchant has modified many of its CURRENT payment gateways to include the CVV2 feature in the LATEST releases. Some CVV2 supported gateways are:
# AuthorizeNet

# Innovative Gateway
# First Data Global Gateway
# Payflow Link
# Payflow Pro
# CHASE Paymentech Orbital Gateway

# CyberSource


What if you process your orders through a terminal and it NEEDS CVV2

This is another frequently asked questions. The simple answer is... Tough Luck!.

There is a REASON why your terminal wants this CVV2. It's probably because your merchant account provider is giving you a good rate for NON-INTERNET sales. They give you this rate because if you are processing a card through a terminal, and have the card in hand then this is low risk. If on the other hand you are trying to process internet sales, then your merchant account providor wants to charge you Mid or Low qualifying rates.

What do you do? Well one thing you cannot do is find some way to store your customers CVV2 at checkout. This is absolutely forbidden by Visa, Mastercard etc. Think about it... what value is the CVV2 standard if people start storing this number with the credit card!!!

Bottom line, if you use simple credit card validation then your only options are:

# 1. Call customers and ask for the CVV2 when processing the transaction
# 2. Upgrade your payment gateway to one of the options above.

Read more »

Help Desk Software by Kayako fusion
ERROR: This domain name (, does not match the domain name in the license key file,

For assistance with your license, please contact the Kayako support team: