Main Page
Summary
Introduction to the MO PayJunction module
The MO PayJunction module was created by Made to Order Software Corporation.
This module is an extension to the Ubercart module available in Drupal. It lets you access the PayJunction gateway with just a few clicks.
The module supports direct payments of any product or service directly from your website.
When the UC Recurring module is also installed, then the MO PayJunction module can be used to charge customers a daily, weekly, monthly or yearly recurring fee. Note that the module does not make use of the PayJunction recurring payment facility since that would prevent your website from knowing the current status of the payments. Instead, it uses the UC Recurring module which ensures the current status of your product or service for the corresponding user(s).
- Back to Summary
Requirements
This module requires you to have the Ubercart module installed. The core and Credit Card sub-modules are necessary. The modules required by those sub-modules will also be required, although they all are found in the Ubercart module.
The PayJunction payment is done using the PHP PayJunction library by Made to Order Software Corporation.
- Back to Summary
Installation
In order to install this module:
- Extract the PHP PayJunction library in a folder and copy the payjunction.php file in your misc/php-payjunction folder; you will have to create the php-payjunction folder
- Extract the MO PayJunction tarball under sites/all/modules
- On your server, feel free to delete the doc sub-folder (it is safe since it is just and only static HTML)
- Go to admin/build/modules and select MO PayJunction
Note that you will not be able to enable the MO PayJunction until the PHP PayJunction library is installed.
In order to use the MO PayJunction, you will need to enter your login and password in the MO PayJunction settings window. The settings are found under admin/store/settings/payment/edit/gateways
If you are selling products for shipping, you should be using the "Authorize only" as the credit transaction type and capture the charge whenever you actually ship the good. Note that at this time, you have to go to PayJunction to do the credit card capture and to your online store to mark the payment as processed.
Otherwise, feel free to select "Authorize and capture immediately." This is the easiest solution if you can always ship everything within 48h. If you often run out of stock, this can be problematic.
- Back to Summary
Errors generated by this module.
This module does not generate errors directly on screen. It will return errors to the Ubercart system that will in turn display the error.
The PHP PayJunction library can raise errors. However, when used properly it will not throw anything. You should never see such errors unless something bad happens (i.e. your database loses the login and password...)
It is possible to setup the MO PayJunction module in test mode. In that case, only a few people are expected to be able to use the MO PayJunction module to properly process credit cards in test mode (this protects you from letting anonymous and other users from purchasing software or other goods available for download without due payment. See permissions for more info.)
A test mode card number is any number that satisfy the Luhn number check. For example: 4444 3333 2222 1111. Although a valid credit card number is acceptable, we strongly suggest you don't use such!
The expiration date has to be in the future.
The test CVV/CVC code is 999.
If the address is being checked, enter "8320" for the street address and "85284" for the zip code (without the quotes, of course.)
The draw back of the test mode is that if you have real users who attempt a purchase, that purchase will fail when the module is setup in test mode. Purchases will fail until the module is put back to normal mode. Transactions initiated by users while the module is in test mode generate an error and no PayJunction transactions take place. You may authorize different users based on roles and permissions.
Immediate recurring fees are ignored because you cannot process two fees one after another with PayJunction (it is a good feature to protect your users from double payments.)
This means a recurring fee setup with "0 days" has no effect other than decrementing the number of fees to be processed by 1. To avoid confusion, it is a good idea to not use that feature and add the cost of the first recurring fee to your product (i.e. a product sold for $100 setup fee and $30 recurring fee, should be sold for a total of $130 if the recurring fee is to occur on the same data as the setup fee.)
- Back to Summary
Copyright (c) 2009-2011 Made to Order Software Corp.
http://www.m2osw.com/mo_payjunction contact@m2osw.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
- Back to Summary
on Fri Aug 9 2013 16:19:17