Subsciption PayPal Payment |
Copyright © 2001, William Weiland |
Overview The purpose of this module is to allow customers to place a subscription order at a Miva Merchant © Miva Corp. enabled store which they will then pay for using their PayPal © x.com account. |
|
Initial Setup Use the Merchant admin upload feature to upload the paypals.mv (paypals.mvc compiled) module. Once uploaded, click the Add button to add it to the mall/domain. If you are updating an existing module, click Modules, then the link to the module, then the file upload feature, overwriting and updating the older version. In admin, under your store, click on the link for Payment Configuration. Assign the module and Update it to install it in your store. Click the link for Subscription Payment via PayPal to enter the configuration settings. For compiled Merchant only: Through admin, upload the file cim_aux.mvc (CIM Auxiliary System Extension). Install it as a system extension module in your store. No configuration settings are needed for this module other than to Assign it to the store. This requirement does not apply to uncompiled Miva Merchant stores, version 4.13 and older. FTP the paypal_1.mv, paypal_2.mv and paypal_3.mv (paypal_1.mvc, paypal_2.mvc and paypal_3.mvc compiled) to the Merchant root directory, eg Merchant2/ This is the same directory that your merchant.mv (merchant.mvc compiled) 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. Compiled version (Merchant 4.14 and newer) only. If you are upgrading from a previous version of our paypal module and the version you are upgrading is dated Nov 11, 2003 or newer, be sure you upgrade all of the files in the paypal.zip file. The modules paypals.mvc and cim_aux.mvc are updated through admin:modules:name of the module, upload, then UPDATE. The paypal_1.mvc, paypal_2.mvc and paypal_3.mvc are FTPd to the /Merchant2/ directory, replacing the previous files of the same name. |
|
Configuration Settings Enter data into the applicable input fields. Merchant Script Name PayPal ID URL to PayPal Conversion Rate from USD ($) Your Store Logo URL Payment Method Prompt
Additional Instructions Instant Payment Notification (IPN)
Subscription Payment Terms
|
|
Editing Requirements (skip if using the OpenUI) If you are using the Miva Merchant User Interface (mmui) you will need to make some very simple edits to the core files. Be sure to do that with a text editor (NO WYSIWYG editors) such as Programmer's File Editor (PFE) so as not to damage the mv files. ALWAYS BACKUP your unmodified mv files in case you make a mistake. 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.
If you are using compiled Miva Merchant, you will need to re-compile the
meremail.mv into meremail.mvc.
|
|
Be Aware 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 is not being refreshed periodically. |