7.1
Table Of Contents
- Table of Content
- Overview
- Understanding PrintShop Mail Web
- Getting Started
- The PrintShop Mail Web Interface
- Publishing Workflow
- Ordering Workflow
- New Document
- Order Manager
- Checkout
- Companies
- Users
- Publication Types
- Collections
- Settings
- About
- License
- Roles
- Languages
- Web Design
- Maintenance
- Settings
- Currencies
- Tax Rates
- Shipping Rates
- Calendar
- Production Settings
- User Input Field Defaults
- Output Folders
- Job options
- Printers
- E-mail Settings
- E-mail Addressees
- Managing E-mail Templates
- Modules Settings
- Enabling a MIS connector
- Installed modules
- Properties
- Enabling a Print Production connector
- Installed modules
- Properties
- Requirements
- Configuring the module
- The PayPal Sandbox
- Processing orders
- Requirements
- Configuring the Authorize.net module
- Test mode
- AVS and CCV checks
- Payment page
- Requirements
- Requesting a test account
- Configuring the iDEAL test dashboard
- Configuring the iDeal module
- Requirements
- Configuring the Moneris module
- Test mode
- Requesting a live account
- AVS and CVD checks
- Payment page
- Add a new Module
- Configure a module
- Delete a Module
- XML (eXtensible Markup Language)
- Options
- Sample POST receive script
- Interaction With PrintShop Mail Design
- Introduction to Regular Expressions
- Introduction
- Skinning Guide
- Getting started
- Creating your own skin
- The template file
- HMTL Outline
- Styling
- Key Concepts
- Style organization
- Header
- User information
- Menu bar
- Background
- Overview tables
- Edit forms
- Sub menus
- Special variables
- Variables for template files
- Variables for style files
- Creating page exceptions
- Creating a page specific template file
- Modifying a page specific template file
- DOM manipulation using jQuery
- Launching code on Document Ready
- Populating fields with computed values
- Removing elements from the DOM
- Adding information to the DOM
- Customizing the store front
- Storefront class
- Creating a hierarchical tree
- Adding a live search option
- Copyright Information
- Index
l Order Description Prefix The end user will see this value in his bank environment as the description of the order he is
about to pay. The shop owner also sees this information in his internet bank account website. This description consist of
this field followed by the order id.
l
Check for AVS(address verification system) response codeIf this option is checked Moneris will perform an address
verification check. Below this option there is a list of all the possible response this address verification check can
produce. The user must choose which response he will accept by checking that option. If the response PSMW
receives is not accepted PSMW will do a void action to cancel the purchase.
l
Check forCVD (card validation digits) response code If thisoption is checked Moneris will perform a card validation
digit check. Below this option there is a list of all the possible results that this check can generate. The user must
choose which result he will accept by checking that option. If the result PSMW receives is not accepted PSMW will
do a void action to cancel the purchase.
Test mode
You can also request a developer test account from Moneris to make test payments.
The developer test account is actually a shared account that is used by all the people who are currently testing their web shop
against the Moneris test gateway. Therefore you should not make any changes in the test account settings. You can also see
other transactions that where not generated by yourself.
Moneris has provided several documents on their website which describe how the testing process goes. The shop owner
should download the following documents from http://www.eselectplus.ca/en/downloadable-content if the shop owner does-
n't have access to this part of the site he must sign up before he can download the documents.
The following documents should be downloaded:
l Integration Guide - General -> PHP API Integration Guide
l Others -> Other Documents -> eFraud verification result codes
l Others -> Other Documents -> Response Codes
l Others -> Other Documents -> Test Environment CVD/AVS Result Table
l Others -> Other Documents -> Test Environment Penny Value Response Table
The test environment of Moneris uses shared test accounts. In the PHP API Integration Guide on page 21 there is a list of sev-
eral test accounts that can be used. If you want to test CVD or AVS you must use store5. In the same document on page 22
there is al list of credit card numbers that can be used in the test environment.
In the payment connector settings on the PSMW website you must enter the store id and api token of a test account and set the
gateway to test before you can make any test payments.
The penny value will determine if the payment will be successful in the test environment please read the Test Environment
Penny Value Response Table document for more details.
The AVS and CVD checks are additional; this means that those checks could fail but you could still have a successful trans-
action, if that happens PSMW will perform a void action on the payment to cancel it. The AVS or CVD check will only be per-
formed if you have enabled them in the payment connector's settings page.
In the settings page you can also select which AVS and CVD response code you want to accept. If the transaction was suc-
cessful PSMW will do an additional check by looking at the AVS and CVD response code. If the response code is not accepted
according to the payment module settings PSMW will do a void action to cancel the transaction, that void action is than visible
in the moneris account website.
To manage your Moneris account you will have to go to the Moneris developer merchant account website:https://esqa-
.moneris.com/mpg/
©2010 Objectif Lune Inc - 175 -