PayPal main module

Merchant version 4.13 and older

• New Installation of our Payment via PayPal module
  • Go to admin:modules:add module and click the link
  • Use the Merchant admin upload feature to upload the paypal.mv module
  • Once uploaded, click the Add button to add it to the mall/domain
  • Select admin:stores:payment configuration and assign the module
  • Click the tab at the top and update the settings
• Update of prior version of our Payment via PayPal module
  • Go to admin:modules
  • Scroll down to Payment via PayPal and click the link
  • Use the Merchant admin upload feature to upload the paypal.mv module
  • Select Overwrite and update the older version
  • Select admin:stores:payment configuration
  • Click the tab at the top and update the settings

Merchant version 4.14 and newer

• New Installation of our Payment via PayPal-R module
  • Go to admin:modules:add module and click the link
  • Use the Merchant admin upload feature to upload the paypalr.mvc module
  • Once uploaded, click the Add button to add it to the mall/domain
  • Select admin:stores:payment configuration and assign the module
  • Click the tab at the top and update the settings
• Replace prior version of our Payment via PayPal (compiled) with Payment via PayPal-R (compiled) module
  • Go to admin:modules:add module and click the link
  • Use the Merchant admin upload feature to upload the paypalr.mvc module
  • Once uploaded, click the Add button to add it to the mall/domain
  • Select admin:stores:payment configuration and assign the module
  • Click the tab at the top and update the settings
  • If the message appears to convert references in the orders database, check the box and update. Once updated you can remove the old version of Payment via PayPal.
  • If there is no message it means the prior PayPal module is either not ours or has been inactivate so that the data cannot be retrieved
• Replace prior version of our Payment via PayPal (uncompiled) with Payment via PayPal-R (compiled) module - Note: This must be done before you run the upgrade.mvc to upgrade an uncompiled store to a compiled store. If it is not done beforehand, you need to go back up to the "New Installation of our Payment via PayPal-R module" section.
  • Rename the file u2cstop.mvc to paypal.mvc
  • FTP it to the modules/payment/paypal.mvc location in the path that matches your new merchant version, eg. Merchant2/4.23/modules/payment/paypal.mvc Overwrite the paypal.mvc that is supplied by Miva Corp
  • Run the upgrade.mvc to upgrade your store
  • After a successful upgrade, go to admin:modules:add module and click the link
  • Use the Merchant admin upload feature to upload the paypalr.mvc module
  • Once uploaded, click the Add button to add it to the mall/domain
  • Select admin:stores:payment configuration and assign the module
  • Click the tab at the top and update the settings
  • If the message appears to convert references in the orders database, check the box and update. Once updated you can remove the old version of Payment via PayPal.
• Update of prior version of our Payment via PayPal-R module. Note: This is a new module as of April 27, 2004. If you did not obtain our PayPal module after that date, you are not updating the Payment via PayPal-R module. Rather, you are replacing an earlier Payment via PayPal with the Payment via PayPal-R.
  • Go to admin:modules
  • Scroll down to Payment via PayPal-R and click the link
  • Use the Merchant admin upload feature to upload the paypalr.mvc module
  • Select Overwrite and update the older version
  • Select admin:stores:payment configuration
  • Click the tab at the top and update the settings

If you are unsure which scenario above applies to you, contact us with as much info about your current and past PayPal modules as you can supply. We will also need your order number, Merchant version and full url to your merchant.mv(c) in order to better advise you.

CIM Auxiliary System Extension module - ONLY Merchant version 4.14 and newer

• New Installation of the CIM Auxiliary System Extension module
  • Go to admin:modules:add module and click the link
  • Use the Merchant admin upload feature to upload the cim_aux.mvc module
  • Once uploaded, click the Add button to add it to the mall/domain
  • Select admin:stores:system extension configuration and assign the module
  • No configuration settings are needed for this module
• Update of prior version of the CIM Auxiliary System Extension module
  • Go to admin:modules
  • Scroll down to CIM Auxiliary System Extension and click the link
  • Use the Merchant admin upload feature to upload the cim_aux.mvc module
  • Select Overwrite and update the older version
  • Select admin:stores:system extension configuration

Required PayPal stub files - Merchant version 4.13 and older

FTP the paypal_1.mv and paypal_2.mv to the Merchant root directory, e.g. Merchant2/ This is the same directory that your merchant.mv file is located in. It should be the same directory that you have identified the Non-Secure URL to Miva Merchant in your Admin:Domain Settings:Site Configuration. These must be FTP'd; they are not installed as modules.

Required PayPal stub files - Merchant version 4.14 and newer

FTP the paypal_1.mvc and paypal_2.mvc to the Merchant root directory, e.g. Merchant2/ This is the same directory that your merchant.mvc file is located in. It should be the same directory that you have identified the Non-Secure URL to Miva Merchant in your Admin:Domain Settings:Site Configuration. These must be FTP'd; they are not installed as modules.

PayPal Reports: If you are using the compiled version of Merchant (4.14+) you can also upload the optional reports module for creating summary reports. Individual payment details are available through the basic PayPal module (fig 1). The summary reports provide more info for broader time periods and multiple transactions (fig 2, 3).

Warning: Since hackers continually come up with new schemes, you must always compare the order total in Miva Merchant with the money received at PayPal. You must go to https://www.paypal.com and verify the actual payment.

1) If your account at PayPal is a "Personal" account, you will need to edit the mmui.mv file to incorporate the hyperlink for PayPal payments to personal accounts. Do NOT make this edit if your account is a Business or Premier account. Locate the function UIModule_Invoice in the mmui.mv file. Locate the second TABLE tag in this function if using Merchant 3.x or 4.x or the first TABLE tag in this function if using Merchant 2.x:
<TABLE BORDER = 0 CELLPADDING = 2 CELLSPACING = 0 WIDTH = "100%">
On the line before this table tag, place the following lines:

<MvDO FILE = "{ g.Module_Library_DB }" NAME = "l.module_id" VALUE = "{ Module_Find_ID( Orders.d.pay_id ) }">
<MvIF EXPR = "{Modules.d.code EQ 'paypal'}">
<MvDO FILE="{g.Module_Root$'modules/payment/paypal.mv'}" NAME="l.paypal_link" VALUE="{PaymentModule_Payment_Link()}">
</MvIF>
Personal PayPal account is not compatible with compiled versions of Merchant. If your PayPal account is personal, you will need to use an older version of the PayPal module. Contact us for info.

2) Optionally, if you want to include a notation in the merchant email which type of payment the buyer used, you can insert the following lines just above the </MvSMTP> tag in your meremail.mv file for Merchant version less than 4.10.

<MvDO FILE = "{ g.Module_Library_DB }" NAME = "l.ok" VALUE = "{ Module_Find_ID( Orders.d.pay_id ) }">
<MvIF EXPR = "{Modules.d.code EQ 'paypal'}">
<MvEVAL EXPR = "{ asciichar( 10 ) $ 'Payment method: ' $ Modules.d.name }">
</MvIF>

In the meremail.mv and custeml starting with Merchant 4.10, locate the line:
<MvDO FILE = "{ g.Module_Library_Utilities }" NAME = "l.ok" VALUE = "{ SendEmail( l.to,l.from,l.cc,l.subject,l.headers,l.message ) }">
Add the following immediately preceeding that line:
<MvDO FILE = "{ g.Module_Library_DB }" NAME = "l.ok" VALUE = "{ Module_Find_ID( Orders.d.pay_id ) }">
<MvIF EXPR = "{Modules.d.code EQ 'paypal'}">
<MvASSIGN NAME = "l.message" VALUE = "{l.message $ asciichar(10) $ 'Payment method: ' $ Modules.d.name}">
</MvIF>

If you are using compiled Miva Merchant, file names ending with .mv above need to be changed to mvc. Then you will need to re-compile the meremail.mv into meremail.mvc.

You can also change the text in your invoice note if your PayPal account is a "Personal" account, not Business or Premier. To do that, scroll down in the paypal.mv file to the function called PaymentModule_Payment_Link which contains the invoice text. This function contains the link which sends the customer to PayPal personal accounts after placing their order. This should only be changed if you have some experience at mivascripting. Backup before editing.

Because customers can spend a good bit of time setting up their PayPal account, you should be sure that you have a lengthy basket time out setting, e.g. 120 minutes. Typical time out error messages might be: "Your keyboard has been idle greater than 15 minutes. Therefore, your basket was automatically expired before you completed your order." or "Your basket's contents changed unexpectedly during the checkout process. Please press your browser's back button and restart the checkout process." To the customer who has been entering data at the PayPal site, this message might not make sense. The reality is that Merchant can only monitor keystrokes when they are entered in the URL containing merchant.mv (merchant.mvc compiled). When the customer is at the PayPal site, merchant.mv (merchant.mvc compiled) is not being refreshed periodically.

The phonein.mvc is an optional file that does not need to be installed. Use it only if you want to have a phone-in option for customers. You would still need a terminal or virtual terminal to process the credit card numbers. That service is not free. For example, paypal.com has a virtual terminal for $20 per month plus per transaction fees.