QMerchant Manual Version 10.0

QMerchant Manual Version 10.0
1 QMerchant Manual QMerchant Manual Version 10.0 This document reflects version 10.0.0 of QMerchant. Some of the screenshots are just examples and may differ from the real product. QBAutomation is a trademark and service mark of RHAV. addQin is a trademark and service mark of RHAV. QuickBooks is a registered trademark and service mark of Intuit Inc. in the United States and other countries Authorize.Net is a registered trademark of Lightbridge, Inc. All other marks are the property of their respective owners. Copyright © 2002 – 2015 by RHAV All rights reserved. October 1, 2014 2 QMerchant Manual Table of Contents INSTALLATION ........................................................................................................................ 4
PREPARATION FOR USE WITH QUICKBOOKS (DESKTOP VERSIONS) ................................................... 9
SETUP FOR USE WITH QUICKBOOKS (DESKTOP VERSIONS) ............................................................ 10
SETUP FOR USE WITH QUICKBOOKS POINT-­‐OF-­‐SALE ................................................................... 11
START USING QMERCHANT .................................................................................................... 13
SETTINGS ............................................................................................................................ 14
KEYBOARD SHORTCUTS .......................................................................................................... 18
MULTIPLE MERCHANT ACCOUNTS ........................................................................................... 19
USE QMERCHANT AS VIRTUAL TERMINAL WITHOUT QUICKBOOKS ............................................. 20
USE QMERCHANT WITH QUICKBOOKS PRO, PREMIERE, ENTERPRISE ............................................ 22
WORKING WITH SALES RECEIPTS ............................................................................................. 23
USE OF CHECKS .................................................................................................................... 27
WORKING WITH INVOICES / RECEIVE PAYMENTS ........................................................................ 28
WORKING WITH SALES ORDERS ............................................................................................... 30
WORKING WITH CREDIT MEMO .............................................................................................. 31
RECURRING BILLING .............................................................................................................. 32
BATCH PROCESSING (‘UNATTENDED MODE’) ............................................................................ 35
BEHAVIOR OF THE GET PAYMENT BUTTON ................................................................................ 36
USE QMERCHANT WITH QUICKBOOKS – POINT OF SALE ............................................................. 38
VOIDS, CREDITS AND REFUNDS ............................................................................................... 42
QUICK MODE ....................................................................................................................... 43
SERVER INSTALLATION AND MANAGEMENT ............................................................................... 44
LEVEL II DATA ...................................................................................................................... 45
LEVEL III DATA ..................................................................................................................... 46
CIM (AUTHORIZE.NET CUSTOMER INFORMATION MANAGEMENT) ........................................ 47
USE OF MAGNETIC STRIPE READERS ........................................................................................ 49
QMERCHANT MENU ENTRIES ................................................................................................. 50
THE LOG FILE ....................................................................................................................... 52
TRANSACTION TYPES AND OTHER CODES ................................................................................... 53
PRINT RECEIPT ..................................................................................................................... 54
CHANGE THE PRINT RECEIPT .................................................................................................... 54
BARCODE PRINTING .............................................................................................................. 56
RECEIPT FORMATTING PARAMETERS AND COMMANDS ................................................................ 56
RE-­‐PRINT A RECEIPT. ............................................................................................................. 57
CUSTOM SETTINGS ................................................................................................................ 58
REPORTS ............................................................................................................................. 63
ACTIVATION ......................................................................................................................... 64
PAYMENT GATEWAYS ............................................................................................................ 65
AUTHORIZE.NET API LOGIN ID AND TRANSACTION KEY .............................................................. 66
TIPS .................................................................................................................................... 67
TEST YOUR CONNECTION TO THE PAYMENT PROVIDER: ................................................................ 67
October 1, 2014 3 QMerchant Manual GET THE QMERCHANT VERSION AND SERIAL NUMBER ................................................................. 67
TROUBLESHOOT ................................................................................................................... 68
Prerequisites .................................................................................................................... 68
How do I get the transaction key from Authorize.Net? ................................................... 68
I see the following message from Authorize.Net ............................................................. 68
Supported Payment Gateways: ........................................................................................ 68
How can I see the authorization and transaction id of a sales receipt? ........................... 68
Cannot get the credit card number from QuickBooks ..................................................... 69
QuickBooks Desktop Versions i.e. Enterprise and Windows 7 ......................................... 69
How can I disable the integrated QuickBooks merchant service? ................................... 69
Error message ‘Market type is invalid. ............................................................................. 70
I want to change the QuickBooks version I selected during installation. ......................... 70
APPENDIX A: SCREENSHOTS FOR THE USE WITH QUICKBOOKS POINT-­‐OF-­‐SALE (OLDER VERSIONS) ...... 71
APPENDIX B: AUTHORIZE.NET RESPONSE CODES (EXCERPT FROM AUTHORIZE.NET DOCUMENTATION)74
October 1, 2014 4 QMerchant Manual INSTALLATION After download, please run the downloaded executable. Step 1: The following dialog appears. Step 2: Click ’Next’ to continue. The RHAV license agreement is displayed. You must accept the license, otherwise you cannot use QMerchant. October 1, 2014 5 QMerchant Manual Step 3: Confirm the installation folder. We recommend leaving it as it is and click ‘Install’ to complete the installation. October 1, 2014 6 QMerchant Manual Step 4: Finish the installation and launch QMerchant. Step 5: Use the setup wizard. The setup is a two-­‐step process. First we setup your QuickBooks connection and then we establish the connection to the selected payment provider. Please select your QuickBooks version and click continue. QMerchant tries to connect to QuickBooks. If this is the first time you install QMerchant, some dialogs will appear (as described in the following chapter). Please respond to those dialogs. After the connection is successful, then please select your payment gateway. The following selections are currently available: Authorize.net You need the API Login ID and the transaction key. You get both from the authorize.net merchant website under security settings. PPI You need an Account Token. Please ask PPI Paymover for it. Other You are going to use one of the other supported payment gateways. Please follow the in-­‐
structions and set it up via the QMerchant settings dialog. I will setup the Please define the payment gateway via the QMerchant settings dialog payment provider later Now enter the credentials your payment provider gave you. October 1, 2014 7 QMerchant Manual Below is a screenshot of a successful setup for a QuickBooks desktop or server version and authorize.net. Here is a screenshot of a successful setup for a QuickBooks Point-­‐of-­‐Sale and PPI. If we are able to establish the connection to your payment provider, you are ready to use QMerchant. Press the ‘Ready to use QMerchant’ button to close the wizard. Please review your settings, connect to QuickBooks and start with QMerchant. October 1, 2014 8 QMerchant Manual If your payment provider is not listed, please select OTHER. From the QMerchant dashboard click Settings And enter the payment provider information. After installation you see the following icon at your desktop. Also there is an entry in your Programs Menu named QMerchant. To run the application, double-­‐click that icon. If you choose to uninstall QMerchant, you can do this either from the program menu or via the Control Panel -­‐ Unin-­‐
stall Programs. October 1, 2014 9 QMerchant Manual PREPARATION FOR USE WITH QUICKBOOKS (DESKTOP VERSIONS) Open your QuickBooks application. Then invoke from the menu Edit | Preferences. Choose Integrated Applications and the Company Preferences tab. Make sure that the "Don't allow any application to access this company file" is un-­‐checked. October 1, 2014 10 QMerchant Manual SETUP FOR USE WITH QUICKBOOKS (DESKTOP VERSIONS) Open QuickBooks. You will be asked to authorize our application (This is a one-­‐time process). QMerchant requests ac-­‐
cess to QuickBooks. The following QuickBooks message -­‐ or similar for QuickBooks Point of Sale -­‐ appears: Please continue as indicated with 'Yes, whenever this QuickBooks company file is open' and don't forget to check the 'Allow ....' checkbox. This is necessary, because we will access / modify the customer credit card information. A confir-­‐
mation dialog will appear Confirm with 'Done' and the next dialog with Yes. October 1, 2014 11 QMerchant Manual SETUP FOR USE WITH QUICKBOOKS POINT-­‐OF-­‐SALE Please login as SysAdmin and make sure that QuickBooks Point-­‐of-­‐Sale is in network mode. You can get this dialog in POS from the File menu and then Company Operations (older versions) or ‘Switch company file to multiuser mode’. QMerchant acts like an additional workstation to POS When QMerchant tries to access QuickBooks Point-­‐of-­‐Sale for the first time during the setup dialog or when you connect to QuickBooks, you see the following dialog sequence: QMerchant looks for available Point-­‐of-­‐Sale servers to connect to. After a server is found or selected, you must give QMerchant the permission to access POS. Please choose ‘Yes, Always’. October 1, 2014 12 QMerchant Manual Then after a short period of time the QMerchant dashboard shows that it is connected to QuickBooks and you can start to process payment. Please continue with the section ‘Use QMerchant with QuickBooks Point-­‐of-­‐Sale’. October 1, 2014 13 QMerchant Manual START USING QMERCHANT From the Dashboard press the yellow button ‘Connect to QuickBooks’. By doing that, a connection to QuickBooks is established. The Dashboard then looks like this: October 1, 2014 14 QMerchant Manual SETTINGS Open the Settings dialog (the box in the lower left). The picture above shows an example for authorize.net settings. Please read the explanations below. If you work with QuickBooks Point-­‐of-­‐Sale, the QuickBooks Settings (right side) are not visible because that is done au-­‐
tomatically. There are some special settings available via the menu entry ‘Special’ 1. Itemized: If checked not only the totals but also the single items are send to the payment provider. This option is not available for all payment providers. 2. Debug Mode: In debug mode, all message to and from QuickBooks are recorded in a log file. We recommend to use this only on advice by our support team. 3. Multiple Merchant Accounts: Enables the usage of several different merchant accounts with the same of with differ-­‐
ent payment providers. 4. Allow Batch Processing: Enables the process of a series of payments in unattended mode (authorize.net only). 5. Level 3: Level 3 transaction mode (PayTrace only). October 1, 2014 15 QMerchant Manual The fields have the following meaning: Provider Information Select one of the implemented payment providers. You must have Payment Gateway a contract with them. They provide you with the credentials neces-­‐
Provider sary. Authorize.Net Settings (you must obtain this information from Authorize.Net) API Login ID Authorize.Net Login ID or API Login ID Transaction Key Transaction key from Authorize.Net CARD PRESENT Check if you have a ‘Card Present’ account with Authorize.Net. By default it is set to a Card NOT Present account Address of the Authorize.Net server. Server https://secure.authorize.net/gateway/transact.dll Address For card present accounts: https://cardpresent.authorize.net/gateway/transact.dll Transaction will send be send to Authorize.Net in test mode only. Test Mode The credit card will not be processed, but you will receive a proper response. (The trial application is always set to Test mode). PayTrace Settings (you must obtain this information from PayTrace) User Name PayTrace User Name Password PayTrace Password (Please remember you must change your Pay-­‐
Trace password every 60 days) Server Address of the PayTrace server. Address https://paytrace.com/api/default.pay Transaction will send be send to PayTrace in test mode, using the Test Mode demo account. The credit card will not be processed, but you will receive a proper response. PPI Paymover (You must obtain this information from Payment Processing Inc.) Account Token Account Token generated from Payment Processing. Check this if you have a Retail (industry type) account. Otherwise DIRECT MARKETING is assumed. In case you use a card reader, RETAIL those transactions are automatically assigned to the industry type RETAIL. October 1, 2014 16 QMerchant Manual Hardware Use a magnetic stripe reader. Select the type of your magnetic stripe reader. QMerchant supports USB HID or USB keyboard emu-­‐
lation interfaces card readers. Among the supported types are: MagTek Mag Mini 21040101 or newer Card Reader UIC MSR 213 Encrypted devices: (PPI gateway) MagTek MagneSafe card reader MagTek IPad Pin Pad Receipt Printer Select the receipt printer you use. The selection of ‘None’ means that there is no printer used. Auto Print If checked, automatically print the receipt after a successful trans-­‐
action. Print Preview Check this box, to review the receipt before printing. Print Copies Select the number of copies. QuickBooks Settings (There are no specific transaction or payment types for QuickBooks Point of Sale) Choose the QuickBooks transaction types for payment processing (check all that apply). Currently we support the following transac-­‐
tion types from QuickBooks: ‘Sales Receipt’, ‘Receive Payment’, Transaction Types ‘Credit Memo’, ‘Invoice’ and ‘Sales Order’. We recommend check-­‐
(not available with POS) ing the first three transaction types. For use of Recurring Billing you must check Invoice. Default settings are: ‘Sales Receipt’, ‘Receive Payment’, ‘Credit Memo’. Which types of payment will be handled by your payment proces-­‐
Payment types sor (check all that applies)? These payment types are defined in QuickBooks in the Payment Method List. Usually you check all types of Credit Card Payments. Preferences Automatically con-­‐
Check if you will automatically log on to QuickBooks. nect to QuickBooks QuickMode When checked, a minimal payment window is shown for the usual day-­‐to-­‐day transactions. Use ShortCuts Enable use of keyboard shortcuts. autoClosePayment October 1, 2014 Default false. If set to true the payment dialog is closed automatically after print-­‐
17 QMerchant Manual ing or if the printer selection in the settings is set to ‘None’ after a successful payment transaction. Always show the Select Transaction Dialog. Default: true. If set to false the Select Transaction Dialog is shown only when: showSelectDialog 1. No transactions are found. 2. More than one transaction is found. Default: false. If set to true, the Select Transaction dialog is closed automatically if there was only one transaction shown. autoCloseSelectDialog Send an email receipt to the customer via the selected payment gateway. Currently supported gateways are: Send Email Receipt authorize.net (Overrides the merchant account settings) PayTrace Please enter the appropriate data and do not forget to press ‘Save’ to store your settings. October 1, 2014 18 QMerchant Manual KEYBOARD SHORTCUTS Keyboard shorts simplify the use of some of the QMerchant dialog. Five different short cuts are implemented for the following dialogs and are active when you are connected to QuickBooks. The shortcuts can get modified via the custom settings dialog. To use the shortcuts, please enable it in the settings dialog. G LOBAL There is a global shortcut Alt – G that directly opens the payment dialog from any application. When you i.e. have saved a transaction in QuickBooks, by pressing Alt-­‐G the payment window comes. There is no need to bring QMerchant to the front. M AIN W INDOW Alt – G Get the payment. Open either the payment dialog or the select transaction dialog. S ELECTION O F TRANSACTIONS W INDOW Alt – P Process the selected transaction. Open the payment window. Alt – C Close the window. P AYMENT W INDOW (SMALL AND LARGE W INDOW ) Alt – S Submit the transaction Alt – R Print the Receipt Alt – C Close the window. October 1, 2014 19 QMerchant Manual MULTIPLE MERCHANT ACCOUNTS You can simultaneously use multiple merchant accounts. The administration is done as follows: Please enable the multiple merchant accounts feature from the special menu. Enter all necessary information in the Payment Gateway Information box. Then enter in the Multiple Merchant Accounts text field a name for this account and press ‘Add’. This will create this merchant account. With ‘Del’ you delete the selected account and with ‘Chg’ you will change the information for the selected account. If you never added an account, the information as shown in the Payment Provider Gateway will be used. If you added only one account, that one will be used automatically. If you defined more than one merchant account, you have to select the merchant account to use at the dashboard. The merchant account selection is visible only if you have defined a list of merchant accounts. October 1, 2014 20 QMerchant Manual USE QMERCHANT AS VIRTUAL TERMINAL WITHOUT QUICKBOOKS From Tools menu choose ‘Virtual Terminal’. The following dialog appears: Enter the necessary information and press Submit to process the credit card. Depending on the version of QMerchant, you can process e-­‐checks with Authorize.Net also. To switch between credit card and e-­‐check, make your selection of the payment type at the bottom of the dialog mentioned above. The e-­‐check payment dialog is as follows: October 1, 2014 21 QMerchant Manual With the virtual terminal you can also process other transaction types. Those are listed at the bottom of the payment screen und TX-­‐Type. Most common types are VOID Void a previous – not yet settled transaction. REFUND Refund a previous settled transaction Please enter in the parameters field (bottom left) the transaction and the authorization code separated by a slash i.e. 0006780/12345. Then enter the refund/void amount, credit card number and expiration data and press submit. If you do not know transaction id or authorization code, both are included in the transaction report or the transaction log, accessible from the QMerchant menus. October 1, 2014 22 QMerchant Manual USE QMERCHANT WITH QUICKBOOKS PRO, PREMIERE, ENTERPRISE Always start QuickBooks first, because QMerchant is triggered automatically by QuickBooks. After a connection to QuickBooks was established, the Dashboard looks like this: There are several transaction types supported by QMerchant, which are used for further transaction processing: • Sales Receipt, • Receive Payment, • Credit Memo • Invoices (automatically creates a receive payment transaction or used for recurring billing) • Sales Order (automatically creates a receive payment transaction if it is a CAPTURE transaction) Based on example screenshots from QuickBooks we will outline the typical payment procedure. This process remains the same with other QuickBooks version, but the screens may look different. Press the green ‘Get Payment’ button to capture a payment from QuickBooks. Hint: If you have stored credit card numbers in QuickBooks and you would like to use them in QMerchant, please open the payment information of the customer in QuickBooks and copy and paste the credit card number into the account no. field. If that field is used for other purposes, please follow the instructions in the QMerchant Troubleshoot section (#10) October 1, 2014 23 QMerchant Manual WORKING WITH SALES RECEIPTS (The outline of the QuickBooks dialogs may vary and be different depending on the QuickBooks version you use). Create a sales receipt in QuickBooks. In order to process the payment and charge a credit card, it is important that you select the correct Payment Method. This must be one of the payment methods you accepted in the settings dialog. Af-­‐
ter completing the sales receipt, press ‘Save & Close’ or’ Save & New’. Make sure, that the the checkbox ‘’Process… payment when saving’ above the ‘Save’ buttons in NOT checked. Otherwise you will use Intuit for payment processing. Now press the green ‘Get Payment’ button in QMerchant. The information of the sales receipt is transmitted to QMer-­‐
chant and the following dialog pops up. Most fields contain information of the sales receipt. Please complete the missing fields (Those in yellow are most time required) and press submit. This will send the information to your payment proces-­‐
sor for further processing. October 1, 2014 24 QMerchant Manual If you didn’t add some required information, you will see those fields flagged red and further processing is suspended until you enter the information. As a result, the payment processor responds either with a success or a failure. In any case you will get an appropriate message. In case of a success the result will appear as: October 1, 2014 25 QMerchant Manual The resulting authorization code and/or the transaction id are shown. Whenever you added or changed the credit card information, this information can become stored in QuickBooks. Please press ‘Update QuickBooks’ to do so. In any case, the authorization code and the transaction id are recorded in QuickBooks. In case of a failure, you can directly return to the sales receipt in QuickBooks and do the necessary changes there. Have in mind; the transaction is recorded in QuickBooks, even if the processing with your payment provider fails. So, you are responsible to take corrective actions. As mentioned above, the authorization code, the transaction id, the amount charges and the last four digits of the credit card are recorded in QuickBooks. To make those visible, you must change your sales receipt template. In the sales re-­‐
ceipt press ‘Customize Template’ and select your template from the dialog. ‘Edit’ will lead you to the following screen: October 1, 2014 26 QMerchant Manual Under fields is an additional entry Q_Authorization. There are also some fields labeled Q_RB_. Those are for use with recurring billing. Please check the field Q_Authorization and add some title like ‘TX ID’ to it. And press ‘OK’ to save your changes. The TX ID will appear in the sales receipt as shown below. October 1, 2014 27 QMerchant Manual USE OF CHECKS An alternative to the use of credit cards is the electronic check feature. (Please note that this is not supported by all payment gateways) Just select in QuickBooks as payment method ‘Check’. In QMerchant the echeck payment information will come up. Most values are preset. You have to enter the bank account number and the bank routing number. As you can see at the bottom of the payment window as payment type ECHECK is selected. There is also a way to automate the entry of the banking information. In QuickBooks you can define some additional fields that hold this data for each customer. Please name the fields as follow: BankName: Name of the bank BankAccount: Customer account number BankRouting: Routing of the bank (ABA) In case you work with invoices in QuickBooks, then you to manually select ECHECK as payment type in the QMerchant payment screen. October 1, 2014 28 QMerchant Manual WORKING WITH INVOICES / RECEIVE PAYMENTS (The outline of the QuickBooks dialogs may vary and be different depending on the QuickBooks version you use). When an invoice is recorded in QuickBooks, there is not a direct payment involved. Payment will usually be done by a Receive Payment transaction. Make sure that you select the appropriate Payment Method and then ‘Save & Close’ or ‘Save & New’. Make sure, that the the checkbox ‘’Process… payment when saving’ above the invoice list is NOT checked. Otherwise you will use Intuit for payment processing. Now press the green ‘Get Payment’ button in QMerchant. The information of the payment is transmitted to QMerchant and the same dialogs as described with the sales receipt procedure above will follow. When in the Settings under Transaction Types the option ‘Invoice’ is checked, invoices for payment can be selected manually. From the dashboard press the green button ‘Wait for Payment’. This will show a list of unpaid invoices as well as of all transactions from the last 2/15 minutes. Usually only unpaid invoices are retrieved. In addition to this retrieved invoices are filtered by the payment terms. I.e. when a payment term CreditCard is specified, only invoices with this term are retrieved. All others are ignored. By de-­‐
fault, there is filtering of invoices disabled. To enable it, please change the ‘FilterInvoicesbyTerm’ in the ‘Custom Set-­‐
tings’. Please read more under ‘Custom Settings’. From the invoices shown, highlight the one for the payment and press OK. October 1, 2014 29 QMerchant Manual You can pay the invoice similar to the sales receipt explained earlier on. After a successful payment, QMerchant auto-­‐
matically creates a receive payment in QuickBooks. In order to see the successful payment in the invoice, you have to customize the invoice template as described for the sales receipt. The invoice will then look like the screenshot below. October 1, 2014 30 QMerchant Manual WORKING WITH SALES ORDERS The use of sales orders in conjunction with QMerchant is similar to the handling of invoices. First you create in QuickBooks a sales order. Depending on your mode of operation you can now select in QMerchant the sales order and process it with the payment provider. Usually you just do an authorization to validate the credit card and amount. We will store a successful authorization back to QuickBooks. When you later create an invoice for the sales order then you can capture the amount. It is basically the same as with invoices. QMerchant displays the authorization code / transaction id of a former authorization transac-­‐
tion. After a successful capture, a receive payment transaction is automatically generated in QuickBooks. If you have chosen to charge the credit card with the sales order, then a receive payment transaction is created and your customer has a credit until you apply it to an invoice later on. An example (for authorize.net): In QuickBooks customize the templates for sales orders and invoices and made visible the additional field Q_Authorization to see the authorization code and transaction id. In QMerchant in the custom settings change DefaultTxtype to AUTH_ONLY to avoid incidental capture of sales orders. Also in the QMerchant settings select Sales Order as transaction type (So in the right upper list at least Sales Order and Invoice is checked). Now create a sales order in QuickBooks and capture it via the QMerchant get payment button. In the payment screen at the bottom the txtype is selected as AUTH_ONLY. Submit and authorize the credit card and store the authorization code back to QuickBooks. Then create in QuickBooks from the sales order an invoice. Open it in QMerchant via the get payment button. At the pay-­‐
ment screen at the left bottom is the authorization code shown and as txtype VOID is selected (Unfortunately this is the de-­‐
fault). Change VOID into PRIOR_AUTH_CAPTURE and submit. This will not ask for any credit card info and the card will be charged. October 1, 2014 31 QMerchant Manual WORKING WITH CREDIT MEMO (The outline of the QuickBooks dialogs may vary and be different depending on the QuickBooks version you use). A Credit Memo is a transaction where you refund the customer. This can be done by refunding a credit card. The steps in QuickBooks are as follows: Create the Credit Memo. Save it and choose how to process the credit memo. Issue the refund. Make sure that you select the Payment Method as indicated and press ‘OK’. The processing with Au-­‐
thorize.Net is the same as described earlier on. Make sure, that the the checkbox ‘’Process… payment when saving’ at the bottom is in NOT checked. Otherwise you will use Intuit for payment processing. Then press the green ‘Get Payment’ button in QMerchant and proceed in QMerchant. October 1, 2014 32 QMerchant Manual RECURRING BILLING Recurring Billing is supported for the QuickBooks desktop versions (not Point-­‐of-­‐Sale) and with authorize.net as payment provider. There are some steps necessary to enable recurring payment. 1. With authorize.net you need a card-­‐not-­‐present account with recurring billing enabled. 2. In QuickBooks make sure that you have under Terms an entry ‘Recurring Billing’. Furthermore check that you have the same entry available as payment method. These entries are automatically added when you install QMerchant. 3. In the QMerchant settings dialog, select Invoice as Transaction type. 4. You use recurring billing with invoices. We have two different scenarios here. a. You have an unlimited recurring billing. Please choose as invoice amount the regular (i.e. monthly) payment rate. In QuickBooks, enter an invoice amount with the regular payment amount and select ‘Recurring Billing” as Terms. b. You have a fixed number (i.e. 12) of payments. In QuickBooks, enter an invoice amount with the entire expected payments and select ‘Recurring Billing” as Terms. The invoice template will look like the following: In the picture above you also see some additional fields, which are filled by the QMerchant application. They have the following meaning: Q_Authorization: authorization code, transaction id , subscription id whatever is appropriate, amount charged Q_RB_Info: Rate for the recurring billing of this invoice, Interval in which the billing occurs and maximal number of billings. When you save the invoice, you can retrieve that transaction and display it – via the ‘Get Payment’ button in the payment dialog of QMerchant. At the bottom of the merchant dialog Recurring Billing is selected as well as Create Subscription. October 1, 2014 33 QMerchant Manual Additionally the Recurring Billing Dialog is visible. The fields have the following meaning: • Start: Date, when the billing starts. By default it is today’s date. The format is YYYY-­‐MM-­‐DD • Every: Period in which the billing occurs. I.e. 1 Month = Every month, 10 Days, every then days • Times: Number of times the billing occurs or Unlimited. When you change the number of times, the amount will be adjusted. It is calculated as amount of the invoices divided by times. Except you choose ‘Unlimited’. Then the amount is not adjusted. If these fields are correct and you entered the credit card information, the subsription is submitted to the payment provider. That’s all. After a sucessful completion the subscription id is shown. When you go back to the invoice in QuickBooks, it will look like this with all Q_ fields populated. If you ever have the need to cancel a subsription, you may either do that at the payment providers merchant website or as follows: Open the Virtual Terminal, select as payment type ‘Recurring Billing’, Cancel_Subscr as txtype and enter the subsription id of the invoice in the field Subs_ID. Then submit. The subscription will be cancelled. October 1, 2014 34 QMerchant Manual When you receive later on a payment by your payment provider, you must manually create a receive payment in QuickBooks or use our QImport software product. To manually create the receive payment, please do the following in QuickBooks. Select the customer and its invoice and open the receive payment dialog. Please select as payment type ‘Recurring Billing’. That ways it prevents QMerchant from opening up the payment dialog again. The dialog looks as shown below. October 1, 2014 35 QMerchant Manual BATCH PROCESSING (‘UNATTENDED MODE’) In case you have authorize.net as payment gateway (others may be implemented later on) you can process a series of payments in unattended mode. By default, the unattended mode is NOT enabled. To make use of it, please open the settings dialog and click the menu ‘Special’. Make sure that ‘Allow Batch Processing’ is checked. When now the green ‘Get Payment’ button is pressed, the layout of the transaction selection dialog is changed. The query for transaction remains unchanged. After the query is done, QMerchant analyzes the transaction data and verifies if the transaction can be processed. That verification depends on the tx-­‐type(AUTH_CAPTURE, AUTH_ONLY etc.) that is used. Valid transactions are marked green and checked. Invalid ones are in red and unchecked. For all tx-­‐types: The transaction must have a credit card number and an expiration date. The amount of the transaction is larger than zero. AUTH_CAPTURE: Valid if the transaction was never charged earlier on. AUTH_ONLY: Valid if the transaction was never charged earlier on. All other tx-­‐types: Valid if the transaction has a transaction id/ authorization code. Regardless of the color marking, you can check the transaction and it will be processed. Hovering the mouse over the first column of the list shows the reason why a transaction is marked green or red. Please review all transaction and check all those transaction that must be processed. The small + and – buttons select all or none. When the review is done, click ‘Process checked transactions’. The unattended mode starts. Same time a red STOP button is displayed that stops the processing. During the processing each transactions is marked if processed suc-­‐
cessful or not. If successful, it is stroked out and marked gray. If the transaction failed, it is marked red. Hover the mouse over the first column of the failed transaction to see the failure reason. Everything else is identical to the single transac-­‐
tion processing. Don’t forget to review the transaction log after the unattended mode is finished. Still, you can process a single transaction as usual. Reminder: When you like to re-­‐process the transaction for what reason ever (like voiding all), please query again, since the listed transaction do NOT reflect the previous processing state. That state is updated in QuickBooks only. October 1, 2014 36 QMerchant Manual BEHAVIOR OF THE GET PAYMENT BUTTON The behavior of QMerchant after you click at the Get Payment button depends on the transaction types you have checked in the settings. QMerchant supports five different transactions types. Sales Receipt Credit Memo Receive Payment Invoice Sales Order The first three (Sales Receipt, Credit Memo, Receive Payment) directly correspond to the respective QuickBooks transac-­‐
tions. When these transaction types are checked and you create one of those transactions, the Get Payment button will query QuickBooks for all those transactions created or modified within the last five minutes. They are displayed in a dia-­‐
log and can be chosen for further processing. The Invoice transaction is mainly used, if you work with recurring billing. Here, the Get Payment button retrieves invoic-­‐
es created or modified within the last five minutes and with Recurring Payment as payment term set. When you then process a transaction with your payment provider, QMerchant automatically creates a receive payment transaction in QuickBooks, so that the invoices is marked PAID in QuickBooks. Most common, only Sales Receipt, Credit Memo, Receive Payment transaction types are checked, because those are the only QuickBooks transaction that are involved in some kind of payment. If you mainly work with invoices, the please un-­‐
check Receive Payment. Otherwise you will see transaction created by QMerchant in the payment selection dialog. The transactions in the list are marked as follows: Clear Text: A credit card transaction not yet processed. Stroked Text: A transaction that is processed. Double click it only if you need to VOID or Refund the transaction. October 1, 2014 37 QMerchant Manual Clear Text with gray background: A transaction submitted in test mode. So, the credit card was never charged. Either reprocess the transaction outside of test mode or remove it in QuickBooks. Italic Text: A transaction where we cannot determine exactly if it was processed or not. Please check the trans-­‐
action log. This may happen only for Split transactions in QuickBooks Point-­‐of-­‐Sale. Query for transactions by date. QuickBooks has two different dates. One is the transaction date, as shown in the date field of the transaction. The other one is the transaction modification date. In the query dialog, we mix both. When you just changed or created a transaction (within the last 15 mins) that one is shown. When you query for a transaction, we look for the modification date of the transaction. When using a Quick-­‐
Books desktop version, you can also query by transaction date. Those are the queries in the lower part of the date selection box. Query for transactions by reference number. You can also seek transactions in QuickBooks by reference number. Please select ‘Enter Reference or Customer’ and enter the reference number of the transaction in the query field, replacing the date selections and click que-­‐
ry. The query is done as follows: QuickBooks Desktop versions: Query for the transaction types as specified in the settings dialog. If the transaction type allows payment methods (i.e. sales receipt), only credit card payment transactions are retrieved. QuickBooks Point-­‐of-­‐Sale: Only sales with a credit card payment are retrieved. Query for transactions by customer name. You can query transactions in QuickBooks by customer name. Please select ‘Enter Reference or Customer’ and enter the customer name in the query field, replacing the date selections and click query. The query is done as follows: QuickBooks Desktop versions: Query for the transaction types as specified in the settings dialog. If the transaction type allows payment methods (i.e. sales receipt), only credit card payment transactions are retrieved. QuickBooks Point-­‐of-­‐Sale: not available. October 1, 2014 38 QMerchant Manual USE QMERCHANT WITH QUICKBOOKS – POINT OF SALE (The outline of the QuickBooks dialogs may vary and be different depending on the QuickBooks version you use). Select QuickBooks – Point of Sale from the QMerchant-­‐Dashboard. The following dialog appears. It may take some time until the next screen with the company data selection comes up. Select your POS data file. It may happen that you will see the setup dialogs as described earlier. After that the QMerchant-­‐Dashboard looks like this: October 1, 2014 39 QMerchant Manual In order to make a sale with QuickBooks – Point of Sale you start with the following screen in QuickBooks – Point of Sale and create a sale: (The following screenshots may differ in various QuickBooks POS versions) Create a sale. After you finished press the ‘Credit’ button for credit card payment and a dialog with the various credit cards comes up.. October 1, 2014 40 QMerchant Manual Choose one of the credit card types and return to the previous screen. Press “Save Only” or Save & Print”. Now you are finished with the QuickBooks part of the payment. Navigate to the QMerchant Dashboard and press “Get Payment” October 1, 2014 41 QMerchant Manual The sale is requested from QuickBooks – Point of Sale and presented as follows: Complete the yellow fields either by swiping a credit card or by entering them manually. Then Press ‘Submit’ to transfer the data to your payment processor. After completion you see a message box with the result. Depending on your QuickBooks – Point of Sale version, QMerchant will add the transaction id and the authorization code to the sales receipt in QuickBooks POS. You also can hardcopy a receipt with the ‘Print’ button. Have in mind; the transaction is recorded in QuickBooks, even if the processing your payment processor fails. So, you are responsible to take corrective actions. If your customer is going to pay the bill with several credit cards, please enter those different payments in QuickBooks Point-­‐of-­‐Sale. QMerchant will automatically create the necessary number of transactions for approval and processing. October 1, 2014 42 QMerchant Manual VOIDS, CREDITS AND REFUNDS QuickBooks Point of Sale has four different transaction types, which will result in a credit card transaction: Sales and Deposit will charge a credit card while Return and Refund will refund a credit card. Normally we will detect these transaction types automatically. We also detect if a Sale is in fact a refund because of exchanged items or. Means, whenever we detect that the total amount is negative, we treat this as a refund. The exception to this is a VOID. If you like to void a transaction, then click at payment screen in QMerchant the link ‘Switch to MANUAL’. Then you are able to make changes in the parameter fields at the bottom of the payment screen. Please enter the transaction id of the transaction to void in the TX-­‐ID field. Select VOID as TX-­‐Type. Then enter the credit card information and press submit. Important Rules: These are the guidelines for issuing a credit from authorize.net. They are similar for other payment providers: This transaction is also referred to as a Refund and indicates to the gateway that money should flow from the merchant to the customer. The gateway will accept a credit or a refund request if the transaction submitted meets the following conditions: •
•
•
•
•
•
The transaction is submitted with the ID of the original transaction against which the credit is being issued (tx_id). The gateway has a record of the original transaction. The original transaction has been settled. If it is not settled (usually the transaction is as of today, please use the VOID function) The sum of the amount submitted in the Credit transaction and all credits submitted against the original transac-­‐
tion is less than the original transaction amount. The full or last four digits of the credit card number submitted with the credit transaction match the full or last four digits of the credit card number used in the original transaction. The transaction is submitted within 120 days of the settlement date and time of the original transaction. In case you subscribed to authorize.net ECC Expanded Credit Capabilities, you can credit any amount to a credit card outside of the rules above. ECC can be enabled at the authorize.net merchant website. October 1, 2014 43 QMerchant Manual QUICK MODE For day to day transactions i.e. sale or sales receipt you can choose in the settings to use the quick mode instead of the full payment view. The window shows as follows and allows you to enter/swipe the credit card information and submit the data to the payment gateway provider.. All buttons have the same functions as in the full payment view. A click at the small button labeled ‘F’ returns you directly to the full payment view. October 1, 2014 44 QMerchant Manual SERVER INSTALLATION AND MANAGEMENT Install QMerchant at a Windows server of your choice. QMerchant is installed for All Users. The installation of QMerchant for a server is identical to the desktop installation. Please configure QMerchant complete-­‐
ly at your first desktop station. The server management is available after QMerchant is activated by a server activation code. During this activation the current profile and all settings are copied to a common place, where all users of QMer-­‐
chant can access those. What is the effect of a server? The normal user can only change the QMerchant settings for some individual parameters as printer or swipe reader. All other settings are disabled. Only the QMerchant administrator can change those settings and make them available to all. After Server activation, from the Support menu, a new entry ‘Server Management’ is shown. With server management a normal user can copy the common QMerchant profile to its individual station. Also, you can log on as Administrator. The login is password protected. The password is always the QMerchant serial number, available from the About dialog. Only the QMerchant administrator can change the QMerchant settings as well as the common profile. The settings are saved automatically. If you would like to make your individual settings available for everybody, use the set profile menu command. QMerchant deactivation. Only the QMerchant administrator can deactivate QMerchant. After login as administrator, the License Management is visible. October 1, 2014 45 QMerchant Manual LEVEL II DATA Some payment providers support Level II transaction data. Level II data are submitted automatically. The following screenshot shows the position of the Level II data. The calculations are as follows: PO_Num is copied from Reference. Tax is calculated Customer ID is generated from Lastname and Firstname Tax Exempt is set if there is a tax amount or not. Regarding duty and freight, the amount transmitted is 0.00. If we detect the items Duty, Freight or Shipping we will transmit the real amount. All fields are editable. If tax is changed, the subtotal is changed. October 1, 2014 46 QMerchant Manual LEVEL III DATA When using business or government purchase card, at least Level 2 data are required as explained above. In addition to that Level 3 is a step to lower the transaction costs. Currently – up to our knowledge – only a few payment gateways have implemented the acceptance of Level 3 data. QMerchant currently supports the transmission of Level 3 data for the PayTrace gateway. You can specify the use of Level 3 in the settings dialog. By default, the Level 3 mode is NOT enabled. To make use of it, please open the settings dialog and click the menu ‘Spe-­‐
cial’. Make sure that ‘Level 3’ is checked. QMerchant transmits the following information to the payment gateway: All Level 2 fields plus Ship-­‐To country Ship-­‐To postal code Additional Tax = 0.00 Additional Tax rate = 0.00 Information for all the line items: ID, Description, Quantity, Unit of Measure as EACH, Unit price, Amount, Addl. Tax as 0.00, Addl. Tax rate as 0.00, Discount as 0.00 October 1, 2014 47 QMerchant Manual CIM (AUTHORIZE.NET CUSTOMER INFORMATION MANAGEMENT) With QMerchant v 5.1.0 we support the usage of authorize.net customer profiles (CIM) to process payments. CIM is not enabled automatically. To enable it, please select from the Information menu Support | Custom Settings. Ac-­‐
cept the message. From the following dialog revert CimEnabled from false to true. Press ok to save the dialog. When you open a payment screen i.e. via the Virtual Terminal you see a new entry CIM in the menu of the payment types. When you select CIM, there is a new group of field below the credit card information. October 1, 2014 48 QMerchant Manual The fields have the following meaning: The first text box is the Customer Profile ID. The second drop down list contains the Customer Payment Profile IDs. Both are necessary in order to use CIM for payment. With the checkbox you can define to use CIM or to use .i.e. a credit card for payment. With the Update Button you can change the credit card information in the CIM payment profile. Add either creates a new customer profile at authorize.net (if not already defined) or adds a new payment profile there. The button with the question mark shows the CIM profile as given in the first text box. You can have as many as ten different payment profiles. If there is more than one profile you have to select which one to use. In addition to the payment profile number we show the last 4 digits of the credit separated by an asterisk. Most times CIM is used with the CIM profile information captured from QuickBooks. We expect that information con-­‐
tained an additional field named Q_CIM, defined at the customer level in QuickBooks. The information in the field is the ProfileID. When QMerchant finds that information we will automatically suggest it for payment. In case that you do not have a CIM Profile, use can use the Add button to create one. If the creation was successful we will automatically transfer it to QuickBooks and store it into the Q_CIM field for later usage. If you have the need to create a large amount of CIM profiles, we recommend the usage of our other tools like QImport. Please contact our help desk. In QuickBooks Point-­‐of-­‐Sale, please define a custom field as follows: From the Preferences menu select Company and then from the list box General and My Field Labels. Name one of the “Customer Custom Fields” Q_CIM and check Use. Leave the dialog with save. Note: QMerchant currently does not allow the use of recurring billing with CIM. October 1, 2014 49 QMerchant Manual USE OF MAGNETIC STRIPE READERS QMerchant supports several Magnetic Card Readers. Most commonly used is the Magtek USB Reader like MagTek 21040101 that we used for testing. Even if they have an USB connector, they operate either as USB HID device or a so called keyboard wedge. You simple can test, which type of card reader you have. Please open the Windows notepad. Place the cursor into the notepad and then swipe a card. If you see the card data in the notepad then you have a keyboard wedge. In the QMer-­‐
chant settings, please select ‘Keyboard’. Otherwise you have an USB reader. Please select the appropriate type. Use of keyboard wedge: When the payment screen opens, the cursor is usually placed in the credit card number field. Now you can swipe the card and the information from the credit card is display in the various fields. You can repeat the swipe as often as you need. Please make sure that if possible your keyboard wedge send a CR after finishing reading. Please consult the stripe reader’s manual. Use of USB card reader: When the payment screen opens, you can swipe the card at any time. If the card is swiped successfully, a green label is shown above the submit button. Whenever you need to swipe the card a second time (i.e. the customer changed its mind), then click that green label. The color of the label becomes yellow and you can swipe the card again. October 1, 2014 50 QMerchant Manual QMERCHANT MENU ENTRIES Tools Settings Opens the settings dialog Backup/Restore Opens a dialog to backup and/or restore the settings and the logfiles. Virtual Terminal Open the Virtual Terminal for transactions outside of QuickBooks Get Transaction from QuickBooks Same function as the ‘Get Payment’ button. Payment Gateway Virtual Terminal Optional menu to navigate to your payment providers Virtual Terminal (available for select-­‐
ed payment providers only. Please contact our helpdesk.) Setup Wizard Re-­‐Initializes all settings for QuickBooks and your payment provider. Currently this is sup-­‐
ported for authorize.net only. Re-­‐Print Receipt Re-­‐Print a transaction receipt. Exit QMerchant End the QMerchant program and disconnect from QuickBooks Information About Opens the About dialog, which display technical information. Help Opens this QMerchant Guide. View Sales log Display the list of sales done. View Application log Display the technical information log file. View Transaction log Display the list of transactions done. View Sales Receipt by ref number QuickBooks Point of Sale only. Retrieve transaction id and authorization code of a transac-­‐
tion referenced by a reference number. Transaction Report Shows a formatted report of the daily transactions Sales Report Shows a formatted report of the daily sales October 1, 2014 51 QMerchant Manual Support Custom Settings Open the custom settings dialog (on advice of the QMerchant support team only) Test MSR Test a magnetic stripe reader or card reader. Show Data Folder Open the folder location, where QMerchant stores its data. Server Management (available in the QMerchant Server version only) Login as Admin Login as administrator for QMerchant server Set User Profile Set profile information for a QMerchant Server user Get User Profile Replace profile information for a QMerchant Server user License Purchase License Purchase you QMerchant license. Activation After purchase you will receive an activation code for QMerchant. Please enter it here. De-­‐Activation In case you are going to use your activation code at a different computer, please deactivate it here first. View License Agreement Read the software license agreement. October 1, 2014 52 QMerchant Manual THE LOG FILE All transactions send to your payment provider are recorded in a daily log file. The log file can be accessed via the Dash-­‐
board. It opens an Internet Explorer with the following content (similar for other payment providers): For PayTrace the log is as follows: October 1, 2014 53 QMerchant Manual TRANSACTION TYPES AND OTHER CODES Most common transaction Types When working with a credit card transaction processor, you can specify several transaction types: AUTH_CAPTURE This is the most common transaction type. It authorizes the transaction amount and captures the money AUTH_ONLY Just authorize the amount. It must get captures later on. CAPTURE_ONLY Captures a previously authorized amount. (Needs the auth-­‐code or transaction id) VOID Cancels an authorization, voids a transaction (Needs the auth-­‐code or transaction id) CREDIT Reimburses the credit card (For authorize.Net only) (Needs the auth-­‐code or transaction id) CREATE_SUBSCR Create a subscription for recurring billing. CANCEL_SUBSCR Cancel a subscription for recurring billing. AVS Codes A = Address (Street) matches, ZIP does not B = Address information not provided for AVS check E = AVS error G = Non-­‐U.S. Card Issuing Bank N = No Match on Address (Street) or ZIP P = AVS not applicable for this transaction R = Retry – System unavailable or timed out S = Service not supported by issuer U = Address information is unavailable W = 9 digit ZIP matches, Address (Street) does not X = Address (Street) and 9 digit ZIP match Y = Address (Street) and 5 digit ZIP match Z = 5 digit ZIP matches, Address (Street) does not Card Code verification Codes M = Match N = No Match P = Not Processed S = should have been present U = Issuer unable to process request October 1, 2014 54 QMerchant Manual PRINT RECEIPT CHANGE THE PRINT RECEIPT The template for print receipt is located in the application data folder and is named printreceipt.xsl. The application data folder can get accessed via the About Dialog with a click at the link ‘Open Application Data Folder’ Open the file printreceipt.xsl with the notepad editor and edit the highlighted lines as follows: Please place your company header information at the place marked yellow. You also can add a footer line at the place marked yellow. If you have to have a new line, please use the following character sequence: &#xd;&#xa;. Do not forget to save the file. <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text" indent="no" omit-­‐xml-­‐declaration="yes"/> <xsl:param name="topMargin" >20</xsl:param> <xsl:param name="leftMargin" >10</xsl:param> <xsl:param name="firstTab" >60</xsl:param> <xsl:param name="barCode" >true</xsl:param> <xsl:param name="barFont" >Free 3 of 9 Extended</xsl:param> <xsl:param name="barSize" >48</xsl:param> <xsl:param name="barReference" >//Reference</xsl:param> <xsl:param name="logoName" >logo.jpg</xsl:param> <xsl:template match="/ | @* | node()"> <xsl:comment>Place your company header below</xsl:comment> <xsl:comment> <![CDATA[<LOGO>]]></xsl:comment> <xsl:text></xsl:text> <xsl:comment>Your Company header in the text above</xsl:comment> <xsl:text>&#xd;&#xa;Receipt&#xd;&#xa;</xsl:text> <xsl:value-­‐of select="Receipt/PaymentType"/> <xsl:text>&#xd;&#xa;Reference:</xsl:text> <xsl:value-­‐of select="Receipt/Reference"/> <xsl:text xml:space="preserve"> </xsl:text> <xsl:value-­‐of select="Receipt/Date"/> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:value-­‐of select="Receipt/Description"/> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:value-­‐of select="Receipt/NameOnCard"/> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:value-­‐of select="Receipt/CardType"/> <xsl:text xml:space="preserve"> **** </xsl:text> October 1, 2014 55 QMerchant Manual <xsl:value-­‐of select="substring(Receipt/CreditCard,string-­‐length(Receipt/CreditCard)-­‐3)"/> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:for-­‐each select="Receipt/Items/SingleItem"> <xsl:value-­‐of select="ItemID"/> <xsl:text>&#09;</xsl:text> <xsl:value-­‐of select="Description"/> <xsl:text>&#09;</xsl:text> <xsl:value-­‐of select="Price"/> <xsl:text>&#09;</xsl:text> <xsl:value-­‐of select="Quantity"/> <xsl:text>&#09;</xsl:text> <xsl:value-­‐of select="Total"/> <xsl:text> </xsl:text> </xsl:for-­‐each> <xsl:text> </xsl:text> <xsl:text xml:space="preserve">Subtotal:&#09;</xsl:text> <xsl:value-­‐of select="Receipt/Subtotal"/> <xsl:text xml:space="preserve">&#xd;&#xa;Tax:&#09;</xsl:text> <xsl:value-­‐of select="Receipt/Tax"/> <xsl:text xml:space="preserve">&#xd;&#xa;Total:&#09;</xsl:text> <xsl:value-­‐of select="Receipt/Total"/> <xsl:text>&#xd;&#xa;&#xd;&#xa;</xsl:text> <xsl:if test="Receipt/PaymentType='RECURRING BILLING'"> <xsl:text>Recurring Billing&#xd;&#xa;</xsl:text> <xsl:text xml:space="preserve">Rate:&#09;</xsl:text> <xsl:value-­‐of select="Receipt/ARBRate"/> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:text xml:space="preserve">Start:&#09;</xsl:text> <xsl:value-­‐of select="Receipt/ARBStart"/> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:text xml:space="preserve">Interval:&#09;</xsl:text> <xsl:value-­‐of select="Receipt/ARBIntv"/> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:text xml:space="preserve">Times:&#09;</xsl:text> <xsl:value-­‐of select="Receipt/ARBMaxOccurrence"/> <xsl:text>&#xd;&#xa;</xsl:text> </xsl:if> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:value-­‐of select="Receipt/Processor"/> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:value-­‐of select="Receipt/TxType"/> <xsl:text xml:space="preserve">&#xd;&#xa;AuthCode:&#09;</xsl:text> <xsl:value-­‐of select="Receipt/Authorization"/> <xsl:text xml:space="preserve">&#xd;&#xa;Transaction-­‐ID:&#09;</xsl:text> <xsl:value-­‐of select="Receipt/TransactionID"/> <xsl:text>&#xd;&#xa;</xsl:text> <xsl:text>&#xd;&#xa;&#xd;&#xa;&#xd;&#xa;&#xd;&#xa;................................................</xsl
:text> <xsl:text>&#xd;&#xa;Signature&#xd;&#xa;&#xd;&#xa;</xsl:text> <xsl:comment> <![CDATA[<BARCODE>]]></xsl:comment> <xsl:comment>Place your company footer below</xsl:comment> <xsl:text></xsl:text> <xsl:comment>Your Company footer in the text above</xsl:comment> <xsl:comment><![CDATA[<PAGEBREAK>]]></xsl:comment> <xsl:comment>Possibly another page</xsl:comment> </xsl:template> </xsl:stylesheet> October 1, 2014 56 QMerchant Manual BARCODE PRINTING By default barcode printing is switched off. To enable it, please do the following: 1. Change the barCode parameter in the printreceipt.xsl file to “true” (It is marked blue in the listing above) 2. Printing is done by a special font. It is named “Free 3 of 9 extended”. This font is delivered with each QMerchant distribution, but not installed automatically. Please go to the same location where the printreceipt.xsl file is and double-­‐click the file FRE3OF9X.tff. This will install the font. 3. By default the reference number of the transaction is barcoded. 4. To change the barcode size, the information to barcode or the font type, please change the appropriate parame-­‐
ters in the printreceipt.xsl file or contact addQin support. 5. Don’t forget to save the printreceipt.xsl file. RECEIPT FORMATTING PARAMETERS AND COMMANDS Parameters: topMargin leftMargin firstTab barCode barSize barFont barReference logoName Position from the top of the page in points (Default: 20) Position from the left in points (Default: 10) Position of the first tab in poits (Default: 60) Print a bar code (Default: false) Height of the barcode in points (Default: 48) Font used for barcode printing (Default: 3 Free Of 9 Extended) Content of the barcode (Default: Reference number) Name of the logo file (Default: logo.jpg) Commands: <![CDATA[<BARCODE>]]> <![CDATA [<PAGEBREAK>]]> <![CDATA [<LOGO>]]> Placeholder for the barcode position Continue printing at a new page Placeholder for logo at the top of the receipt Special Characters: &#xd;&#xa; &#09; Newline(Line feed and carriage return) Tab character October 1, 2014 57 QMerchant Manual RE-­‐PRINT A RECEIPT. Choose this function, if you need an old print receipt or in case you forgot to print the current receipt. Select the date of the transaction. Then enter one of the following: •
•
•
•
transaction id authorization code amount of the transaction or reference If you do not know one of those values, please open from the Reports menu the sales report and checkout the transac-­‐
tion id. Afterwards you will see the print dialog and/or you can print the receipt. October 1, 2014 58 QMerchant Manual CUSTOM SETTINGS These settings control in some aspects how QMerchant behaves. Please change those settings on advice by our support team only, since wrong settings seriously influence the way QMerchant operates. The description of the settings is as follows: Name Default Comment AcceptPendingTransactions False When set to true pending transactions from QuickBooks are also selected for payment. By default those are ignored. allowShortCuts False AlternateTxType AlwaysShowTxDialog True Allows shortcuts in the payment window. Implemented shortcuts are: Alt-­‐C = Close Window Alt-­‐S = Submit Transaction Alt-­‐P = Print Receipt Valid transaction type as alternate to the defaults. I.e. AUTH_ONLY instead of AUTH_CAPTURE. Always show a select transaction dialog. If set to False, the dialog is suppressed if only one transaction is available. AppDirectory Location of application data folder. ARForPayment AR-­‐Account name in QuickBooks (without the numbers) where to place the received payment. By default it is placed into ‘Ac-­‐
counts Receivable’. AutoApplyRPayment True Applies an automatic receive payment automatically by Quick-­‐
Books if the payment cannot be applied to the original invoice October 1, 2014 59 QMerchant Manual transaction. autoClosePayment False Automatically close the payment dialog after a successful trans-­‐
action. autoCloseTxDialog False Automatically close the transaction selection dialog. AutoPrint Automatically (Auto) print a receipt after a successful transac-­‐
tion. CCExpDateFieldName CCExpDate Name of custom field that contains the credit card expiration date ccFormLocation 150,150 Screen location of the payment form CCNumberFieldName CCNumber Name of custom field that contains the credit card number. De-­‐
fault is the use of the account number of the customer payment info. CheckFields True Check the field for plausibility before submitting a transactions CIMEnabled False If set to true uses authorize.net CIM for payments. CIMValidate none Validation code for CIM transactions ColorTransactions True Show green color if transaction has valid credit card credentials. CountryList Comma separated list of countries placed before the common list. We recommend that you also add the country ISO code. The syntax is a follows: USA;US, Canada;CA … First comes the name you like to see in the list and then separat-­‐
ed by semicolon the two character ISO code. Name of the QuickBooks additional field that holds the custom-­‐
er’s bank account number. Name of the QuickBooks additional field that holds the custom-­‐
er’s bank name. Name of the QuickBooks additional field that holds the custom-­‐
er’s bank routing number (ABA). Record all messages to and from QuickBooks. CustBankAccount BankAccount CustBankName BankName CustBankRouting BankRouting Debug False DefaultTxType AUTH_CAPTURE Default Transaction type. Usually AUTH_CAPTURE. DepositPaymentTo October 1, 2014 Deposit-­‐Account name in QuickBooks (without the numbers) where to place the received payment. By default it is placed into ‘Undeposited Funds’. 60 QMerchant Manual DutyItemNames Duty List of the names of the QuickBooks items specifying duties. This is used to specify a shipment amount to the payment gateway. EditMode False Make item list and amounts editable. EnableBatch False Allows the simultaneous processing of multiple credit card charges forceCCV False Force the entry of the card’s CCV code ForceQBXMLVersion False Internal use only. forceZip False Force the entry of a ZIP code in the customer billing area getCCfromParent False Get credit card information from the parent customer in case there is no information at the job. hideWinControlBox False Hide Windows Controlboxes IgnoreQBDSubtotal False Ignores in the item lines an item that contains ‘Subtotal’ in its name. ignoreReversed True Point-­‐of-­‐Sale only. Don’t show revered transactions. InstalledVersion n/a Internal use only. InvoiceFilterbyTerm Place the name of the term in case you like to filter invoices by term. This field is case sensitive. If you want to switch off this filter, remove replace the entry with blanks. Itemized False If true sends itemized transactions to authorize.net. For PayTrace it sends Level 3 information to the payment gateway. L3 False Enable Level 3 transactions for PayTrace and SecureNet L3SourceZip Zip code of the merchant for Level 3 processing LicenseRead Internal use only. mainFormLocation 100,100 Screen location of the main form. MaskCCNumber True Masks credit card and bank account numbers in reports. MaxReturnedQueryResults 50 ModifiedMinutesBack1 2 Number of returned results for a query against QB. Number of minutes searched back by the ‘Get Payment’ button ModifiedMinutesBack2 15 Alternate number of minutes searched back by the ‘Get Pay-­‐
ment’ button MSR Name of MSR type (Keyboard, COM, USB) October 1, 2014 61 QMerchant Manual MsrASynch True Use Magnetic Card Reader to asynchronous mode . MSRClose True MsrOverlap False MsrTimeout 30000 Timeout for synchronous MSR operations multipleMerchantAccounts False Support of multiple merchant accounts. PrintCopies 1 Number of print receipt copies Printer Name of receipt printer PrintPreview False Show preview before printing QBDLaunchMode 1 QuickBooks connection mode. QBPOSConnection Sets the Point-­‐of-­‐Sale server to a specific database. The must be as shown in the following sample: Computer Name=QUAD;Company Data=Test POS;Version=10 QBVersion n/a Internal use only. QBXMLVersion “2.0” Minimum QuickBooks version QuickMode False Show abbreviated payment screen. RefundForLinkedTransactionsOnly True Query credit memos and refund for previous credit card transac-­‐
tions only. RemoveItemAfterProcess True sc_Close C Removes a successfully processed transaction from the transac-­‐
tion selection dialog. Close a window (Alt-­‐C) sc_GetPayment G Open the payment dialog (Alt-­‐G) sc_GlobalGetPayment G Global shortcut to open the payment screen. (Alt-­‐G) sc_Process P Open the payment screen for the selected transaction (Alt-­‐P) sc_ReceiptPrint R Print the receipt (Alt-­‐R) S Submit the transaction (Alt-­‐S) selSrFormLocation 120,120 Screen location to transaction selection form SendEmailReceipt False If supported by the payment gateway, automatically send an email receipt. Currently only authorize.net and PayTrace are supported. sc_SubmitTx October 1, 2014 62 QMerchant Manual SetPaymentMethodForRP False Set a payment method for new receive payments in QuickBooks. Otherwise a payment method is ignored. ShipItemNames Shipping,Freight List of the names of the QuickBooks items specifying shipment. This is used to specify a shipment amount to the payment gate-­‐
way. shouldUpdate True Internal use only ShowBackToQBBtn False If set to true the ‘Back to QuickBooks’ button is always shown. Otherwise QMerchant controls the appearance of this button ShowInTaskbar True Set to False if QMerchant shall show up in the icon tray only, if minimized. ShowProcessedTxAlso True If true, shows all processed transactions also. TxConfirmationMsg False Confirmation Message before a transaction is processed. Trace False Records complete messages between QMerchant and the pay-­‐
ment provider. UpdateAppliedToTxn False Propagate the transaction id and authorization code to linked transactions in QB. UseSaveMemory True Release Unused Memory. UseTrack 0 Magnetic track to use. (0 = automatically selected) UseTxInfo False vPosUrl Uses in addition to POS flag the txinfo.db3 database to filter pro-­‐
cessed transactions. POS only. The url for the payment gateway web-­‐based virtual terminal (.i.e. for authorize.net https://anet.vpos.authorize.net/). Please con-­‐
sult your payment gateway provider. October 1, 2014 63 QMerchant Manual REPORTS Transaction Report Sales Report October 1, 2014 64 QMerchant Manual ACTIVATION When you first start QMerchant, it works automatically in Test Mode. This allows you to play around with the software and become familiar. The only limitation in contrast to the activated product is that the maximum amount you can charge is limited to 5.00. To switch to production mode you have to purchase QMerchant from http://www.addqin.com/QMerchant. After pur-­‐
chase you will receive an activation code. This code is displayed after purchase and is also send to your email address. To activate, please select in QMerchant from the menu bar Information, License and then Activation. In the dialog, copy and paste the activation code and press ok. After the activation process finished QMerchant re-­‐
starts. Then open the settings dialog and un-­‐check the test mode check box. Leave the settings dialog with save. If you would like to use QMerchant at a different computer, you can de-­‐activate the activation code and activate it at the other computer again. You also can reset your activation at the helpdesk at http://www.addqin.com/QMerchant October 1, 2014 65 QMerchant Manual PAYMENT GATEWAYS QMerchant has implemented the following payment gateway functionality. If functionality is missing or not implement-­‐
ed does not mean that the payment gateways does not offer it. PayTrace This is the typical sale. Authorize the card and capture the amount PPI Paymover Auth_Capture Authorize.net Function ! ! ! Capture Only ! ! ! Auth Only ! ! ! Void ! ! ! Credit ! ! ! Force_Auth " ! " Force_Sale " ! " Prior Auth Capture ! " " Pin Debit " ! " Query " ! " eCheck ! ! ! Recurring Billing ! " " Customer Information Management ! " " Level 2 transactions ! ! ! Level 3 transactions " " ! Capture the amount after as prior authorization Authorize the amount and capture later Void a transaction that is not settled Issue a refund Force an authorization Force an authorization and a capture Capture the amount after as prior authorization Authorize and capture the amount using a Pin based Debit Card Query the state of a transaction Process checks electronically Use the payment gateways recurring billing Use the payment gateways customer management system Submit transactions a Level 2 transactions for better rates Submit transactions a Level 3 transactions for better rates October 1, 2014 66 QMerchant Manual AUTHORIZE.NET API LOGIN ID AND TRANSACTION KEY Please log-­‐in to your merchant account administration at the authorize.net website. Then navigate to Settings and then General Security Settings. Choose ‘API Login ID and Transaction Key’. Your API Login ID and Transaction Key are unique pieces of information specifically associated with your payment gate-­‐
way account. However, the API Login ID and Transaction Key are NOT used for logging into the Merchant Interface. The-­‐
se two values are only required when setting up an Internet connection between your e-­‐commerce Web site and the payment gateway. They are used by the payment gateway to authenticate that you are authorized to submit Web site transactions. Transactions that cannot be authenticated by the payment gateway using these values are rejected. IMPORTANT: The API Login ID and Transaction Key protect your payment gateway account from unauthorized use and should not be shared with anyone. Be sure to store these values securely on a server separate from your Web server and change the Transaction Key regularly to further strengthen the security of your account. To create an API Login ID or Transaction Key for the first time: Step 1: Type in your Secret Answer. You should have configured a Secret Question and Secret Answer during ac-­‐
count activation. Step 2: Click Submit to continue or click Cancel to cancel the action. The API Login ID and Transaction Key gen-­‐
erated for your payment gateway account appear. Once you have initially created your API Login ID, you may not change it in the Merchant Interface. To change your API Login ID, please contact Authorize.Net Customer Support. IMPORTANT: The API Login ID is different than your user login ID. Your user login ID allows you to log into your Mer-­‐
chant Interface user account. The API Login ID grants a merchant access to submit transactions to the payment gate-­‐
way. You may obtain a new, unique Transaction Key on this page as often as needed. To obtain a new transaction key: Step 1: Enter your Secret Answer (the answer to your Secret Question configured at account setup). Step 2: To disable the old transaction key, click the check box labeled Disable Old Transaction Key. Note: If the Disable Old Transaction Key check box is not selected, the old transaction key will automatically ex-­‐
pire in 24 hours. Step 3: Click Submit to continue or click Cancel to cancel the action. Your new transaction key is displayed. October 1, 2014 67 QMerchant Manual TIPS TEST YOUR CONNECTION TO THE PAYMENT PROVIDER: Start QMerchant and make sure that you have your payment provider selected in the settings dialog. Make sure that the test mode is checked. Then from the Tools menu select ‘Virtual Terminal’. Fill in a total amount; enter some digits as credit card number. Add the expiration date and press ‘Submit’. If you can connect to your payment provider then you will receive an error message, that either your account is invalid or the credit card number is wrong or so. This proves that you correctly can connect to the payment provider and submit transactions. GET THE QMERCHANT VERSION AND SERIAL NUMBER From the QMerchant menu bar select Information and then About. In the About dialog click the Details button. October 1, 2014 68 QMerchant Manual TROUBLESHOOT Prerequisites Current Prerequisites are: •
•
•
•
Windows XP, Windows Vista, Windows 7, Windows 8 Microsoft .Net Framework 4.0, QuickBooks 2004 -­‐ 2015 Pro, Premiere, Enterprise US or CA version or QuickBooks Point of Sale A valid merchant payment provider account. How d o I g et the transaction k ey from A uthorize.Net? Open your web browser and navigate to http://www.authorize.net. Login into your account and go to the Account Settings. In the section ‘Security Settings’ is a link to the transaction key. Follow that link and acquire the transaction key. I s ee the following m essage from A uthorize.Net The login and password information you specified is not correct. You will first need to log into your Authorize.Net account and go to Settings > API Login ID and Transaction Key. There you will acquire your API Login and your Transaction Key. Simply replace the login and transaction key within QMerchant with your API Login and Transaction Key. Supported P ayment G ateways: Authorize.Net http://www.authorize.net PayTrace http://www.paytrace.com PPI Paymover http://www.ppipaymover.com If you have a different payment provider, please contact our helpdesk. How c an I s ee the a uthorization a nd transaction id o f a s ales receipt? In QuickBooks Desktop versions, we added a custom field Q_Authorization. Please add this to your sales receipt layout in QuickBooks. October 1, 2014 69 QMerchant Manual In QuickBooks Point of sale, please use the sales history to get the reference number of the sale. Then open the menu item ‘View sales receipt by refnumber’ from the information menu and enter the reference number. The required information is displayed. Cannot g et the c redit c ard n umber from Q uickBooks The cc number is shown as ******… only. Intuit does not allow any longer retrieving the credit card numbers stored in QuickBooks in an un-­‐masked format. So, when we retrieve that number, it is shown in our payment di-­‐
alog masked, practically unusable. To use this number again, you either have to re-­‐type it or copy and paste it from QuickBooks. To solve this problem you can store the credit card number at another place or in a custom field with the cus-­‐
tomer in QuickBooks. That way you can overcome this restriction. It is a one-­‐time copy and paste process. 1. You can use the Account No. field of the customer payment info. In the QMerchant custom settings please enter as value in the CCNumberFieldName the expression //CustomerRet/AccountNumber. This is the de-­‐
fault. We recommend this because you still have all payment information in QuickBooks at the same tab. 2. Use an additional or custom field: Create for your customer an additional or custom field named i.e. CCNumber. You have to define it only once. It is automatically propagated to all customers. Then copy and paste the credit card number from the customer payment info into the new field. Leave everything else like exp date etc. at the QuickBooks payment info. Then in QMerchant select from the 'Information' menu 'Support' and then 'Custom Settings'. OK the message box. In the following dialog, there is a field named CCNumberFieldName. Click in the column right off that name and enter CCNumber (the name of your custom field from above). Click ok to save it. Now QMerchant will grab the credit card number from that custom field. QuickBooks D esktop V ersions i.e. E nterprise a nd W indows 7 I cannot connect to QuickBooks. Typically this is a problem with newer QuickBooks version and Windows ac-­‐
count control. Intuit recommends the following: Please open in Windows the Control Panel and search for UAC. It is location in the Action Center. Click Change User Account Control and scroll the slider down to never notify. Close the dialog with OK. Close all control panel dialogs. Also close all QMerchant windows. Then restart QMer-­‐
chant and try to connect again to QuickBooks. Q UICKB OOKS P OINT-­‐OF-­‐S ALE V ERSIONS I cannot connect to QuickBooks POS. This may happen with older QuickBooks POS versions. Please download and install the QBMXL POS Runtime, which allows the access to QuickBooks POS from the following link: http://www.addqin.com/download/QBPOSSDKRuntimeInstaller.exe How c an I d isable the integrated Q uickBooks m erchant s ervice? QuickBooks POS v. 10 and below: In the Company Preferences | Merchant and Gift Services, please remove the Merchant Number. Newer QuickBooks POS versions: October 1, 2014 70 QMerchant Manual Choose File > Setup Interview. Click the Payments tab. Select No and then click Done. Other QuickBooks versions (Pro, Premiere, Enterprise): Make sure the checkbox 'Process ... credit card pay-­‐
ment' is unchecked all the time when you save a sales receipt, a receive payment or a credit memo. Error m essage ‘Market type is invalid. I am trying to use QMerchant with Authorize.net for payment. when I process the payment I get AN error mes-­‐
sage it says ‘Market type is invalid’.Authorize.net has two types of accounts: CP = Card Present or CNP = Card not Present. Depending on the type of the account you must in the QMerchant settings check or uncheck the Checkbox ‘CPAccount’. CPAccount Check = CP, CPAccount uncheck = CNP. Please reverse the state of the check box. I w ant to c hange the Q uickBooks v ersion I s elected d uring installation. During Installation you can select between None, QuickBooks Point of Sale and QuickBooks Pro, Premiere or En-­‐
terprise. To reverse this decision, please do the following: Start QMerchant. From the Tools menu select Setup Wizard and follow the instructions. If you have any questions or experience other problems, please visit our helpdesk at http://www.addqin.com October 1, 2014 71 QMerchant Manual APPENDIX A: SCREENSHOTS FOR THE USE WITH QUICKBOOKS POINT-­‐OF-­‐SALE (OLDER VERSIONS) Create a sale. After you finished press the ‘Take Payment’ button. Select Credit Card as Payment. A dialog to select the Credit Card type appears. Make the appropriate selection. October 1, 2014 72 QMerchant Manual Choose the payment type and return to the previous screen. Press “Save Only” or Save & Print”. Now you are finished with the QuickBooks part of the payment. Navigate to the QMerchant Dashboard and press “Get Payment” October 1, 2014 73 QMerchant Manual The sales receipt is requested from QuickBooks – Point of Sale and presented as follows: Complete the yellow fields either by swiping a credit card or by entering them manually. Then Press ‘Submit’ to transfer the data to your payment processor. After completion you see a message box with the result. Depending on your QuickBooks – Point of Sale version, QMerchant will add the transaction id and the authorization code to the sales receipt in QuickBooks POS. You also can hardcopy a receipt with the ‘Print’ button. Have in mind, the transaction is recorded in QuickBooks, even if the processing your payment processor fails. So, you are responsible to take corrective actions. October 1, 2014 74 QMerchant Manual APPENDIX B: AUTHORIZE.NET RESPONSE CODES (EXCERPT FROM AUTHORIZE.NET DOCUMENTATION) 2 2 This transaction has been declined. 2 3 This transaction has been declined. This code indicates a referral response. 2 4 This transaction has been declined. The code returned from the processor indicating that the card used needs to be picked up. 3 5 A valid amount is required. The value submitted in the amount field did not pass validation for a number. 3 6 The credit card number is invalid. 3 7 The credit card expiration date is invalid. The format of the date submitted was incorrect. 3 8 The credit card has expired. 3 11 A duplicate transaction has been submitted. A transaction with identical amount and credit card infor-­‐
mation was submitted two minutes prior. 3 12 An authorization code is required but not present. 3 13 The merchant Login ID is invalid or the account is inactive. 3 15 The transaction ID is invalid. The transaction ID value is non-­‐numeric or was not present for a transaction that requires it (i.e., VOID, PRIOR_AUTH_CAPTURE, and CREDIT). 3 16 The transaction was not found. The transaction ID sent in was properly formatted but the gateway had no record of the transaction. 3 17 The merchant does not accept this type of credit card. The merchant was not configured to accept the cred-­‐
it card submitted in the transaction. 3 19 An error occurred during processing. Please try again in 5 minutes. 3 20 An error occurred during processing. Please try again in 5 minutes. 3 21 An error occurred during processing. Please try again in 5 minutes. 3 22 An error occurred during processing. Please try again in 5 minutes. 3 23 An error occurred during processing. Please try again in 5 minutes. 3 25 An error occurred during processing. Please try again in 5 minutes. 3 26 An error occurred during processing. Please try again in 5 minutes. 2 27 The transaction resulted in an AVS mismatch. The address provided does not match billing address of card-­‐
holder. 3 28 The merchant does not accept this type of credit card. The Merchant ID at the processor was not config-­‐
ured to accept this card type. 3 30 The configuration with the processor is invalid. Call Merchant Service Provider. 3 33 FIELD cannot be left blank. The word FIELD will be replaced by an actual field name. This error indicates that a field the merchant specified as required was not filled in. 3 34 The VITAL identification numbers are incorrect. Call Merchant Service Provider. The merchant was incor-­‐
rectly set up at the processor. 3 35 An error occurred during processing. Call Merchant Service Provider. The merchant was incorrectly set up at the processor. 3 36 The authorization was approved, but settlement failed. 3 37 The credit card number is invalid. 3 39 The supplied currency code is either invalid, not supported, not allowed for this merchant or doesn’t have an exchange rate. 3 40 This transaction must be encrypted. 3 47 The amount requested for settlement may not be greater than the original amount authorized. This occurs if the merchant tries to capture funds greater than the amount of the original authorization-­‐only transaction. 3 48 This processor does not accept partial reversals. The merchant attempted to settle for less than the origi-­‐
nally authorized amount. 3 49 A transaction amount greater than $99,999 will not be accepted. October 1, 2014 75 QMerchant Manual 3 50 This transaction is awaiting settlement and cannot be refunded. Credits or refunds may only be performed against settled transactions. The transaction against which the credit/refund was submitted has not been set-­‐
tled, so a credit cannot be issued. 3 51 The sum of all credits against this transaction is greater than the original transaction amount. 3 52 The transaction was authorized, but the client could not be notified; the transaction will not be settled. 3 54 The referenced transaction does not meet the criteria for issuing a credit. 3 55 The sum of credits against the referenced transaction would exceed the original debit amount. The transac-­‐
tion is rejected if the sum of this credit and prior credits exceeds the original debit amount. 3 57 An error occurred in processing. Please try again in 5 minutes. 3 58 An error occurred in processing. Please try again in 5 minutes. 3 59 An error occurred in processing. Please try again in 5 minutes. 3 60 An error occurred in processing. Please try again in 5 minutes. 3 61 An error occurred in processing. Please try again in 5 minutes. 3 62 An error occurred in processing. Please try again in 5 minutes. 3 63 An error occurred in processing. Please try again in 5 minutes. 3 66 This transaction cannot be accepted for processing. The transaction did not meet gateway security guide-­‐
lines. 3 68 The version parameter is invalid. The value submitted in x_cpversion was invalid. 3 69 The transaction type is invalid. The value submitted in x_type was invalid. 3 70 The transaction method is invalid. The value submitted in x_method was invalid. 3 72 The authorization code is invalid. The value submitted in x_auth_code was more than six characters in length. 3 74 The duty amount is invalid. The value submitted in x_duty failed format validation. 3 75 The freight amount is invalid. The value submitted in x_freight failed format validation. 3 76 The tax amount is invalid. The value submitted in x_tax failed format validation. 3 78 The Card Code (CVV2/CVC2/CID) is invalid. The value submitted in x_card_code failed format validation. 3 84 The device type is invalid. The value submitted in x_device_type did not match the configured value. 3 85 The market type is invalid. The value submitted in x_market_type did not match the configured value. 3 86 The response format is invalid. The value submitted in x_response_format was not equal to “0” or “1.” 3 87 This market type is not supported. 3 88 The Track1 data is invalid. 3 89 The Track2 data is invalid. 3 90 ACH transactions cannot be processed. ACH transactions cannot be processed by the card-­‐present system. 3 103 This transaction cannot be accepted. A valid fingerprint, transaction key, or password is required for this transaction. 3 111 A valid billing country is required. This code is applicable to Wells Fargo SecureSourceSM merchants only. 3 112 A valid billing state/province is This code is applicable to Wells Fargo required. SecureSourceSM mer-­‐
chants only. 3 120 An error occurred during processing. Please try again. The system-­‐generated void for the original timedout transaction failed. (The original transaction timed out while waiting for a response from the authorizer.) 3 121 An error occurred during processing. Please try again. The system-­‐generated void for the original errored transaction failed. (The original transaction experienced a database error.) 3 122 An error occurred during processing. Please try again. The system-­‐generated void for the original errored transaction failed. (The original transaction experienced a processing error.) 3 123 This account has not been given the permission(s) required for this request. The transaction request must include the API Login ID associated with the payment gateway account. 2 127 The transaction resulted in an AVS mismatch. The address provided does not match billing address of cardholder. The system-­‐generated void for the original AVSrejected transaction failed. 3 128 This transaction cannot be processed. The customer’s financial institution does not currently allow trans-­‐
actions for this account. October 1, 2014 76 QMerchant Manual 2 141 This transaction has been declined. The system-­‐generated void for the original FraudScreen-­‐rejected transaction failed. 2 145 This transaction has been declined. The system-­‐generated void for the original card code-­‐rejected and AVS-­‐rejected transaction failed. 3 152 The transaction was authorized, but the client could not be notified; the transaction will not be settled. The system-­‐generated void for the original transaction failed. The response for the original transaction could not be communicated to the client. 2 165 This transaction has been declined. The system-­‐generated void for the original card code-­‐rejected transac-­‐
tion failed. 3 170 An error occurred during processing. Please contact the merchant. Concord EFS – Provisioning at the pro-­‐
cessor has not been completed. 3 171 An error occurred during processing. Please contact the merchant. Concord EFS – This request is invalid. 3 172 An error occurred during processing. Please contact the merchant. Concord EFS – The store ID is invalid. 3 173 An error occurred during processing. Please contact the merchant. Concord EFS – The store key is invalid. 3 174 The transaction type is invalid. Please contact the merchant. Concord EFS – This transaction type is not ac-­‐
cepted by the processor. 3 175 The processor does not allow voiding of credits. Concord EFS – This transaction is not allowed. The Con-­‐
cord EFS processing platform does not support voiding credit transactions. Please debit the credit card instead of voiding the credit. 3 180 An error occurred during processing. Please try again. The processor response format is invalid. 3 181 An error occurred during processing. Please try again. The system-­‐generated void for the original invalid transaction failed. (The original transaction included an invalid processor response format.) 3 185 This transaction cannot be processed. Merchant is not configured for VPOS. 2 201 This transaction has been declined. The expiration date is invalid. This error code applies only to mer-­‐
chants on FDC Omaha. 2 202 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The transac-­‐
tion type is invalid. 2 203 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The value submitted in the amount field is invalid. 2 204 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The de-­‐
partment code is invalid. 2 205 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The value submitted in the merchant number field is invalid. 2 206 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The mer-­‐
chant is not on file. 2 207 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The mer-­‐
chant account is closed. 2 208 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The mer-­‐
chant is not on file. 2 209 This transaction has been declined. This error code applies only to merchants on FDC Omaha. Communica-­‐
tion with the processor could not be established. 2 210 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The mer-­‐
chant type is incorrect. 2 211 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The card-­‐
holder is not on file. 2 212 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The bank configuration is not on file 2 213 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The mer-­‐
chant assessment code is incorrect. 2 214 This transaction has been declined. This error code applies only to merchants on FDC Omaha. This func-­‐
tion is currently unavailable. October 1, 2014 77 QMerchant Manual 2 215 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The en-­‐
crypted PIN field format is invalid. 2 216 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The ATM term ID is invalid. 2 217 This transaction has been declined. This error code applies only to merchants on FDC Omaha. This transac-­‐
tion experienced a general message format problem. 2 218 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The PIN block format or PIN availability value is invalid. 2 219 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The ETC void is unmatched. 2 220 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The primary CPU is not available. 2 221 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The SE number is invalid. 2 222 This transaction has been declined. This error code applies only to merchants on FDC Omaha. Duplicate auth request (from INAS). 2 223 This transaction has been declined. This error code applies only to merchants on FDC Omaha. This transac-­‐
tion experienced an unspecified error. 2 224 This transaction has been declined. This error code applies only to merchants on FDC Omaha. Please re-­‐
enter the transaction. October 1, 2014 
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement