Contributions

2006-07-05 mischa
* v1.0.2 released
* Fix in order declined notification
* Status output in callback
* Callback IP updated

2006-03-17 mischa
* v1.0.1 released
* Fix shipping name

2005-12-26 mischa
* v1.0.0 released
* Add icelandic translations

2005-09-14 mischa
* v1.0.0-pre4 released
* Add product attributes

2005-09-11 mischa
* v1.0.0-pre3 released
* Properly escape comments in SQL queries

2005-09-06 mischa
* Updated to use new API
* Allow admin to enable card types
* Allow admin to choose the Multicards order page language

2005-08-01 mischa
* v1.0.0-pre2 released
* Spanish and German translation

2005-03-14 mischa
* v1.0.0-pre1 released
* Code based on the osCommerce PayPal IPN module v1.1 from the osCommerce Team
Design Requirements: osCommerce Multicards Payment Module v1.0.0
Author: Mischa Untergrass

module:
-------
+ osCommerce 2.2 Milestone 2
+ communicates with multicards payment processor and notifications
+ installation like other payment modules
+ uninstall removing everything again (except for order statuses)
+ don't overwrite other files
+ follow osCommerce coding standards

administration:
---------------
+ enable / disable module
+ multicards merchant id
+ multicards page id
+ notification password

+ waiting for notification order status
+ accepted order status
+ credited order status
+ creditrequested order status
+ declined order status
+ suspended order status
+ unknown order status
+ voided order status

+ enable visa
+ enable mastercard
+ enable eurocard
+ enable american express
+ enable discover
+ enable diners club
+ enable carte blance
+ enable jcb

+ choose multicards order page language

+ debug e-mail address
+ sort order

order:
------
+ post fields to multicards processor
+ optional: tax

notification:
-------------
+ check validity of fields
+ check NotificationPassword
+ verify MultiCards IP (64.39.17.164)
+ check valuta (voided if invalid)
+ check amount (voided if invalid)
- could: detect duplicate notifyids

status update:
--------------
+ change status
+ show comments: status, reason, origin, order_num, notifyid, created,
amount, valuta
osCommerce 2.2 Milestone 2 Multicards Payment Module v1.0.2
Author: Mischa Untergrass

MultiCards: http://www.multicards.com/
osCommerce: http://www.oscommerce.com/

Summary
-------
The MultiCards module stores orders prematurely in the database to be processed
by MultiCards notifications. This takes care of customers not returning back to
the store to store the order in the database, and allows processing to occur
when the MultiCards notification is received.

This module was built to be as simple as possible without having the need to
touch core files for installation and usage.

The osCommerce PayPal IPN module from the osCommerce Team has served as a basis
for the development of this module.

Installation
------------
1. Copy the files in the directory structure set in the contribution download
file to your osCommerce installation directory.

Note: Be sure to also copy the new "ext" directory to the catalog root
directory.

2. Go to the Administration Tool->Modules->Payment section at your osCommerce
Administration Tool.

3. Install the MultiCards module and configure its parameters.

Note: The module is disabled by default so configuration can occur during the
operation of a live store.

4. Contact MultiCards customer support to configure your merchant account.

Configuration Parameters
------------------------

* Enable MultiCards Module
When enabled, the customer is allowed to choose the MultiCards payment method
at the checkout procedure.

* MultiCards MerchantID
Your 6-digit MultiCards merchant number.

* MultiCards PageID
Refers to the page ID (page properties) in the MultiCards database.

* Notification Password
This password is used to validate the origin of notifications. It has to match
the one configured for you by MultiCards customer support.

* Set Waiting Order Status
As soon as the checkout confirmation page is shown to the customer, the
contents of the shopping cart is prematurely stored in the orders table with
this defined order status.

If the customer decides to alter the content of their shopping cart (different
products, different shipping or billing address, or if the currency has been
changed), the order is deleted from the orders table and is reinserted with the
updated information.

This only occurs when the checkout confirmation page is shown to the customer,
so if the shopping cart has been modified, it will be out of sync with the
premature order in the database until the checkout confirmation page is shown
again.

If a premature order has been stored in the orders database table and the
customer does not make the payment transaction at MultiCards, the order will
remain in the database until manually removed by the store administrator. This
can be done easily by selecting the "Set Waiting Order Status" status on the
status filter on the Administration Tool->Customers->Orders page, to show the
current existing orders made prematurely.

Please take care when removing premature orders, to be sure they are a few days
old.

Premature orders will have their order status set to the "Set Waiting Order
Status" value but will not contain an entry in the order status history
database table until the customer has made the payment transaction at
MultiCards and has returned back to the store to the checkout process and
checkout success pages. (This can be used to differentiate between invalid and
valid orders)

* Set Accepted Order Status
This is the status the premature order is set to when a notification from
MultiCards has been received, and has returned the result of 'accepted'.

Accepted orders will automatically have an order status history record inserted
containg the MultiCards status values in the order comment. This comment will
not be sent to the customer via e-mail, but is visible to the customer when
they view their order online.

* Set Credited Order Status
Same as Accepted Order Status, but for 'credited' notifications.

* Set Credit Requested Order Status
Same as Accepted Order Status, but for 'creditrequested' notifications.

* Set Declined Order Status
Same as Accepted Order Status, but for 'declined' notifications.

* Set Suspended Order Status
Same as Accepted Order Status, but for 'suspended' notifications.

* Set Unknown Order Status
Same as Accepted Order Status, but for 'unknown' notifications.

* Set Voided Order Status
Same as Accepted Order Status, but for 'voided' notifications.

Additionally this order status is used when there is a mismatch in the amount
and/or currency in the notification. A warning will be appended to the order
comment.

* Enable Visa
When enabled, Visa payments are accepted.

* Enable Mastercard
When enabled, Mastercard payments are accepted.

* Enable Eurocard
When enabled, Eurocard payments are accepted.

* Enable American Express
When enabled, American Express payments are accepted.

* Enable Discover
When enabled, Discover payments are accepted.

* Enable Diners Club
When enabled, Diners Club payments are accepted.

* Enable Carte Blance
When enabled, Carte Blance payments are accepted.

* Enable JCB
When enabled, JCB payments are accepted.

* MultiCards Language
The language that the MultiCards order pages should appear in.

* Debug E-Mail Address
All parameters and errors from an notification are sent to this e-mail address
for debugging/verification purposes. Leave this empty to disable.

* Sort order of display
The order the MultiCards payment method should be shown on the checkout payment
page if more than one payment method is available.

Known Issues
------------
* If the customer does not hit the "click here to finish your order!" button
once payment has been made at MultiCards, and the customer goes back to the
store and modifies their shopping cart, it will delete the order made from the
database when they enter the checkout confirmation page and no MultiCards
notification has been received during this time. This should not happen at all
though...
There is no way around this without making changes to the core codebase and
database structure.

multicards modules remember to read the readme file and if you have any questions the please email me

ompsco@omps.co.uk

thanks