Credit Card Processing User Guide Release 5.4

Transcription

1 Credit Card Processing User Guide Release 5.4

2

3 Copyright 1996, 2002, 2004, 2008 by Business Property VORMITTAG ASSOCIATES, INC. Business Information/Authorized Use All rights reserved. is the sole owner of this manual. Information in this manual is subject to change without notice. No part of this publication may be reproduced in any form, by any means, electronic or mechanical, including photocopying, recording or by any other information storage and retrieval system, or distributed without prior written authorization of an executive officer of While every precaution has been taken in the preparation of this manual, assumes no responsibility for errors or omissions. This software is designed for use with the IBM i family operating system and the IBM Power Systems TM server. IBM i family operating system and IBM Power Systems TM are registered trademarks of International Business Machines Corporation (IBM ). Authorized Possession and Use 1. Who May Use - Only licensees and current employees of may possess and use this manual. 2. Purpose of Use - This manual may only be used in connection with or in support of licensees, authorized users, or the company's internal use. Penalties for Unauthorized Possession, Copying or Use Any person or organization possessing, copying, or using this manual in violation of the authorized possession and use provision above will be subject to civil and criminal prosecution. Credits Editor Elaine Cereola, Director of Documentation Services Technical Writers Elaine Cereola, Director of Documentation Services Al Sheremeta, Technical Writer Susan Licata, Technical Writer Richard Schreiber, Director of Quality/Training Manager Additional technical information provided by Larry Murphy Vice President of Research & Development, Gary Unger Development Engineer, Kevin Dick Development Engineer, Purnadip Mukherjee Programmer/Analyst (3 rd Party Integration), Rajeev Naidu Programmer/Analyst, Beth Steadman Administrations Manager: Help Desk Support, Richard Schreiber Director of Quality/Training Manager, Bob Moloney Programmer/Analyst (EDI Segment) and the Programming Staff of VAI. The Organization Robert Vormittag, President Russ Cereola, Vice President Robert Giustino, Vice President of Operations Larry Murphy, Vice President of Research & Development Joe Scioscia, Vice President of Marketing Publication Date February 21, 2013

4 About Documentation S2K Enterprise user guides have been designed to provide the user with a quick look at some of the important features of the S2K Enterprise Management solution. Geared to the end user, they provide the information needed to perform the day-to-day operational tasks of an organization. Our goal in creating user guides is to take the user, step by step, through the processes that will make them successful S2K Enterprise users. S2K Enterprise documentation, including but not limited to, manuals, user guides, workbooks, online help text, and documentation posted at is written in accordance with the S2K Enterprise Software base package. Custom modifications required for individual S2K Enterprise users will not be reflected in S2K Enterprise documentation unless the modification has been incorporated into the S2K Enterprise Software base package. Illustrations, screen captures, flowcharts, report samples, worksheets, etc. are for illustrative purposes only and may not reflect the software version currently in use by individual users. If you are unable to find the answers you need from this manual, feel free to call VAIs technical support hotline at or VAI.4HELP.

5 Table of Contents Overview... 1 Process... 1 Authorization Information... 1 Re-Authorizing... 1 Pick Ticket Process... 1 Invoicing... 2 Split Order Processing... 2 Calculation for Split Order Processing Amount... 2 Calculation for Backorder Re-Authorization Amount... 2 Credit Card Data Purge... 2 Cross Applications Interface Set Up... 3 Customer Orders Interface... 4 Credit Card Interface... 5 S2K Enterprise Cross Applications Interfaces RiTA Server Menu Client ID Maintenance Pre Settlement Report Settlement Manager Detail Report Batch Details VeriSign Merchant Specific User Profile File Maintenance Tables Payment Types Credit Card Type Retail VeriSign Documentation Systems Requirement Configuration Management VeriSign Interface (VERSGNINT) VeriSign Setup (VERSETUP) VeriSign Batch Engine (VERSGNENG) PFProJava (Java Servlet) VeriSign Settlement (VERSPORT) End VeriSign (VERSENDGEN) VeriSign Settlement (VERSPO1) Layout Response DTAQ (@CR+job#) Layout Regular Order Flow Order Entry Invoicing Final Settlement Credit Flow Credit Entry Invoicing Final Settlement ROI Setup S2K Enterprise Interface Setup Order Entry Invoicing Procedure Settlement Procedure Settlement Procedure Flow Summary I

6 ROI Notes Customer Orders Daily Transaction Processing Credit Card Payments Order Entry/Update Summary Window Credit Card Processing Credit Card Swipe Voice Authorization Credit Card Not Available/Automatic Authorization Credit Card Available/Authorization Required Credit Accounts Receivable Daily Transaction Processing Credit Card Payments Cash Receipt Entry/Update Window Credit Card Retail Point of Sale Daily Transaction Processing Credit Card Payments Retail Sales Entry Summary Window Credit Card Swipe Manual Entry Voice Authorization CC# Scan set to Yes Voice Authorization CC# Scan set to No Multiple Credit Card Payments Debit Card Index /21/ EMC CCP_54.doc II

7 Overview S2K Enterprise permits credit card processing for several third party processors. S2K Enterprise integrates with either PAYware Connect, PayFlowPro or RiTA Direct. This integration permits the processing of credit card transactions through the Customer Order and Retail Point of Sale modules with real time authorization capabilities. With proper set up, the credit card process is a fully integrated process that handles backorders, declined authorizations, credit card swiping, and buffer reservations. Process Credit card processing takes place in the Customer Order, Accounts Receivable, and Retail Point of Sale applications. In the Customer Orders and Retail Point of Sale applications the credit card information is captured on the summary window by selecting the credit card payment type. The payment type holds the specifications for each credit card, i.e., credit card length, is authorization required, days to keep authorization, etc. In the Accounts Receivable application credit card information is captured during cash receipt entry on the Credit Card window by selecting the CREDIT CARD function on the Cash Receipt Entry/Update window. If authorization is required the system will perform real time authorization at the point of entering and accepting the credit card information and will capture and display the authorization number on the summary window. The authorization will be for the order amount and any additional dollar or percentage amount entered in the Reservation Buffer fields via the Cross Application Customer Orders Credit Card Interface window. Authorization Information The system will hold the authorization as valid based on the number of days entered in the Days to keep Authorization field in the Payment Type Master File. The End of Day process will go through the authorization log file and determine if any authorizations have expired. If any authorizations meet the expiration criteria, the system will change the authorization status from an A to an X, delete the record in the Accounts Receivable Deposits File, reduce the YTD deposit amount in the Order Header File, and print an expired authorization report for all expired authorizations. If the authorization had failed for other reasons, in addition to but not necessarily contingent on the expiration date, the order may be placed on hold depending on interface settings. Note: To review any expired authorizations that need to be re-authorized, a Credit Card Authorization Expiration Report can be run from the S2K Enterprise Customer Orders Reports menu. Re-Authorizing Re-authorizing orders can be done from the Order Entry/Update summary window. Select the order from the Order Entry/Update window. Continue through the order until you have reached the Order Entry/Update summary window. From the summary window click on the CREDIT CARD button, this will display the Order Entry/Update window. On this window position your cursor on the desired transaction and click on the POS TO SELECT button. This will pass deposit amount, card type, card number and card expiration date back into the order. The user can now change any of the captured data and then resubmit for authorization. Pick Ticket Process Pick tickets will have no effect on credit card order processing unless the order is split out by locations. If a credit card was taken for an order with merchandise being picked and sent from several locations, the system will need to recalculate the authorization dollars. When the pick ticket process is run the system will split the order out by location creating individual orders. At this point the system will reverse the original authorization and split out the amount taken on the card based on the individual order totals and re-authorize them for the new split amounts. Note: The system will generate a report for any declined authorizations. 1

8 Invoicing The invoicing cycle does several functions that will affect credit card orders. When invoicing, the system will check to see if the order has been completely shipped. If an order has been split due to backorder conditions the system will re-authorize the remaining balance on backorders during the invoice cycle. The invoicing cycle will also mark all authorized orders for settlement. The settlement process occurs during the End of Day process. Split Order Processing Suppose you have taken a credit card deposit on an order with merchandise from different locations. During the printing of Pick-ticket process the order gets split into three different orders. In that case we reverse out the original authorization done to the base order and split the amount taken as deposit in the ratio of their new order totals (calculation given later) and reauthorize them for the new split deposit amount. A report gets printed for any declined authorizations. Calculation for Split Order Processing Amount Say for example the base order (123-00) total is $1000 & the deposit taken on the order is $500. During the Pick Ticket printer process suppose the order gets split 3 ways (123-00, & ) with order totals of $500, $200 & $300 respectively. Then split order processing does 4 new transactions First we reverse the initial deposit of $500 taken on order & then we re-authorize the $500 deposit split in ratio of the order totals for the orders , & So the deposit for respective orders will be $250 (123-00) = ($500/$1000) * $500 $100 (123-10) = ($500/$1000) * $200 $150 (123-20) = ($500/$1000) * $300 Calculation for Backorder Re-Authorization Amount Consider a base order (123-00) with order total of $1000 & the deposit taken on the order $800. Suppose we have only half of the merchandise available to ship, when the order gets invoiced, we have an invoice total of $500 for the base order (123-00). That s the amount that gets settled for the base order & the remaining deposit amount $300 ($800 - $500), is re-authorized for the backorder (123-01). Credit Card Data Purge It is VAIs recommendation to run XADLDTAQ program during IPL to purge credit card queues. While running, make sure the Credit Card Engine is not active. Make sure the library list is correct by executing the EDITCL command prior to running the XADLDTAQ program. Additionally, the user should have proper authority to DLTDTAQ. 2

9 Cross Applications Interface Set Up C r e d i t C a r d P r o c e s s i n g : U s e r G u i d e Setup for PAYware Connect, PayflowPro (VeriSign) or RiTA Direct takes place in the Cross Application Customer Order Credit Card Interface. Select Customer Orders from the S2K Enterprise Cross Applications Interface menu (Figure 1). Select Customer Orders from the S2K Enterprise Cross Applications Interfaces menu. Figure 1 S2K Enterprise Cross Applications Interfaces Menu 3

10 Customer Orders Interface Selecting Customer Orders prompts the display of the following Customer Order Interface window. Click on the CREDIT CARD button. Figure 2 Customer Orders Interface Window Clicking on the CREDIT CARD button from the Customer Order Interface window prompts the display the following Customer Orders Credit Card Interface window. 4

11 Credit Card Interface Clicking on the CREDIT CARD button, from the Customer Orders Interface Setup window, prompts the display of the Customer Orders Interface Setup - Credit Card Interface window, allowing the user to set all parameters that will be used by the credit card processor. When processing credit card transactions throughout the system the credit card number is encrypted in the system as required by CISP (Cardholder Information Security Program) standards. FIGURE 3 CUSTOMER ORDERS INTERFACE SETUP CREDIT CARD INTERFACE WINDOW On the Customer Order Interface Credit Card Interface window the user will set all parameters that will be used by the credit card processor. Information regarding these parameters is as follows. Field Descriptions and Specifications Company Display Field Display field representing the company to which these Credit Card Processing settings will be applied. The value in this field defaults from selection on the Company Search window. Are you using Credit Card Processing Check Box Are you using credit card processing? If yes, select (check) the Are you using Credit Card Processing check box to provide the capability of using either the PayflowPro (VeriSign), RiTA Direct, or PAYware Connect credit card processing systems and reply to the following questions. If no, leave this check box unselected (blank) for NO and bypass all other entries on this window. If Y Product Drop Down Selection Box Select the product to be used if you are using credit card processing. Select PayflowPro (VeriSign), RiTA Direct, or PAYware Connect from the If YES Product drop down selection box to define which technology partner credit card processing software will be used. In order to select RiTA Direct the user must have QSECOFR authority. 5

12 If Y Enter Hold Reason Code for Credit Card Decline 4 Alphanumeric What default hold code should be used if the current credit card order is declined? Enter the default hold reason code that will automatically default to the Hold Reason Code field on the Order Entry/Update header 1 window upon credit card authorization decline. This code needs to be setup in the Hold Reason Code Master File. If the Hold Reason Code is NOT known, it can be located in the Hold Reason Search window by clicking on the 'SEARCH' icon. Additionally, with proper authority, the user may ADD, EDIT, mark INACTIVE or REACTIVATE a Hold Reason Code record, by clicking on the SEARCH icon. If Y Do you want to De-Allocate Inventory Check Box Will inventory for orders on shipping hold be de-allocated? Select (check) the De-Allocate Inventory check box for YES, to un-commit all order quantities, and place the quantity on backorder when the code is assigned to an order and placed on hold. Reservation Buffer: Whichever is Greater Dollar Amount Over Sale 9.2 Numeric At what dollar amount, over the sale, will the reservation buffer be set for freight? Enter the amount at which the reservation buffer will be set. This amount, added to the sale amount will become the reserved amount for credit card processing. Percentage Over Sale 8.3 Numeric At what percentage over the sale will the reservation buffer be set for freight? Enter the percentage at which the reservation buffer will be set. This amount added to the sale amount will become the reserved amount for credit card processing. Enter the discount percentage in decimal format, i.e., a discount of 10% would be entered as Note: The reservation buffer will be whichever is greater, the dollar amount over sale or the percentage over sale as entered on this window. For an Expired Authorization does the Order go On Hold Check Box Select (check) the For an Expired Authorization does the Order go On Hold check box for YES to place orders on hold if the order s credit card authorization has expired. If Y Specify the Hold Reason Code 4 Alphanumeric If the order was placed on Hold due to an expired credit card authorization, a valid Hold Reason Code is required in this field. If the Expired authorization causes order to go on hold check box is selected (checked) for YES, enter a valid Hold Reason Code in this field. If the Hold Reason code is NOT known, it can be located in the Hold Reason Search window by clicking on the SEARCH icon. If Y Do you want to De-Allocate Inventory Check Box If an order was placed on Hold due to an expired credit card authorization should inventory that had been allocated to these orders be de-allocated? If the Expired authorization causes order to go on hold check box was selected (checked) for YES, the user may select to de-allocate the inventory. The default setting for this box is unselected (blank) for NO. Select the If Y De-Allocate Inventory check box for YES to de-allocate inventory for orders placed on Hold for expired credit card authorizations. Do you need Automatic Re-Authorization for Backorders Check Box The default setting in the Automatic Re-Authorization for Backorders check box is unselected (blank) for NO. Selecting (checking) this check box for YES instructs the system to automatically perform credit card re-authorization for backorders when these backorders become available for shipment. Address Verification (AVS) Check Box The default setting in the Address Verification (AVS) check box is unselected (blank) for NO. Selecting (checking) this check box for YES instructs the system to verify Address Line 1 and Zip Code against the address on file at the bank. 6

13 CVV2 Check Box Do you require a Card Verification Value when processing credit card transactions? If yes, select (check) the CVV2 check box for YES. A credit card security code is a 3 or 4 digit number (not part of the credit card number) that is printed on the credit card. Because the card security code appears only on the credit card and not on receipts or statements, the card security code provides some assurance that the physical card is in the possession of the buyer. The credit card security code has various names, depending on the payment network. Visa calls it CVV2, Master Card calls it CVC2, and American Express and Discover call it CID. Credit card CVV2/CVC2/CID data (the verification number that appears on the front or back of the credit card) is NOT stored by RiTA/VeriSign and MAY NOT be stored in the integrated application. The following outlines CVV2 for RiTA: RiTA CVV2-based Auto-Decline Support: CVV2-based auto-decline support is available for merchants processing MOTO and e-commerce Pre-authorization transactions. Enabling this feature allows RiTA to automatically decline pre-authorization transaction requests based on certain CVV2 responses. The auto-decline feature is configurable at the MERCH_SITE level. There is a field in each MERCH_SITE record for configuring which CVV2 response codes will be accepted: CVV2_ACCPT_LVL. Configuration: To enable the CVV2 auto-decline feature, assign a value to the CVV2_ACCPT_LVL fields of the merchant's MERCH_SITE record. This value will be interpreted by RiTA to determine which CVV2 responses will not auto-decline a transaction. To assign a value for CVV2 auto-decline, use the following table to determine which value to assign in the CVV2_ACCPT_LVL field: CVV2 Code Description Value All response values accepted 0 Non-response accepted 1 U Issuer not certified and/or has not provided encryption 2 S keys Merchant indicated that CVV2 was not present on card 4 P Not processed 8 N CVV2 No Match 16 M CVV2 Match 32 As the table shows, to disable the CVV2 auto-decline feature for a MERCH_SITE, leave the value of CVV2_ACCPT_LVL for the MERCH_SITE record unassigned (null), or assign the fields the value of 0. If the feature is disabled, any approved pre-authorization transaction, regardless of the CVV2 response, will be available for completion. To enable the auto-decline feature, choose which CVV2 responses are acceptable and add the values associated with each response. The sum of these values will be placed in the appropriate CVV2_ACCPT_LVL field. 7

14 Example: To accept transactions only when the following CVV2 responses are returned by the processor: S-Merchant indicated that CVV2 was not present on card (4) M-CVV2 Match (32) Assign 36 ( = 36) as the CVV2_ACCPT_LVL value. Since the system does not store the CVV2 and RiTA does not support a Reference Transaction; therefore, during the back order re-authorization or the split process the system will be unable to pass the CVV2 code, which is why we have to keep 4 along with 32. The following outlines CVV2 for VeriSign: VeriSign CVV2-based Auto-decline Support: CVV2-based auto-decline can be set in the Fraud Protection filter (it may not work in the Test Mode). There is a filter named Card Security Code Failure that performs the action after the transaction is processed. This means that, if set to reject, the filter rejects the transaction after the transaction is authorized by the processor. Settlement success Response Codes for ROI 2 Alphanumeric/2 Alphanumeric Settlement Success Response Codes are supplied by the Authorization Network. Please refer to the corresponding addendum, for response codes, provided by VeriFone for further information. The system will look for these codes to determine the settlement status of the batch. If a response code, other than the 2 codes identified in this field, is returned then the batch was not settled. Credit Card Swipe Device Configuration ( /1,2) 1 Alphanumeric What is the Credit Card Swipe Device Configuration? The Credit Card Swipe Device Configuration determines how many carriage returns are present in the swipe data. 8

15 Verisign Interface In the year 2005, VeriSign Payment Services was acquired by PayPal. VeriSign's suite of products provides the ideal payment transaction platform for merchants who want to conduct business on the Internet. VeriSign's portfolio of products provides merchants with a high-speed, secure, and dependable way of processing transactions online, in real-time. The PayFlow Pro is the TCP/IP solution. Customer would be required to download the VeriSign SDK (Software Developers' Kit - VeriSign API) onto their web server. It is designed for merchants requiring a high performance solution to process a high volume of transactions. In conjunction with Pro, customer must use SSL (purchased separately) to encrypt the transmission of data between customer's servers and VeriSign. This is the link to the (Verisign, now PayPal) Payflow Pro product that S2K Enterprise software integrates with: Sign up Payflow Pro and make a note of the Partner, User Id and Password. Payflow Pro Datasheet: PayPal Manager User Guide: IBM Power Systems TM server System Requirements: TCP/IP Connection (Internet) JDK (Power Systems Developer Kit for Java) VeriSign Java SDK V3.05 requires JDK 1.1 through 1.4. VeriSign Java SDK V3.06 and up requires JDK 1.4 only. Power Systems Toolbox for Java Qshell Interpreter Please contact VAI with the following Payflow Pro Sign up information for VeriSign (now PayPal) setup: Partner User Id Password A VAI technician will setup the VeriSign SDK on your IBM Power Systems TM server IFS, do the necessary setup on the test environment and test a few transactions before handing it over to your organization for more testing. This setup performed by VAI is billable, estimated to take approximately 8 hours. The information gathered from Payflow Pro is used to populate the following VeriSign Interface window. If PayFlowPro is selected from the If -Y- Select Product drop down selection box on the Customer Order Credit Card Interface window, clicking on the ENTER icon will prompt the display of the following VeriSign Interface window. Figure 4 Verisign Interface Window 9

16 Enter the following information: Field Descriptions and Specifications Host Addr 30 Alphanumeric What is the Host Address or website at which authorization will take place? Enter the URL of the website at which the authorization will take place. The URL for live is live-payflow.verisign.com. Partner 15 Alphanumeric What is the Partner ID? The Partner ID is provided by the authorized VeriSign re-seller who registered your organization for the pay flow pro service. If your organization signed up on its own (downloaded the Partner ID password from internet) use VeriSign. Note: This field is case sensitive VeriSign work Library 10 Alphanumeric What is the designated VeriSign Work Library? This is the working library created by VAI. User ID 64 Alphanumeric The User ID and Password were created during the registration process. These fields are used to access the website and are validated by the website. Note: This field is case sensitive Password 32 Alphanumeric The User ID and Password were created during the registration process. These fields are used to access the website and are validated by the website. Note: This field is case sensitive AVS Check on Street Address Check Box Is Address Verification Service (AVS) required on the Street Address? The default setting in the AVS Check on Street Address check box is unselected (blank) for NO. Select (check) this check box for YES to verify the Address Line 1 against the address on file at the bank. On Zip Check Box Is Address Verification Service (AVS) required on the Zip Code? The default setting in the On Zip check box is unselected (blank) for NO. Select (check) this check box for YES to verify the Zip Code against the address on file at the bank. Native Optimizations Path 60 Alphanumeric What is the designated Native Optimizations Path? Enter the native optimizer for JDK (Java Developer Kit). Valid entries are: For IBM i5/os V4R5 JDK 1.2/1.3 - :/QIBM /ProdData/Java400/jt400ntv.jar For IBM i5/os V5R1 and above with JDK 1.2 and up - :/QIBM /ProdData/OS400/jt400/lib/jt400native.jar] 10

17 S2K Enterprise Cross Applications Interfaces RiTA Server Menu RiTA Overview RiTA (Rapid Internet Transaction Authority), a product of VeriFone, is a Java based engine that is operating system, database, and machine independent. Designed to enable a variety of hosting and merchant capabilities, RiTA Server is a highly scalable transaction switch that supports high-volume, multi-threaded transaction processing. RiTA Server is e-transaction middleware for businesses that process large volumes of payment transactions. RiTA Server provides TCP/IP or dial connectivity directly to processing companies. With the S2K Enterprise client application RiTA is integrated to the IBM Power Systems TM server using the Data Queue Integration Method (name/value pair API). RiTA includes the following credit card processing features and fraud protections: Accept all major credit cards - Visa, MasterCard, American Express, Discover, etc. Additionally, this product supports Debit Card with PIN and Check Processing. Customer database with recurring & installment billing allows you to schedule payment processing according to your specific business requirements. Real time or batch transaction processing. Highly scaleable and flexible to accommodate high levels of growth and activity. Support Level I & II Purchase Cards. Internet connectivity using SSL. Smart Settlement, automatically detect errors, quarantines those errors and resubmits until successfully transmitted. No transaction fee charged by VeriFone. Electronic Commerce certified (ECI Compliant). Meets up to date compliance standards for Visa and MasterCard. Fraud Protection Features Address Verification Service (AVS) is an industry standard known for its effectiveness in reducing loss. Data file encryption allows you to encrypt and protect credit card account numbers. 11

18 Select RiTA Server from the S2K Enterprise Cross Applications Interfaces menu, the following S2K Enterprise Cross Applications Interfaces RiTA Server menu will display. Figure 5 S2K Enterprise Cross Applications Interfaces RiTA Server Menu 1. Client ID Maintenance Pre Settlement Report Settlement Manager

19 Client ID Maintenance The Client ID Maintenance option provides for the setup of a link between the S2K Enterprise Merchant ID and the Client ID supplied by RiTA. Select Client ID Maintenance from the S2K Enterprise RiTA Server menu, the Merchant Search window will display. Figure 6 Merchant Search Window Program Functions Clicking on the ADD icon allows the user to add a new message to the Message File. Clicking on the EDIT icon, with the cursor positioned on a Message detail line on the VAI Message File Maintenance selection window, prompts the display of the VAI Message File Maintenance window and allows the user to edit the selected message. Clicking on the DELETE icon, with the cursor positioned on a Merchant detail line on the Merchant Search window, prompts the display of the Confirm Delete window prompting the user to confirm the deletion of the selected record. Click on the CONFIRM button to confirm the deletion. Clicking on the CANCEL button terminates the delete request. Figure 7 Confirm Delete Window Click on the ADD icon to add a new Client ID to the master file. The following RiTA Client ID Maintenance window will display in the ADD mode. Figure 8 RiTA Client ID Maintenance Window 13

20 Field Descriptions and Specifications Merchant ID 4 Alphanumeric Enter the Merchant ID. To edit an existing Merchant ID record, click on the PREVIOUS icon, the display will return to the Merchant Search window where the record to be edited may be selected. The Merchant ID is utilized by the credit card processing system to track credit card purchases through Customer Orders. If RiTA Direct, PayflowPro, or PAYware Connect is selected from the If YES Product drop down selection box, in the Cross Applications Customer Orders Interface via the CREDIT CARD button, this number is user-defined. The S2K Enterprise Merchant ID (4 Alphanumeric) is established in the Cross Applications Company Setup Interface via the INTERFACES button and will be used here to cross reference to the Bank Merchant ID (12 Alphanumeric). However, if a Land Merchant ID was entered in the Store Master File via the ADDITIONAL DEFAULTS button that number will need to be entered here as the cross reference to the Bank Merchant ID. Client ID 16 Alphanumeric Required field used for entering the Client ID supplied by RiTA. Entry in this field links the Merchant ID for your organization to the Client ID supplied by RiTA. If the Client ID number is NOT known, it can be located in the RiTA Client ID Search window by clicking on the SEARCH icon. Manager Password 16 Alphanumeric When mapping between the merchant number and the client ID a data element of password will be required. PABP (Payment Applications Best Practices) regulations require complex passwords. Additionally, passwords must be changed every 90 days. Program Functions Clicking on the RECORD INFO icon prompts the display of the Record Information window which provides the user with details on the date and time the record was created as well as the user ID of the person that created the record. Additionally, this window displays the date and time a change was made to the selected record and the user ID of the person that made the change. This function is only active when accessing the selected record in Change mode. Figure 9 Record Information Window 14

21 Pre Settlement Report Selecting Pre Settlement Report from the RiTA Server menu prompts the display of the RiTA Client ID Search window. Select a client ID, and click on the ENTER icon, to print a list of all transactions that will be settled during the next settlement process. Figure 10 RiTA Client ID Search Window 15

22 Settlement Manager Selecting Settlement Manager from the RiTA Server menu prompts the display of the RiTA Settlement Manager window. This inquiry lets the user know the status of the settlements, i.e., whether they were accepted, rejected, etc. Additionally, report details can be displayed or printed by selecting from the available program functions. To display batch details select the DISPLAY BATCH DETAILS button. Figure 11 RiTA Settlement Manager Window The RiTA Settlement Manager window displays the Client ID, Batch Status, Batch Date and Batch Amount for all transactions displayed. The batch status shows whether or not the debit and credit card transactions were accepted or rejected. Rejection codes displayed in this window are system-generated by RiTA. For additional information on RiTA rejection codes, contact VeriFone, or consult your RiTA documentation. The display can be sorted to display transactions for a specific Client ID and beginning and ending date by entering sort criteria in the fields provided. Additional information for sort fields is as follows. Field Descriptions and Specifications Client ID 16 Alphanumeric Optional field that may be used to sort the transactions displayed in the RiTA Settlement Manager window. If the Client ID is NOT known, it can be located in the RiTA Client ID Search window by clicking on the SEARCH icon. Beginning Date 8.0 Numeric Optional field that may be used to sort the transactions displayed in the RiTA Settlement Manager window by beginning date. Entry in this field is in YYYYMMDD (year, month, date format). End Date 8.0 Numeric Optional field that may be used to sort the transactions displayed in the RiTA Settlement Manager window by ending date. Entry in this field is in YYYYMMDD (year, month, date format). 16

23 Program Functions Clicking on the DISPLAY DETAIL REPORT button, with the cursor positioned on a transaction detail line, prompts the display of the Post Settlement Report spool file. See Detail Report on page 18 for additional information. Clicking on the PRINT DETAIL REPORT button, with the cursor positioned on a transaction detail line, prints the Post Settlement Report to the default printer for the current user. Clicking on the DISPLAY BATCH DETAILS button, with the cursor positioned on a transaction detail line, prompts the display of the Batch Details window showing the Client ID, batch number, batch amount, status (accepted, rejection code, etc.), batch count and amount for debit card transactions, credit card transactions and voids. See Batch Details on page 19 for additional information. 17

24 Detai l Report Clicking on the DISPLAY DETAIL REPORT button, with the cursor positioned on a transaction detail line on the RiTA Settlement Manager window, prompts the display of the Post Settlement Report spool file. Figure 12 Display Spooled File Window The Post Settlement Report provides transaction detail information including the Client ID, TROUTD (transaction identifier) Command (Sale = Debit Card Transaction, Credit = Credit issued on a credit card and Completion = Settlement has been completed on transaction), account number (credit or debit card number) and transaction amount. 18

25 Batch De tail s Clicking on the DISPLAY BATCH DETAILS button, with the cursor positioned on a transaction detail line on the RiTA Settlement Manager window, prompts the display of the following Batch Details window. Field Descriptions and Specifications Figure 13 Batch Details Window Client ID Display Field Display field identifying the Client ID for which this batch was processed. Batch Number Display Field Display field identifying the batch number associated with the transaction selected from the RiTA Settlement Manager window. Batch Amount Display Field Display field identifying the batch amount (amount of the transaction) associated with the transaction selected from the RiTA Settlement Manager window. Batch Status Display Field Display field identifying the status of the batch. If the transaction was rejected, the rejection code displayed is systemgenerated by RiTA. For additional information on RiTA rejection codes contact RiTA or consult your RiTA documentation. Count Display Field Display field identifying the number of debit card, credit card and void transactions included in the selected batch. Amount Display Field Display field identifying the total amount (value) of the debit card, credit card and void transactions included in the selected batch. Date/Time Display Fields System-generated display fields identifying the date and time on which the batch was generated. 19

26 VeriSign Merchant Specific User Profile Selecting VeriSign Merchant Specific User Profile from the S2K Enterprise Cross Applications Interfaces menu prompts the display of the VeriSign Merchant Specific User Profile prompt window. This option provides for the setup of a link between the S2K Enterprise Merchant ID and the partner information supplied by VeriSign/Payflow Pro. Information entered here will override information entered on the VeriSign Interface window via the Cross Applications Customer Orders Interface using the CREDIT CARD button. Field Descriptions and Specifications Figure 14 VeriSign Merchant Specific User Profile Prompt Window Merchant ID 4 Alphanumeric Enter the Merchant ID. The Merchant ID is utilized by the credit card processing system to track credit card purchases through Customer Orders. If Verisign or RiTA are selected from the If Y Type of Processing drop down selection box, in the Cross Applications Customer Orders Interface via the CREDIT CARD button, this number is user-defined. The S2K Enterprise Merchant ID (4 Alphanumeric) is established in the Cross Applications Company Setup Interface via the INTERFACES button. However, if a Land Merchant ID was entered in the Store Master File via the ADDITIONAL DEFAULTS button that number will need to be entered here. The Merchant ID number entered here is used to establish specific VeriSign partner information. Additionally, the Information entered here will override information entered on the VeriSign Interface window via the Cross Applications Customer Orders Interface using the CREDIT CARD button. Click on the ENTER icon to continue. The following VeriSign Merchant Specific User Profile detail window will display. Field Descriptions and Specifications Figure 15 VeriSign Merchant Specific User Profile Detail Window Merchant ID Display Field Defaults from entry on the VeriSign Merchant Specific User Profile prompt window. Partner ID 15 Alphanumeric The Partner ID is provided by the authorized VeriSign re-seller who registered your organization for the Payflow Pro service. If your organization signed up on its own (downloaded the Partner ID password from internet) use VeriSign (now PayPal). Note: This field is case sensitive 20

27 User ID 65 Alphanumeric The User ID was created during the registration process. This field is used to access the website and is validated by the website. Note: This field is case sensitive. Password 32 Alphanumeric The Password was created during the registration process. This field is used to access the website and is validated by the website. Note: This field is case sensitive. Program Functions Clicking on the DELETE icon prompts the display of the Confirm Delete window prompting the user to confirm the deletion of the selected record. Click on the CONFIRM button to confirm the deletion. Clicking on the CANCEL button terminates the delete request. Figure 16 Confirm Delete Window Clicking on the RECORD INFO icon prompts the display of the Record Information window which provides the user with details on the date and time the record was created as well as the user ID of the person that created the record. Additionally, this window displays the date and time a change was made to the selected record and the user ID of the person that made the change. This function is only active when accessing the selected record in CHANGE mode. Figure 17 Record Information Window 21

28 File Maintenance Tables The following File Maintenance table from the S2K Enterprise Customer Orders File Maintenance menu must be maintained for Credit Card Processing to function. Payment Types The Payment Type Master File maintains information for deposit type codes used during the Order Entry process. For clarification purposes, different payment type records should be established for each payment method accepted at retail stores, i.e. Visa, Discover, American Express, Gift Certificates, etc. To add a record to the file, select Payment Types from the S2K Enterprise Customer Orders File Maintenance menu, the Payment Type Search window will display (not shown). Click on the ADD icon to add a new Payment Type code to the master file. The following Payment Type File Maintenance window will display. Field Descriptions and Specifications Figure 18 Payment Type File Maintenance Window Company Display Field The company number defaults from the Payment Type Search window and is based on the current user s S2K Enterprise User Profile. Payment Type 6 Alphanumeric To create a new payment type code, enter a code that uniquely identifies the Payment Type record being created. Click on the ENTER icon to continue. Additional entry fields are activated. To edit an existing payment type record, click on the PREVIOUS icon, the display will return to the Payment Type Search window where the record to be edited may be selected. 22

29 Once the company and payment type have been entered, click on the ENTER icon to continue. Additional entry fields are activated. Field Descriptions and Specifications Figure 19 Payment Type File Maintenance Window Description 30 Alphanumeric Required field used for entering free-form text to describing the Payment Type code. Try to use a description that accurately describes the code. For example, do not use credit card when this code is for a Master Card credit card. Allow Refund of Cash Check Box If this check box is selected (checked) for YES, users will be permitted to refund cash, to the customer, when processing Returns with a Receipt during the order entry process, if the original order payment type, selected at the time of Order Entry, is the Payment Type selected here. Leave this check box unselected (blank) for NO to prohibit cash refunds for the payment type selected here. Wait Days for Cash Refund 3.0 Numeric If the preceding Allow Refund of Cash check box is selected (checked) for YES, enter the number of days that must transpire before cash refunds are permitted. Typically, this field would be used for a Payment Type of CHECK and the number entered here would represent an amount of time in excess of the number of days if takes for a check to clear, this will assure your organization that funds have been collected before a cash refund is made to the customer. Authorization Required Check Box Entry in this field is required. If this check box is selected (checked) for YES, users will be required to enter an authorization number on the Order Entry/Update summary window during the order entry process when using this payment type code. Orders using payment types that require an authorization cannot be processed until an authorization code is entered. Authorization numbers are typically used for credit card payments, or for checks approved through a check clearing service. If this check box is unselected (blank) for NO, an authorization number will not be required on the Order Entry/Update summary window during the order entry process. 23

30 Validate Expiration Date Check Box Selecting (checking) this check box for YES instructs the system to determine whether or not the expiration date of a credit card is a valid date. Days to Keep Authorization 7.0 Numeric The value entered in this field refers to credit card authorizations only. Days to Keep Authorization is an optional field that can be used to record the number of days in which the system will consider the Credit Card Authorization to be valid. The system will use the number of days entered here and begin the calculation from the date of the transaction. During the end of day process authorizations that have become eligible to expire will receive a status code of X. Additionally, the end of day process will delete the deposit record in the Deposits Master File and reduce the year to date deposit amount in the Order Header File. Bank Number (debit) 2.0 Numeric Required field validated against the Bank Master File. Represents the bank account deposits received during Customer Order Entry (not used for Retail Point of Sale transactions) will be deposited to. If the bank number is NOT known, it can be located in the Bank Master File by clicking on the 'SEARCH' icon. Additionally, with proper authority, the user may ADD, EDIT mark INACTIVE or REACTIVATE a Bank code, by clicking on the SEARCH icon. General Ledger (credit) 23 Numeric Required field validated against the Chart of Accounts Master File. Represents the general ledger account, deposits received during Customer Order Entry (not used for Retail Point of Sale transactions) should be credited to. This is typically the general ledger account number for the deposits payable liability account. Amounts credited to this account will appear on the Daily Deposit Register printed during end-of-day processing. If the general ledger account number is NOT known, it can be located in the Chart of Accounts Master File by clicking on the 'SEARCH' icon. Additionally, with proper authority, the user may ADD, EDIT mark INACTIVE or REACTIVATE a General Ledger number, by clicking on the SEARCH icon. Validate Credit Card Check Box Entry in this field is required. If this check box is selected (checked) for YES credit card payment types will be validated during the order entry process. If this check box is unselected (blank) for NO credit card payment types will not be validated during the order entry process Note: For Customer Order Entry, this field indicates to the credit card processing system that this Payment Type record is for a credit card. Credit Card Lengths 2.0/2.0/2.0 Numeric Entry in this field is required. Enter the number of digits on this credit card payment type. Space has been provided for two additional entries for the length of the credit card number in the event that the number of digits on this credit card changes. If Validate Credit Card is selected (checked) for YES, in the preceding field, entry in this field is required. Note: This field only applies to Retail Order Entry and not Customer Order Entry. Mandatory CC#/CK# Check Box If this check box selected (checked) for YES the system is instructed to require that the user enter a Credit Card Number or Check Number when accepting deposits on an order in the third window of Order Entry/Update. If this check box is unselected (blank) for NO the user will have authority to enter deposits without requiring a Credit Card or Check number on the Order Entry/Update summary window. Print Signature Receipt Check Box If this check box selected (checked) for YES the system is instructed to print a register receipt and a signature receipt when the Payment Type created here is selected on the Retail Sales Entry summary window. If this check box is unselected (blank) for NO the system is instructed to print a register receipt only. Exclude from Internet Check Box If this check box is selected (checked) for YES the system is instructed to exclude this Payment Type as an option for Internet orders. If this check box is unselected (blank) for NO this Payment Type will be available for Internet orders and an entry will be required in the Thumbnail Image field. 24

31 Thumbnail Image 30 Alphanumeric Conditional field, entry in this field will be required if the Exclude from Internet check box is unselected (blank) for NO. Enter the path and filename of the thumbnail image to display for this payment type. Payment type images reside in the IBM Power Systems TM server Integrated File System (IFS). Valid AVS Response Code 1 Alphanumeric Each This field will display provided the Address Verification Service (AVS) check box is selected (checked for YES in the Cross Applications Customer Orders Interface via the CREDIT CARD button. AVS codes are one character response codes used to validate a cardholder's given address against the issuer's records, to determine accuracy and deter fraud. Please refer to the corresponding addendum, for response codes, provided by VeriFone for further information. Payment Type Class Drop Down Selection Box Valid Payment Type codes are CASH, CHECK, CREDIT CARD, IN HOUSE, DEBIT CARD, or MISCELLANEOUS. Payment Type Class is a system-generated table representing the classification that this Payment Type is categorized by. For instance, Payment Types of AMEX, MC, VISA, or Discover may all be classified as CREDIT CARD. The following example Payment Types should be setup with the Payment Type Class shown: Payment Types Credit Cards Payouts, Traveler s checks In House Charges, Gift Card, Store Credit Cash Check (Bank Checks) Debit Card Payment Type Class CREDIT CARD MISCELLANEOUS IN HOUSE CASH CHECK DEBIT CARD Note: When processing an order, in the Retail Point of Sale application, authorization will not be required, regardless of the setting in the Authorization Required check box, if a payment type is selected that has been designated with a Payment Type Class of CASH or MISCELLANEOUS. Note: Within Customer Order Entry a payment type coded with a payment class of IN HOUSE is prohibited, IN HOUSE payment classes are restricted to the Retail Point of Sale module. Open Cash Drawer Check Box If this check box is selected (checked) for YES the system is instructed to open the cash drawer when the Payment Type Class in the preceding field is tendered during order entry. If this check box is unselected (blank) for NO the cash drawer will not open during order entry when tendering the Payment Type Class selected in the preceding field. Program Functions Clicking on the RECORD INFO button prompts the display of the Record Information window which provides the user with details on the date and time the record was created as well as the user ID of the person that created the record. Additionally, this window displays the date and time a change was made to the selected record and the user ID of the person that made the change. This function is only active when accessing the selected record in CHANGE mode. Figure 20 Record Information Window 25

32 Clicking on the RETAIL button prompts the display of the Retail Store Payment Type window, allowing the user to set up individual stores, by company, by payment type, with separate bank accounts. See Retail on page 28 for additional information. Clicking on the REACTIVATE icon reactivates records previously marked as inactive. This function is only active if an inactive record was selected from the search window. 26

33 Credit Card Type Clicking on the ENTER icon, from the Payment Type File Maintenance window, will display the following Credit Card Type Selection window provided CREDIT CARD was selected from the Payment Type Class drop down selection box. The Credit Card Type Selection window is used to select the appropriate credit card type for the credit card entered on the Payment Type File Maintenance window, e.g., Master Card, Visa, American Express, etc. S2K Enterprise will use the selection made here during credit card processing in the Retail Point of Sale module to validate that the card swiped matches the credit card tender selected on the Retail Entry summary window. Figure 21 Credit Card Type Window Credit Card Types in the Credit Card Type Selection window are predefined in S2K Enterprise. Select (check) the appropriate type and click on the ENTER icon to continue. The following credit card numeric prefixes are predefined in S2K Enterprise: 51, 55, 36 Master Card 4 Visa 34, 37 American Express 300, 305, 38 Diners Club 6011, 65 Discover Card 2014, 2149 enroute/diners Club 3, 2131, 1800 JCB 27

34 R etai l Clicking on the RETAIL button, from the Payment Type File Maintenance window, prompts the display of the Retail Store Payment Type window. This function allows the user to set up individual stores, by company, by payment type, with separate bank accounts. Therefore, stores residing in different geographic locations have the ability to bank in a location that is convenient. For instance, a payment type of American Express may be used by one company with 8 different store locations, with each individual store being responsible for their own daily deposits. Figure 22 Retail Store Payment Type Window Company number and payment type default based on the current user profile and entry on the Payment Type File Maintenance window. Additional field descriptions are as follows. Field Descriptions and Specifications Del 1 Alphanumeric Entry in this field is optional. Valid entry is D for DELETE. Enter a D for DELETE for each store to be deleted from the Retail Store Payment Type window. Store 4.0 Numeric Enter the Store Number(s) for which this Payment Type record will be available. If the Store code is NOT known it can be located in the Retail Store Search window by clicking on the 'SEARCH' icon. Debit Bank 2.0 Numeric Required field validated against the Bank Master File. Represents the bank account deposits received during order entry will be deposited to. If the Bank number is NOT known, it can be located in the Bank Search window by clicking on the 'SEARCH' icon. Additionally, with proper authority the user may ADD, EDIT mark INACTIVE or REACTIVATE a Bank code, by clicking on the SEARCH icon. General Ledger Credit 23 Numeric Required field validated against the General Ledger Master File. Represents the general ledger account, deposits received during order entry should be credited to. This is typically the general ledger account number for the deposits payable liability account. Amounts credited to this account will appear on the Daily Deposit Register printed during end-of-day processing. If the General Ledger Account Number is NOT known, it can be located in the General Ledger Account Search window by clicking the SEARCH icon. Additionally, with proper authority, the user may ADD, EDIT mark INACTIVE or REACTIVATE a G/L Number, by clicking on the SEARCH icon. 28

35 VeriSign Documentation 29

36 Systems Requirement TCP/IP Connection (Internet) JDK (AS/400 Developer Kit for Java) 1.1.8, 1.2. Check with java *version command AS/400 Toolbox for Java. Should be in /QIBM/ProdData/HTTP/Public/jt400 Qshell Interpreter VeriSign SDK API (Download from Internet) Internet Merchant Account An account with a financial institution that accept payments over the Internet. Configuration Management In the integrated file system create the following directory structure in the root file system (/). VeriSign certs com Make all the directory shared Copy f73e89fd.0 into /VeriSign/certs Copy VeriSign.jar into /VeriSign/com Copy PFProJava.java (our version with Java Toolbox) into /VeriSign. Use SAV (Save) and RST (Restore) command. Compile PFProJava.java and create PFProJava.class in /VeriSign - SET CLASSPATH (wrkenvvar) environment variable as: :/VeriSign/com/VeriSign.jar:/QIBM/ProdData/HTTP/Public/jt400/lib/jt400.zip :/QIBM/ProdData/HTTP/Public/jt400/utilities:. - Start Qshell interpreter (STRQSH) - cd /VeriSign - javac PFProJava.java Create a Data length 128 chr. in QGPL Make sure the subsystem VAINEP (*SBSD) and the jobq VAINEP (*JOBQ) exist. 30

37 VeriSign Interface (VERSGNINT) Parameter List: Trxtype 1 A/D I Company 2,0 I Order# 9 I Credit card# 16 I Expdt 4 yymm I Amount 11,2 I Address 30 I Zip 9 I Swipe data 117 I Payment type 6 I Auth code 6 O Trans Ref 15 O Resp. Msg 30 O Fatal 1 O Valid 1 O If the Trxtype = A (Authorization) then for credit (Amount < 0), do not issue any transaction, instead treat it as valid, get the Routing id from VXACONT.XANO01 with key VERISIGN and pass back the OK status and go out. Call VERSETUP to create the DTAQ (@CR+Job#) If the Trxtype = A (Authorization) then for regular order issue Authorization transaction (A) If the Trxtype = D (Delayed Capture) for regular order issue Delayed Captured transaction (D) when the amount is > 0 If the Trxtype = D (Delayed Capture) for credit (Amount < 0), issue credit transaction. If the Trxtype = D (Delayed Capture) for regular order issue Void transaction (V) when the amount is 0 Send data queue entry Receive response from DTAQ (@CR+job#) VeriSign Setup (VERSETUP) Create if it is not present Create the DTAQ (@CR+job#) if it is not present. Check whether the batch engine (VERSGNENG) is active, if not submit it in VAINEP JOBQ. VeriSign Batch Engine (VERSGNENG) Receive entry from Call Java Servlet PFProJava Get the response from Send response to DTAQ (@CR+job#) PFProJava (Java Servlet) Connect to the VeriSign web server Send the credit card request Receive response in using AS/400 Toolbox for Java. 31

38 VeriSign Settlement (VERSPORT) Same as USRPORT, except call VERSPO1 instead of USRPO1. End VeriSign (VERSENDGEN) Delete the which will send a MONMSG to the VeriSign batch engine (VERSGNENG) that will delete DTAQ and end the engine. VeriSign Settlement (VERSPO1) Same logic as USRPO1 with the following exception: Select records based on LF VCOAPP6 (Select TQSTAT=T ) Call VERSGNINT with the following parameters: Trxtype 1 D I Company 2,0 I Order# 9 I Credit card# 16 I Expdt 4 yymm I Amount 11,2 TQRQSM I (Amount to be settled) Address 30 I Zip 9 I Swipe data 117 I Payment type 6 I Auth code 6 O Trans Ref 15 I Resp. Msg 30 O Fatal 1 O Valid 1 O Process only if the Valid parameter is Y (Successful) Update VCOAPPV with the TQSTAT= S Update Trans ref. In VCOAPPV and VARDEPS for credit Note: For cancel order (OADEL=C, and OAPRNT other than E/I) only call VERSGNINT to void the transaction. 32

39 Layout Job number Char Host Website Char Order number Num 9, User Char Password Char Transaction Type Char (A-Authorization, D-Delayed Captured, C-Credit) Tender Type Char (Always C-Credit card) Credit card number Char Expiration date Num 4, (MMYY) Transaction Amount Num 11, VeriSign reference Id Char (Required with transaction type D-Delayed captured) Address Char Zip Char Partner Char Response DTAQ (@CR+job#) Layout Return code Char (A-Approved, D-Declined) Result Char (RESULT) Transaction reference Char (PNREF) Authorization code Char (AUTHCODE) AVS Address match Char (AVSADDR) AVS Zip match Char (AVSZIP) Response Text Char (RESPMSG) 33

40 Regular Order Flow Order Entry VERISIGN Issue Authorization transaction (A) [PGM:VERSGNINT called from COAUCR] VCOAPPV TQADCD A / D TQ$AMOUNT Approval Amount (including buffer) TQDAMOUNT Deposit Amount (excluding buffer) TQRQSM 0 TQSAMOUNT 0 TQSTAT blank VARDEPS TDDEL R TDAMOUNT Deposit Amount (excluding buffer) TDDC D TDTYPE A ROI AU Invoicing VCOAPPV TQADCD A / D TQ$AMOUNT Approval Amount (including buffer) TQDAMOUNT Deposit Amount (excluding buffer) TQRQSM Required Settlement Amount (invoice amount) TQSAMOUNT 0 TQSTAT T ROI AT Final Settlement VERISIGN Issue Delayed captured transaction (D) with the settlement amount (TQRQSM) [PGM:VERSPO1 called from VERSPORT which is called from COSETLCL] VCOAPPV TQADCD S TQ$AMOUNT Approval Amount (including buffer) TQDAMOUNT Deposit Amount (excluding buffer) TQRQSM Required Settlement Amount (invoice amount) TQSAMOUNT Settlement amount TQSTAT S VARDEPS TDDEL A TDAMOUNT Actual Settlement Amount TDDC D TDTYPE A ROI AS 34

41 Credit Flow Credit Entry VERISIGN No action VCOAPPV TQADCD A / D TQ$AMOUNT Approval Amount (-ve) TQDAMOUNT Deposit Amount (-ve) TQRQSM 0 TQSAMOUNT 0 TQSTAT blank VARDEPS TDDEL R TDAMOUNT Deposit Amount (excluding buffer) TDDC C TDTYPE S ROI RC Invoicing VCOAPPV TQADCD A / D TQ$AMOUNT Approval Amount (including buffer) TQDAMOUNT Deposit Amount (excluding buffer) TQRQSM Required credit TQSAMOUNT 0 TQSTAT T ROI CT Final Settlement VERISIGN Issue Credit (C) with the credit amount (TQRQSM) [PGM:VERSPO1 called from VERSPORT which is called from COSETLCL] VCOAPPV TQADCD S TQ$AMOUNT Approval Amount (including buffer) TQDAMOUNT Deposit Amount (excluding buffer) TQRQSM Required settlement Amount (invoice amount) TQSAMOUNT Settlement amount TQSTAT S VARDEPS TDDEL A TDAMOUNT Actual Settlement Amount TDDC C TDTYPE S ROI CS 35

42 ROI Setup On the command line, type ADDLIBLE ASCCOM1. On the command line type CCMENU. The following Verifone JCharge menu will display: Figure 23 Verifone JCharge Menu Select Option 1 to Start JCharge processing or 2 to End JCharge processing. After selecting Option 1 to Start JCharge, it may take a few minutes before the Credit Card authorization process is fully functional. 36

43 S2K Enterprise Interface Setup Order Entry If credit card payment is entered the API COAUCR is called to authorize the credit card entered. COAUCR works in 2 phases. In the first phase it validates the credit card and its expiration date. If either is not valid an error is displayed during order entry. If the credit card is valid then COAUCR actually dials out to get an approval. If for some reason, payment is not approved the order goes on hold and the hold reason code is displayed. If the payment is approved an AU type of record is written to the ROI Transaction File CCFP9000 with the authorized amount. An AU record is written for a positive amount (not a credit). An RC type of record is written to CCFP9000 for a credit. A record is written to VARDEPS with a status code of R for each authorized payment or credit. You could have multiple credit card payment records in VARDEPS for the same order and each record has a unique identification number generated by ROI. Although ROI supports multiple credit cards to be used on the same order, at this time, this feature is not being utilized, therefore, for any order, the same credit card will have to be used, but it can be used a multiple number of times. A record is written to VCOAPPV for each payment/credit with the authorized amount and the unique identification number returned by ROI CCS. When an order is cancelled an API COCNCR is called that marks all the payment records for settlement with the field amount to settle (TSETAM) set to a 0. When the program COSETLCL is run, these marked records are settled. Invoicing Procedure A new program COUPML is called during the invoicing procedure to mark credit card payment records for settlement. This program reads through VCOBILL, for orders with credit card payments, it calls an API COSTMT to mark authorized records for settlement. COUPML passes as parameter to COSTMT for the amount that has to be marked for settlement. For credits, the amounts are always settled in full. After the invoicing cycle is run all the AU records are changed to AT and RC records are changed to CT in the file CCFP9000. Settlement Procedure A new program COSETLCL has been written that actually starts the settlement process for all credit card payments that have been marked for settlement during the invoicing cycle. COSETLCL loops through the Company Master File, for each company found with a Merchant ID it calls program COSTPT with the Merchant ID as the parameter. COSTPT is an interface program between S2K Enterprise and ROI processing. If the batch is successful then a JG type of record is written to CCFP9000 with the batch number and the amount settled. All AT records are changed to AS type and all CT type records are changed to CS type records in CCFP9000. These records are updated with the batch number, settlement date and time. COSETLCL then calls USRPORT with the batch number as the parameter. USRPORT calls the programs: USRPO1 to change the status of credit card payment records from R to A in VARDEPS, update deposit amount in VARDEPS with the actual amount settled and update the YTD deposit field OAYTTD in VCOHEAD. For each settled record, this program also writes a record to file VCORESV to be used later by COUPGL2. VCOAPPV is also updated with the amount settled and the date and time. COUPSA2 to write payment records to the Open A/R File for credit card deposits that where settled. ARUPDPCL to process deposit records settled. COUPGL2 to write deposit records to VARGLMP for G/L postings. 37

44 If the settlement has not completed successfully the program (USRPORT2) will be run to issue a message stating that the settlement was unsuccessful. Credit card transactions that have completed the settlement process are purged from the Credit Card Approval Tracking File (VCOAPPV) during the Customer Orders End of Month Procedure. 38

45 Settlement Procedure Flow Summary COSETLCL + COSTPT (MERCHANT-ID) + USRPORT (Settlement Date, Settlement Time) + USRPO1 (Settlement Date, Settlement Time) + COUPSA2 + ARUPDPCL + COUPGL2 ROI Notes 1. If settlement does not complete successfully, contact ROI. They recommend that the client call ROI for assistance on how to settle an unsettled batch. All our program does is, flash a message stating that the batch did not complete normally. All the unsettled records in file CCFP9000 will be left in an AF state for a failed settlement, AA or AX state if program terminates abnormally. Similarly the records will be in CF, CX or CA state for a credit. 2. ASCCOM1 the ROI CCS library for their data files and other utilities should not be in user s library list as per ROI documentation. So ASCCOM1 library is added and removed from library list by the API programs. 3. Point-of-Sale entry program, COETR3 too has been modified to work with the ROI CCS and changes similar to order entry have been done. This program uses the same API that order entry uses to authorize the credit card payments. Point-of-Sale credit card payments are marked for settlement during the invoicing cycle run during EOD (for OAPRNT= E records) and the records are settled when the utility COSETLCL is run. COET01 too has been modified to handle cancelled Point-of-Sale orders. COSTPT is the program that is called from COSETLCL and it initiates the whole settlement process. The program has been coded in such a way that it s in infinite loop until a response is received from ROI. If we get back a response from ROI stating that a batch completed successfully then the program goes into another infinite loop till at least one settled record (AS/CS type record) is updated with the batch number. If the batch doesn t settle normally or if there were no records to settle then we flash a message saying that the batch did not settle normally. Because of the way ROI works, COSTPT had to be put in an infinite loop till we get a response from ROI. There is good possibility that this program could continue to stay in infinite loop if a code is returned by ROI that they haven t mentioned in their documentation. 39

46 Customer Orders Daily Transaction Processing Credit Card Payments Order Entry/Update Summary Window During the Order Entry process a credit card payment can be entered on the Order Entry/Update summary window. Enter payment information to process the credit card payment; enter the deposit amount, payment type, credit card number, expiration date, and authorization code. Figure 24 Order Entry/Update Summary Window The following information will need to be entered for credit card payments. Field Descriptions and Specifications Deposit Amount 11.2 Numeric If the user has the appropriate authority, they will be able to take a deposit on a customer order. This authority is granted if the Deposit Entry check box is selected (checked) for YES in the Cross Applications User Defaults Interface for the current user. The user would enter the total dollar value of the deposit in the Deposit Amount field. The system would then require entry of a payment type, and an authorization number if the Payment Type Master File requires one. When the invoice procedure is run, the amount of the deposit is added to the customer s year-to-date deposits for this order. This occurs whether or not the actual order has been invoiced. When the order is invoiced, the amounts of the year-to-date deposits are applied as a payment on the resulting invoice. If the deposit amount equals the invoice total, the item is marked in the open accounts receivable file as paid-in-full. If the deposit amount is less than the invoice total, the remaining portion of the invoice is recorded in the open accounts receivable file as a balance due. The invoice that prints for the customer in either case will properly record the amount of the deposit. Note: Clicking on DEPOSITS button prompts the display of the Deposit History window in which the user can view prior deposit history for this invoice. 40

47 Payment 6 Alphanumeric This field will display if the Deposit Entry check box is selected (checked) for YES in the Cross Applications User Defaults Interface for the current user. Entry is required if the user has entered a deposit amount for this order. Entry in this field will be validated against the Payment Type Master File. Entry in this field represents the method of payment for the deposit being recorded on the order. If the Payment Type is NOT known, it can be located in the Payment Type Search window by clicking on the 'SEARCH' icon. Additionally, with proper authority, the user may ADD, EDIT, mark INACTIVE or REACTIVATE a Shipping Terms code, by clicking on the SEARCH icon. Selection of certain payment types will prompt the display of an Authorization Required for Payment Type message during processing. This message will display if the Authorization Required field in the Payment Type Master File is selected (checked) for YES, for the payment type selected. For most payment types this is only a warning message and can be bypassed by clicking on the ENTER icon. However, if the payment type selected is a credit card, and the Authorization Required field in the Payment Type Master File is selected (checked) for YES, then entry will be required in the Authorization field before the user can end the order. Additionally, the system will validate the credit card to insure that the payment type selected matches the credit card number being used provided the Validate Credit Card check box is selected (checked) for YES in the Payment Type Master File. For additional information on processing credit card payments refer to Credit Card Processing on page 42. CC#/Ck 25 Alphanumeric This field will display if the Deposit Entry check box is selected (checked) for YES in the Cross Applications User Defaults Interface for the current user. Entry in this field represents the customer s check number or credit card number that was used for the deposit on this order. For additional information on processing credit card payments refer to Credit Card Processing on page 42. Note: Credit Card payments are not permitted for customers that have been established as foreign currency customers in the Customer Master File. Exp 4.0 Numeric This field will display if the Deposit Entry check box is selected (checked) for YES in the Cross Applications User Defaults Interface for the current user. Represents the date the customer s credit card expires. Format is MMYY. For additional information on processing credit card payments refer to Credit Card Processing on page 42. Auth 8 Alphanumeric This field will display if the Deposit Entry check box is selected (checked) for YES in the Cross Applications User Defaults Interface for the current user. May be required if the Authorization Required check box in the Payment Type Master File is selected (checked) for YES. Program Functions on the Order Entry/Update summary window Clicking on CREDIT button, from the Order Entry/Update summary window, prompts the display of the Credit Card Processing Log Inquiry window which displays all credit card deposits taken for this order. The CREDIT button will only display if Credit Card Processing has been established via the Cross Applications Customer Orders Interface. See Credit on page 46 for additional information. 41

48 Credit Card Processing Credit Card Swipe Entering a deposit amount and credit card payment type and clicking on the ENTER icon prompts the display of the following Credit Card Processing window. Figure 25 Credit Card Processing Window If the credit card is available select (check) the Do you have the credit card check box for YES. Click on the ENTER icon to continue. The following Credit Card Processing: Please Swipe Card window will display. Figure 26 Credit Card Processing: Please Swipe Card Window Swipe the credit card. A window will display notifying the user that authorization is in progress. Figure 27 Authorization Is In Progress Window Once authorization has completed the following Credit Card Approval Code window will display. Figure 28 Credit Card Approval Code Window The Credit Card Approval Code window will display the currency code, as established for the customer selected, amount of the sale approved and the approval code. Click on the ENTER icon to continue. 42

49 Voice Author iz at ion Entering a deposit amount and credit card payment type and clicking on the ENTER icon prompts the display of the following Credit Card Processing window. Figure 29 Credit Card Processing Window If the credit card terminal is down or the swipe could not be read by the credit card terminal select (check) the Voice Authorization check box for YES. Click on the ENTER icon to continue. The following Please Enter Card Information window will display. Figure 30 Please Enter Card Information Window The Authorization field will be available for entry. Enter the authorization code and click on the ENTER icon to continue. A window will display notifying the user that authorization is in progress. Figure 31 Authorization Is In Progress Window Once authorization has completed the following Credit Card Approval Code window will display. Figure 32 Credit Card Approval Code Window The Credit Card Approval Code window will display the currency code, as established for the customer selected, amount of the sale approved and the approval code. Click on the ENTER icon to continue. 43

50 Credit Card Not Avail a ble /Automatic Author i zat ion Entering a deposit amount and credit card payment type and clicking on the ENTER icon prompts the display of the following Credit Card Processing window. Figure 33 Credit Card Processing Window If the credit card is not available, and the system will process the credit card automatically upon entry of the credit card number, leave both the Do you have the credit card and Voice Authorization check boxes blank for NO. Click on the ENTER icon to continue. The following Please Enter Card Information window will display. Figure 34 Please Enter Card Information Window Enter the credit card number and expiration date in the corresponding fields, click on the ENTER icon to continue. A window will display notifying the user that authorization is in progress. Figure 35 Authorization Is In Progress Window Once authorization has completed the following Credit Card Approval Code window will display. Figure 36 Credit Card Approval Code Window The Credit Card Approval Code window will display the currency code, as established for the customer selected, amount of the sale approved and the approval code. Click on the ENTER icon to continue. 44

51 Credit Card Avai lable / A uthor iz atio n Require d Entering a deposit amount and credit card payment type and clicking on the ENTER icon prompts the display of the following Credit Card Processing window. Figure 37 Credit Card Processing Window If the credit card is available but voice authorization is still required, i.e., the credit card terminal displayed the message Please call for Authorization, select (check) both the Do you have the credit card and Voice Authorization check boxes for YES. Click on the ENTER icon to continue. The following Credit Card Processing: Please Swipe Card window will display. Figure 38 Credit Card Processing: Please Swipe Card Window The Authorization Number field will be available for entry. Enter the authorization code and swipe the credit card. A window will display notifying the user that authorization is in progress. Figure 39 Authorization Is In Progress Window Once authorization has completed the following Credit Card Approval Code window will display. Figure 40 Credit Card Approval Code Window The Credit Card Approval Code window will display the currency code, as established for the customer selected, amount of the sale approved and the approval code. Click on the ENTER icon to continue. 45

52 Credit Clicking on CREDIT button, from the Order Entry/Update summary window, prompts the display of the Credit Card Processing Log Inquiry window which displays all credit card deposits taken for this order. The CREDIT button will only display if Credit Card Processing has been established via the Cross Applications Customer Orders Interface via the CREDIT CARD button. The Credit Card Processing Log Inquiry window displays the payment type, whether or not the transaction was approved or declined, approval code, approval amount, deposit amount, settlement amount, transaction date and time, and settlement date and time. Figure 41 Credit Card Processing Log Inquiry Window Positioning the cursor on a payment detail line and clicking on the SELECT PAYMENT button returns the display to the Order Entry/Update detail line and populates the Payment, Credit Card Number, and Exp fields; this feature can speed up the payment process when the customer is using the same credit card for multiple payments on the order. Company, order number and customer number and description default from the selected order. Additional field descriptions are as follows. Field Descriptions and Specifications Pay Type Display Field Display field identifying the payment type selected for the transaction; e.g., Visa, Master Card, etc. Defaults from the Payment/CC#, Ck field on the Order Entry/Update summary window. A/D Code Display Field Display field indicating the status of the credit card transaction, valid codes are A - APPROVED or D - DECLINED. Approval Code Display Field Display field identifying the approval code transmitted during the credit card transaction. Defaults from the Credit Card Approval Code window. Deposit Amount Display Field Display field identifying the amount of the deposit entered in the Deposit Amount field on the Order Entry/Update summary window. This field displays by clicking on the MORE INFO button. Approval Amount Display Field Display field identifying the transaction amount approved by the credit card processor. 46

53 Settlement Amount Display Field Display field identifying the amount processed during the settlement process. Credit card transactions are settled during the end of day process. Credit Card settlement is a procedure in which a transaction is processed between a merchant account provider and the issuing bank or credit card association of the buyer. In the case of a sale, funds are transferred from the issuing bank/card association to the merchant's account. The settlement amount may be less that the approval amount based on the invoiced amount. This field displays by clicking on the MORE INFO button. Date (Credit Card Transaction Date) Display Field Display field indicating the date on which the credit card transaction was approved/declined. Time (Credit Card Transaction Time) Display Field Display field indicating the time at which the credit card transaction was approved/declined. This field displays by clicking on the MORE INFO button. Date (Credit Card Settlement Date) Display Field Display field indicating the date on which the credit card transaction was settled. Time (Credit Card Settlement Time) Display Field Display field indicating the time at which the credit card transaction was settled. This field displays by clicking on the MORE INFO button. Program Functions Clicking on the SELECT PAYMENT button, with the cursor positioned on a payment transaction detail line, returns the payment details to the Order Entry/Update summary window for processing. Clicking on the ADDITIONAL INFO button displays an additional line of information for each payment transaction listed. This line displays the deposit amount, settlement amount, credit card transaction time and settlement time. 47

54 Accounts Receivable Daily Transaction Processing Credit Card Payments Cash Receipt Entry/Update Window Credit Card payments can be processed during Cash Receipt Entry on the Cash Receipt Entry/Update prompt window. To access this window select Entry/Update from the S2K Enterprise Accounts Receivable Daily Transaction Processing Cash Receipts menu. Once entries on the Cash Receipt Entry/Update batch control window (not shown) have been completed, click on the ENTER icon to continue; the following Cash Receipt Entry/Update prompt window will display. Note: Based on Interface settings the Cash Receipt Check Entry/Update window may display before the Cash Receipt Entry/Update prompt window, click on the ENTER icon to bypass the Cash Receipt Check Entry/Update window. Figure 42 Cash Receipt Entry/Update Prompt Window Enter the required information on the Cash Receipt Entry/Update prompt window and click on the CREDIT CARD button to process the credit card payment. When processing a credit card payment entry in the Check Number and Check Amt fields is not required. Field descriptions are as follows. Field Descriptions and Specifications Company Display Field The company number defaults from the Cash Receipt Entry/Update batch control window and may not be edited. The value in this field indicates the company to which the cash receipt batch will be posted. Batch Display Field The batch number defaults from the Cash Receipt Entry/Update batch control window and may not be edited. The value in this field indicates the system-generated batch number assigned to the current cash receipt batch. Time Display Field The value in this field indicates the system-generated time stamp assigned to the current cash receipt batch. This value displays in HHMMSS format. 48

55 Deposit Date Display Field The batch date defaults from the Cash Receipt Entry/Update batch control window and may not be edited. The value in this field indicates the calendar date on which the cash receipt batch was entered. Currency Display Field Display literal indicating the currency in which all entries within the current cash receipt batch will be made. Unlike currencies within a single batch are prohibited. User ID Display Field Display literal identifying the individual logged on to the current session, defaulting based on the current user s S2K Enterprise User Profile. Terminal Display Field Display literal indicating the workstation ID of the terminal assigned to the current session. All S2K Enterprise sessions are assigned a workstation ID on the IBM Power System TM. Bank Display Field The bank number defaults from the Cash Receipt Entry/Update batch control window and may not be edited. The value in this field indicates the bank to which the cash receipt batch will be posted. Invoice Number/Sequence 9.0 Numeric Entry in this field is optional. Entering an invoice number in this field assists in narrowing the invoice search when clicking on the INVOICE ENTRY icon. PO Number 20 Alphanumeric Purchase order number is an optional field available for entering the Customers purchase order number associated with this invoice. Entering a purchase order number in this field will further assist in narrowing the invoice search when clicking on the INVOICE ENTRY button. Parent Number 7 Alphanumeric If the parent customer number is NOT known, it can be located in the Customer Search window by clicking on the 'SEARCH' icon. If a parent number is entered here all open Accounts Receivable, for customers associated with the parent, will display on the Cash Receipt Entry/Update detail window. Additionally, with proper authority, the user may ADD, EDIT, mark INACTIVE or REACTIVATE a Customer record, by clicking on the SEARCH icon. Customers in the search window will only display if they have the same currency code as the bank selected on the Cash Receipt Entry/Update batch control window. Customer Number 7 Alphanumeric Mandatory entry of the customer number associated with the transactions to be displayed on the next window. However, entering an invoice number or purchase order number in the corresponding fields instructs the system to retrieve the Customer Number field based on the invoice or purchase order number entered. If the customer number is NOT known, it can be located in the Customer Search window by clicking on the 'SEARCH' icon. Additionally, with proper authority, the user may ADD, EDIT, mark INACTIVE or REACTIVATE a Customer record, by clicking on the SEARCH icon. Customers in the search window will only display if they have the same currency code as the bank selected on the Cash Receipt Entry/Update batch control window. Check Number/C/C Number 10 Alphanumeric If the system is using the Cash Receipt Check Entry/Update window, the Check Number field will be populated based on the entries made on the previous Cash Receipt Check Entry/Update window. If the Cash Receipt Check Entry/Update window was not used, the user will need to enter the Check Number on the Cash Receipt Entry/Update prompt window illustrated in Figure 42. Values should be entered in the currency displayed on the top of the Cash Receipt Entry/Update prompt window. Note: It is possible to access a customer s A/R account without a check, i.e., to mark off open credit memos against open invoices. If this is the case, the check number and check amount fields can be left blank. 49

56 If processing the payment using a credit card, leave this field blank and click on the CREDIT CARD button; the Credit Card window will display. Once the payment has been processed on the Credit Card window this field will be populated with the payment type code and the last three digits of the credit card number. The field will be protected and editing will be prohibited. Check Amt/C/C Amt 11.4 Numeric If the system is using the Cash Receipt Check Entry/Update window, the Check Amount field will be populated based on the entries made on the previous Cash Receipt Check Entry/Update window. If the Cash Receipt Check Entry/Update window was not used, the user will need to enter the Check Amount on the Cash Receipt Entry/Update prompt window illustrated in Figure 42. Values should be entered in the currency displayed on the top of the Cash Receipt Entry/Update prompt window. If processing the payment using a credit card, leave this field blank and click on the CREDIT CARD button; the Credit Card window will display. Once the payment has been processed on the Credit Card window this field will be populated with the amount charge to the credit card. The field will be protected and editing will be prohibited. Remarks 20 Alphanumeric This is an informational field, used to enter text that will aid in the clarification of this transaction. Remarks entered here will print on the cash receipt proof and update lists. Terms Display Field System-generated display field. This field will only display if the Cross Applications Accounts Receivable Interface check box Display Terms on Cash Receipt Header Window is selected (checked) for YES. Once a customer number has been selected, click on the ENTER icon and the terms for the customer number selected will display. The terms represent the payment terms that have been set up for the selected customer in the Customer Master File. Program Functions Clicking on the CREDIT CARD button prompts the display of the Credit Card window allowing the user to process the cash receipt entry with the use of a credit card. This function is available provided credit card processing has been established for the selected company in the Cross Applications Customer Orders Interface via the CREDIT CARD button. This function is disabled if the bank associated with the cash receipt batch has been established with a foreign currency; i.e., the currency, in which the bank was established, is not the domestic currency for the company for which the cash receipt is being processed. See Credit Card on page 51 for additional information. 50

57 Credit Card Clicking on the CREDIT CARD button prompts the display of the Credit Card window allowing the user to process the cash receipt entry with the use of a credit card. This function is available provided credit card processing has been established for the selected company in the Cross Applications Customer Orders Interface via the CREDIT CARD button. This function is disabled if the bank associated with the cash receipt batch has been established with a foreign currency; i.e., the currency, in which the bank was established, is not the domestic currency for the company for which the cash receipt is being processed. Figure 43 Credit Card Window Enter the credit card information as prompted on the Credit Card window; payment amount, payment type, credit card number and expiration date. If the payment type code is NOT known, it can be located in the Payment Type Search window by clicking on the SEARCH icon. Only those payment types established with the same bank number as the bank assigned to the current batch will display in the Payment Type Search window. Click on the ENTER icon to continue. If voice authorization is required, click on the VOICE AUTH button. An additional field will display on the Credit Card window; the Authorization Number field will be available for entry. Figure 44 Credit Card Window Enter the authorization code and click on the ENTER icon to continue. A window will display notifying the user that authorization is in progress. Figure 45 Authorization Is In Progress Window 51

58 Once authorization has completed the following Credit Card Approval Code window will display. Figure 46 Credit Card Approval Code Window The Credit Card Approval Code window will display the currency code, as established for the customer selected, amount of the sale approved and the approval code. Click on the ENTER icon to continue. Once the Cash Receipt batch is posted the credit card will be charged. 52

59 Retail Point of Sale Daily Transaction Processing Credit Card Payments Retail Sales Entry Summary Window Credit Card Swipe Clicking on the CREDIT CARD (F10) button from the Retail Sales Entry summary window will display one of the following windows. Additionally, the cash drawer may open depending on the Open Drawer check box setting in the Payment Type Master File and the setting in the Cash Drawer field in the Store Master File via the REGISTERS button. If the CC# Scan field is set to Y for YES, for the current Register, in the Store Master File via the REGISTERS button, the following window will display. Figure 47 Credit Card Swipe Window Swiping the card will capture all the credit card data and process it through the credit card processor interfaced to S2K Enterprise. If not interfaced to a credit card processor the system will just capture the credit card information and process it as that payment type. The user will still need to process credit card transactions using the offline credit card processing terminal. Click on the ENTER button to continue. The following Authorization is in Progress window will display. Figure 48 Authorization Is In Progress Window Once authorization has completed the following Credit Card Approval Code window will display. Figure 49 Credit Card Approval Code Window 53

60 The Credit Card Approval Code window will display the amount of the sale approved and the approval code. Click on the ENTER icon to continue. The display will return to the Retail Sales Entry summary window. To print the invoice or credit ticket click on the PRINT INV/CR button. This will print the ticket and complete the transaction. If the credit card swipe failed on the Credit Card swipe window or, to manually enter credit card information, click on the MANUAL ENTRY button from the Credit Card Swipe window. See Manual Entry on page 55 for additional information. For information on Voice Authorization refer to page

61 Manual Entry If the CC# Scan field is set to N for NO for the current Register in the Store Master File, via the REGISTERS button, or by clicking on the MANUAL ENTRY button the following Credit Card information window will display. Additionally, if a credit card swipe failed, on the Credit Card swipe window, click on the MANUAL ENTRY (F11) button to display the following Credit Card window. Figure 50 Credit Card Window Enter the amount tendered, the type of credit card, the credit card number and the expiration date in the fields provided. The system default in the Type field is based on the entry in the Credit Card field in the Store Master File via the PAYMENTS button. If the type code is NOT known, it can be located in the Payment Types Search window by clicking on the 'SEARCH' icon. The Payment Types Search window will display a valid listing of available credit card types as maintained in the Payment Type Master File. Click on the ENTER icon to continue. The following Authorization is in Progress window will display. Figure 51 Authorization Is In Progress Window Once authorization has completed the following Credit Card Approval Code window will display. Figure 52 Credit Card Approval Code Window 55

62 The Credit Card Approval Code window will display the amount of the sale approved and the approval code. Click on the ENTER icon to continue. The display will return to the Retail Sales Entry summary window. To print the invoice or credit ticket click on the PRINT INV/CR (F7) button. This will print the ticket and complete the transaction. 56

63 Voice Authorization CC# Scan set to Yes If the CC# Scan field is set to Y for YES for the current Register in the Store Master File via the REGISTERS button, the following window will display. If the credit card is available but voice authorization is still required, i.e., the card is swiped and the credit card terminal displays the message Please Call for Authorization, click on the VOICE AUTH (F10) button on the Credit Card swipe window. Figure 53 Credit Card Swipe Window The Credit Card swipe window will redisplay with the Authorization Number field activated. Figure 54 Credit Card Information Window (Authorization Field Activated) Enter the authorization code in the Authorization Number field. Swiping the card will capture all the credit card data and process it through the credit card processor interfaced to S2K Enterprise. If not interfaced to a credit card processor the system will just capture the credit card information and process it as that payment type. The user will still need to process credit card transactions using the offline credit card processing terminal. 57

64 Click on the ENTER button to continue. The following Authorization is in Progress window will display. Figure 55 Authorization Is In Progress Window Once authorization has completed the following Credit Card Approval Code window will display. Figure 56 Credit Card Approval Code Window The Credit Card Approval Code window will display the amount of the sale approved and the approval code. Click on the ENTER icon to continue. The display will return to the Retail Sales Entry summary window. To print the invoice or credit ticket click on the PRINT INV/CR button. This will print the ticket and complete the transaction. 58

65 Voice Authorization CC# Scan set to No To process voice authorizations if the CC# Scan field is set to N for NO, for the current Register, in the Store Master File via the REGISTERS button, select CREDIT CARD (F10) on the Retail Sales Entry summary window, the following Credit Card window will display. Figure 57 Credit Card Window Click on the VOICE AUTH button on the Credit Card window. The Credit Card window will redisplay with the Authorization Number field activated. Figure 58 Credit Card Window (Authorization Field Activated) Enter the amount tendered, the type of credit card, the credit card number, the expiration date and credit card authorization code in the fields provided. The system default in the Type field is based on the entry in the Credit Card field in the Store Master File via the PAYMENTS button. If the type code is NOT known, it can be located in the Payment Types Search window by clicking on the 'SEARCH' icon. The Payment Types Search window will display a valid listing of available credit card types as maintained in the Payment Type Master File. 59

66 Click on the ENTER icon to continue. The following Authorization is in Progress window will display. Figure 59 Authorization Is In Progress Window Once authorization has completed the following Credit Card Approval Code window will display. Figure 60 Credit Card Approval Code Window The Credit Card Approval Code window will display the amount of the sale approved and the approval code. Click on the ENTER icon to continue. The display will return to the Retail Sales Entry summary window. To print the invoice or credit ticket click on the PRINT INV/CR button. This will print the ticket and complete the transaction. 60

67 Multiple Credit Card Payments Multiple Credit Card Payments for a single transaction can be processed by entering the amount the customer is paying with one card in the Amount field, and then swiping the credit card. The Retail Sales Entry summary window will redisplay. Click on the CREDIT CARD (F10) button to redisplay the Credit Card swipe window, the balance due will display in the Amount field. Figure 61 Credit Card Swipe Window Swipe the next credit card the customer wishes to use to complete the credit card transaction. 61

68 Debit Card To process an order with a Debit Card, click on the DEBIT CARD (F13) button, from the Retail Sales Entry summary window. Clicking on the DEBIT CARD (F13) button will display the Debit Card window. The cash drawer may open depending on the Open Drawer check box setting in the Payment Type Master File and the setting in the Cash Drawer field in the Store Master File via the REGISTERS button. The DEBIT CARD (F13) button will display provided RiTA Debit Card processing is being utilized. RiTA must be selected from the If Yes: Select Product drop down selection box in the Cross Applications Customer Orders Interface via the CREDIT CARD button in order for this button to be active. Additionally, a payment type of Debit Card must be established in the Payment Type Master File and set up for the current store in the Store Master File via the PAYMENTS button. Note: Debit card processing with PIN is only available for customers operating in a GUI environment due to Java code. Additionally, S2K Enterprise supports the following PINpad: VeriFone MX-870. Figure 62 Debit Card Window The Debit Card window will display the amount of the sale, defaulting from the Retail Sales Entry summary window. Swipe the debit card in the PINpad to process the debit card transaction. 62

69 Index A Access Customer Account without a Check, 49 Address Line 1, 6 Address Verification Service, 10; AVS, 11 Allow Refund of Cash, 23 Approval Amount, 34, 35 Approval Code, 42, 43, 44, 45, 52, 54, 56, 58, 60 AS/400 Toolbox, 30, 31 AT Records, 34, 37 AU Records, 37 Authorization, 1, 2, 10, 36, 41, 43, 45, 51 Authorization Code, 23 Authorization Expiration, 1 Authorization Required, 23 Automatic Re-Authorization For Backorders, 6 Available, 44, 45 AVS, 6, 33 B Backorder, 2, 6 Backorders, 1, 2 Bank Merchant ID, 14 Bank Number, 24, 28 Batch Status, 19 Buffer Reservations, 1 C Card Expiration Date, 1 Card Number, 1, 33 Cash, 25 Cash Drawer, 25, 53, 62 Cash Receipt, 48, 49 Cash Receipt Check Entry, 48, 49 Cash Receipt Entry, 49 Cash Refund, 23 CCFP9000, 37, 39 Check, 23, 24, 25 Check Amount, 49 Check Number, 41, 49 CLASSPATH, 30 Client ID, 12, 14, 15, 16, 17, 18, 19 Company Master File, 37 Company Number, 48, 49 Compile PFProJava.java, 30 Confirm Delete, 13, 21, 27 Copy PFProJava.java, 30 COSETLCL, 34, 35, 37, 39 Credi Card Processor, 5 Credit Card, 23, 24, 25, 53, 55, 59 Credit Card Approval Code, 42, 43, 44, 45, 46, 52, 53, 54, 55, 56, 58, 60 Credit Card Authorization, 1, 41 Credit Card Expiration Date, 41 Credit Card Information, 1 Credit Card Interface, 1, 3, 4, 5, 9 Credit Card Length, 1, 24 Credit Card Number, 41, 44 Credit Card Payment Records, 37 Credit Card Payment Type, 42, 43, 44, 45 Credit Card Processing, 1, 6 Credit Card Processing Log Inquiry, 41, 46 Credit Card Swipe, 53, 54, 55, 57, 59, 61 Credit Card Swipe Device Configuration, 8 Credit Card Swipe Failed, 54, 55 Credit Card Swiping, 1 Credit Card Terminal, 43 Credit Memos, 49 Cross Application Customer Orders, 1 Cross Applications Accounts Receivable Interface, 50 Cross Applications Interface Menu, 3 Cross Applications User Defaults Interface, 40, 41 CT Records, 35, 37 Currency, 41, 42, 43, 44, 45, 52 Customer Master, 50 Customer Master File, 41 Customer Order, 1, 3, 4, 5 Customer Order Interface, 4 Customer Orders File Maintenance Menu, 22 Customer Orders Interface, 5, 19, 41, 46 D Data File Encryption, 11 Data Queue Integration Method, 11 Days to Keep Authorization, 24 De-Allocate Inventory, 6 Debit Card, 62 Declined Authorizations, 1, 2 Delete Code, 28 Deposit, 24, 28 Deposit Amount, 1, 2, 34, 37, 40, 41, 42, 43, 44, 45 Deposit History, 40 Deposits, 24, 28, 40, 41, 46 Discount Percentage, 6 Display Spooled File, 18 Do You Have The Credit Card, 42, 44, 45 Dollar Amount, 6; Over Sale, 6 63 E ECI Compliant, 11 End of Day, 1, 2 Exclude from Internet, 24 Expiration Date, 1, 37, 44 Expired Authorizations, 1 F For An Expired Authorization Does The Order Go On Hold, 6 G General Ledger Account Number, 24, 28 H Hold Reason Code, 6, 37 Host Address, 10 How To Settle An Unsettled Batch, 39 I Integrated File System, 25 Internet, 30 Internet Merchant Account, 30 Invoice, 54, 56, 58, 60 Invoicing Cycle, 2, 37, 39 J Java Based Engine, 11 Java Developer Kit, 10

70 JCharge Processing, 36 JG Record, 37 Jobq, 30 L Land Merchant ID, 14, 20 M Manual Entry, 54, 55 Merchant ID, 13, 14, 20, 37 N Native Optimization Path, 10 O Open Drawer, 53, 62 Open Invoices, 49 Order Entry/Update, 1 Order Entry/Update Summary, 41, 46 P Partner ID, 10, 20 Password, 10, 20 Payflow Pro, 9 PayflowPro, 3 PAYFLOWPRO, 9 Payment Method, 22 Payment Type, 1, 22, 23, 24, 25, 26, 28, 40, 41, 53, 55, 59, 62 Payment Type Class, 25 Payment Type File Maintenance, 27 Payment Type Master File, 55, 59 Percentage: Over Sale, 6 Pick Tickets, 1 Please Enter Card Information, 42, 43, 44, 45, 51 Please Swipe Card, 42, 45 Post Settlement Report, 17, 18 Pre Settlement Report, 12, 15 Process Credit Card, 42, 43, 44, 45 R Rapid Internet Transaction Authority. See RiTA RC Records, 37 Reactivate, 6 Real Time or Batch Transaction Processing, 11 Re-authorize, 2 Re-Authorize, 2 Re-AUTHORIZE, 1 Re-Authorizing, 1 Record Information, 14, 21, 25 Register, 24, 28, 53, 55, 57, 59 Reservation Buffer, 1 Retail Point of Sale, 1, 24, 27 Retail Sales Entry, 24, 54, 56, 58, 60, 62 Returns with a Receipt, 23 RiTA, 11, 12, 14, 15, 16, 18, 19 RiTA Client ID Maintenance, 13, 20 RiTA Rejection Codes, 16, 19 ROI JCharge, 36 ROI Split Order Processing, 2 ROI Transaction File, 37 S Sales Ticket Number, 62 Settled Record, 37, 39 Settlement Manager, 12, 16, 18, 19 Settlement Process, 2, 37, 39 Settlement Success Response Codes, 8 Split Deposit Amount, 2 SSL, 11 Start JCharge, 36 Status Code, 24 Store Credit, 62 Store Number, 28 Subsystem, 30 T TCP/IP, 9, 11 TCP/IP Connection, 30 Thumbnail Image, 25 Toolbox For Java, 30, 31 TQSTAT, 32, 34, 35 Transaction Identifier. See TROUTD TROUTD, 18 U User ID, 10, 21 USRPORT, 32, 37, 39 V VAINEP, 30, 31 Validate Credit Card, 24 Validate Expiration Date, 24 VeriFone, 11, 16 VeriFone MX-870, 62 VeriSign, 1, 5, 9, 10, 20, 30, 31, 32, 33 VeriSign SDK: Software Developers' Kit, 9 Voice Authorization, 43, 44, 45, 57, 59 Z Zip Code, 6 64