📍 Bolt Help / Platforms / Miva - Managed Checkout Miva - Managed Checkout Learn how to integrate Bolt for Miva. Page Contents Click to expand. Prerequisites If you are migrating from a different cart platform, see the Re-platforming section. How to Install Step 1: Upload Plugin Download the boltpayments.mvc plugin file. Log into the Miva Admin Console non-Chrome-based browser. Navigate to Menu > Modules. Select the + icon > Add Module > Upload. Select Choose File. Navigate to the boltpayments.mvc file on your hard drive and select it. Select Upload. You are then returned to the Add Module screen. Select +Add. Step 2: Add Bolt Module to Store Before you can configure the Bolt module, you must first assign it to your store. Log in to the Miva Admin Console. Navigate to Menu > Payment. Select the Add/Remove Modules. Locate Available Modules > Bolt (credit card). Select +Install. Repeat for each store that you want to integrate with Bolt. Step 3: Configure Bolt Module API credentials The following values can be found in the Bolt Merchant Dashboard by navigating to Administration > API > API Keys. Scroll to Identifiers and set up at least one Publishable Key. The publishable key is a long string of lower and upper case letters and numbers that consists of three sections. Log in to the Miva Admin Console. Navigate to Menu > Payment > Bolt (credit card). Update your API Keys. Key Description Required? API Key Calls Bolt API from your back-end server Yes Signing Secret Verifies signature by checking the authenticity of webhook requests Yes Publishable Key - Multi-Step Opens the Bolt Payment Popup typically on Shopping cart and product pages No Publishable Key - Payment Only Opens the Bolt Payment Popup typically on checkout pages No Publishable Key - Back-office Used in the back office of Magento for manually-created orders. No Each Publishable Key type requires a separate division is set up for your account. Environments Production Sandbox Staging Additional Settings Log in to the Miva Admin Console. Navigate to Menu > Payment > Bolt (credit card). Update the following settings: Sandbox Mode: Enable/Disables sandbox. Image Code: Choose the code for the image you wish to send to Bolt; default is main. Fullfillment Modules: Choose Bolt’s plugins interaction with any post-checkout fulfillment modules: Template Based Emails: Template-based emails are usually order confirmation emails, but some retailers send blind drop ship emails or other emails when an order is placed Custom Fields: Ties custom order fields created in MIVA back to Bolt Orders Marketplace: Reduces the items purchased from inventory on external marketplaces (ebay, etsy, etc) Notes Custom Field: When enabled, captures Order Notes from the Bolt Checkout. Enable Logging: Allows internal Miva logging for Bolt. All logs are placed in a boltlog.txt file accessible via samplewebsite.com/boltlog.txt Select Update to save. Step 4: Add Webhook Endpoints in Merchant Dashboard Login to the Bolt Production Merchant Dashboard and Sandbox Merchant Dashboard. Navigate to Administration > API. Scroll to Merchant Callbacks. Set the Webhook URL. Set the Shipping and Tax URL. Upgrade Bolt Plugin The process to upgrade the Bolt module on your store is similar to the installation process. Download the boltpayments.mvc plugin file. Log into the Miva Admin Console non-Chrome-based browser. Navigate to Menu > Modules. Locate Search Modules and search for bolt. Hover over the Bolt (credit card) module. Select the upload icon. Select the Files tab > Upload. Select Choose File. Navigate to the boltpayments.mvc file on your hard drive and select it. Enable the Overwrite checkbox. Select Upload. You are returned to the Edit Module screen. Select Update. Check Version You can quickly check the version of your software by logging into the Miva Admin Console > Apps & Themes. Troubleshooting Create a User Interface Item The Bolt module requires a User Interface Item. This should be automatically created for you during installation. In case that fails, you can use the following steps to automatically create the item. Log in to the Miva Admin Console. Navigate to Menu > User Interface > Items. Select the + icon. In the Code box, enter bolt. Select Look Up to find the boltpayment module. Select +Add. Select the Pages tab. Update the item in the Assigned column to On for all customer-facing pages (usually everything but batch reports, emails, and similar). Template Changes The Bolt module also requires some template changes. These should be automatically added to the correct locations when you install the module. However, in case it fails, use the following steps to modify your templates. If the templates were changed automatically, you may also desire to move the button to a different location. If so, find the code shown in step 4, on the BASK page basket template. Remove it from the bottom of that template and place it where you would like the button to appear. Log in to the Miva Admin Console. Navigate to Menu > User Interface. Find and edit the BASK page. Just before the closing </head> tag, enter the following: <mvt:item name="bolt" param="connect" />. Then wherever you would like the Bolt checkout button to appear, enter this code: <mvt:item name="bolt" param="button" /> <mvt:item name="bolt" param="callback" />. If styling changes need to be made to the button replace <mvt:item name="bolt" param="button" /> with <div class="bolt-checkout-button" style=""></div>. Select Update to save. Return to Menu > User Interface. Select Settings. In the Head Tag Content box, insert the following: <mvt:item name="bolt" param="track" /> Select Update to save. boltstatus Custom Field The Bolt module also uses a new custom field to help you view the status on the Order Processing batch screen. This should be automatically created when you install the module. However, in case it fails, use the following steps to create the boltstatus page. Log in to the Miva Admin Console. Navigate to Menu > Utilities. If there is a Custom fields tab, select it and skip to step 3. If no Custom Fields tab, select the Add/Remove modules tab. Find the Custom Fields module and select +Install. Select the new Custom Fields tab. Select the + icon. Update the following Fields: Type: Order field Code: boltstatus Name: Bolt Status Leave other selections at their default value. You may enter additional information if you prefer. Save. Disable Bolt Plugin Bolt can be disabled, but not fully removed from a MIVA environment. Bolt dependencies inject themselves in their MIVA Orders and the only way to remove the dependency is to delete or archive the orders. Disabling Bolt removes Bolt’s injection on future orders. Step 1: Disable Module Settings Find and remove all occurrences of Bolt. Bolt can manifest itself in some of the following forms: <mvt:item name="bolt" param="connect" /> <mvt:item name="bolt" param="button" /> <mvt:item name="bolt" param="callback" /> <div class="bolt-checkout-button" style=""></div> Navigate to Menu > Payment Settings. Select Bolt (credit card). Delete all keys located on this page. Update the following: Enabled: No Enable Logging: No Step 2: Remove Bolt UI Items Navigate to Menu > User Interface. Select Items. Search for Bolt. Hover over the item and select the arrow. Select Pages. Select the eye icon. Select all assigned pages. Select the - button to unassign the item from all selected pages. Navigate to Item > More…. Select Delete. Step 3: Disable the Bolt Module Navigate to Menu > Modules. Search for Bolt. Select the magnifying glass icon. Hover over the Bolt (credit card) > Select the square + arrow icon. Uncheck Active . Select Update. Uninstall Bolt Plugin Navigate to Menu > Payment Settings. Select … > Add/Remove Modules. Scroll to Bolt Checkout. Select Remove and follow the steps indicated. Navigate to Menu > Modules. Select the magnifying glass icon. Hover over the Bolt (credit card) > Select the square + arrow icon. Select … > Delete. Re-platforming When re-platforming, you must keep in mind all of the following: Use the Merchant Dashboard for order refunds. Do not use a platform-specific backoffice flow that’s connected to a deprecated account division. Disable all of your old webhooks for the deprecated account division.