Miva 10.08 Release Notes

The release of version 10.08 updates the Miva admin’s branching capabilities, making them more user friendly by further isolating a store’s live website from branches that are being worked on behind the scenes.

Using Branches, store owners can add new pages, update old pages or change their entire website without any kind of impact to their production site, and more importantly, no impact to customers using their site.

For additional information on Branching, visit the Version Branching Overview document.

Miva websites can now use CyberSource’s fraud tool, Decision Maker, which allows merchants to set up custom rules for order acceptance, or rejection, based on various data fields. Decision Maker will generate a unique, device fingerprint, for shoppers which will be sent as part of the payment authorization request. Decision Maker uses the created fingerprint to determine if an order is valid or not.

This, coupled with Merchant Defined Fields, which is custom data the merchant sends to CyberSource with each transaction, helps ensure protection from fraudulent activity.

There are some template changes that need to be made in order for this to work. You will need to assign the Cybersource item to OPAY. You will also need to add the following to the head tag to output the JS:

To use Merchant Defined Fields, there are template-level functions to pass any data you want. For example, you would add the following to OPAY. IMPORTANT: The CyberSource item must be assigned to OPAY as noted above.

An update within 10.08 introduces the ability for merchants to configure payment methods to either enable or disable reCAPTCHA validation, depending on the payment method chosen by the shopper.

Specifically, when reCAPTCHA v3 was recently introduced, it caused issues with shopper choosing to use Affirm. Because Affirm is a third party, and because shoppers pay for their purchases through the Affirm website/webapp, it makes reCAPTCHA unnecessary because Affirm has its own fraud prevention tools.

With the release of version 10.08.00, the management of emails for Manage Quotes and Template Based Emails has been moved.

Those emails have been moved to the User Interface section of the Miva admin: User Interface>Emails. They were previously found in the Order Fulfillment section.

The release of 10.08 resolves an issue where Personally Identifiable Information, also known as PII, could be seen, when non-logged in customers looked up orders associated with an email address and zip code. This created a privacy concern.

Now, for non-logged in users looking up orders, all PII will be removed from the information provided.

Release 10.08 includes a Module Priority Configuration, which allows users to configure a priority value for modules, and modifies database queries that load modules to order them based on priority in descending order.

Without a priority configuration method, the Miva admin encountered issues when one module depends on another being executed before it.

• Added support for HTTP Headers at the Store level
• Added ability for Business Accounts to be assigned to Coupons
• PADSS checkup email rescheduled to send every 3 months