Electronic Payments: ACH and Card Processing

Transcription

1 1. ELECTRONIC PAYMENT: ACH AND CARD PROCESSING DEVELOPMENT ACH: CHECK BY PHONE CARD PROCESSING - MANUAL ENTRY OR CARD SWIPE/READER BATCH POSTING - WEBACH; WEBCC; WEBPAY PRODUCT DEFINITION REPORTS, BANK ACCOUNT AND GL INTERFACE FILE(S) REQUIRED (FOR ACH ONLY) FedACHdir.txt FILE(S) GENERATED (FOR ACH ONLY) ElecPmts.txt ABS STANDARD FILE LAYOUT FOR ACH ONLY: ELECPMTS.TXT VENDORS AUTOSCRIBE (PAYMENT VISION) PAYMAXX PRO, LLC PAYTEK SOLUTIONS REPAY REQUEST A PRICE QUOTE USAGE REQUIREMENTS (IF ACTIVATING A WEB-BASED PROCESS FEATURE) DATABASE REQUIREMENTS FORM(S) REQUIREMENTS... 6 November 28, 2011 Page 1 of 8

2 1. Electronic Payment: Development Electronic Payments was developed to provide features such as a NACHA* text file, ACH Fee assessment, bank routing number and bank address verification. * NACHA is the National Automated Clearing House Association. ABS Electronic Payment Offerings have been expanded to include all of the following. Note: All options require a vendor or bank for processing; a list of approved vendors has been provided in section ACH: Check by Phone Branch initiates transaction in absvision with EEP absvision creates elecpmts.txt during Daily Initialization; branch uploads or transmits to vendor for processing For checking and saving account transactions 1.2. Card Processing - Manual Entry OR Card Swipe/Reader Branch initiates Card Not Present transaction in absvision with Electronic Payments (enter card information manually); no card reader or pin pad necessary with this option Payment is pushed to the Gateway through the abssterling web portal at the time the payment is made -OR- Work Order 15309; absvision v Branch initiates transaction in absvision with Electronic Payments / Card Swipe / Reader Payment is pushed to the Gateway through the abssterling web portal at the time the payment is made o Portal returns Pending: Accept or Pending: Declined Requires high speed internet for adequate speed Requires.NET Framework V (minimum) Requires branch to secure agreement with vendor and Business Services 1.3. Batch Posting - WEBACH; WEBCC; WEBPAY Transaction (ACH, Card, Recurring, One-Time) posted at the payment Gateway regardless of vendor Import transaction data into absvision (Batch Posting) o Requires high speed internet for adequate speed o NET Framework V (minimum) o Requires branch to secure agreement with vendor and Business Services NOTE: ABSVISION BLOCK PAYMENT FEATURE IS OFFERED WITH ACTIVATION OF ANY ELECTRONIC PAYMENT SERVICE. November 28, 2011 Page 2 of 8

3 2. Product Definition Electronic Payments is similar to the standard absvision Take Payment screen, but there are identifiers to let a user know where they are Reports, Bank Account and GL Interface This feature includes separate Electronic Payments and Electronic Daily Drawer reports. It also supports the additional bank account for bank adjustments & GL Interface. o The Daily Payments report continues to show ALL payments (so there s one audit trail and total for all). o The Electronic Payments report shows only Electronic Payment transactions File(s) Required (For ACH Only) FedACHdir.txt The purpose of this file is to validate bank routing number and bank name, address and phone number for accuracy (WO 14311). This verification file requires additional files in windows\system32 folder, both provided by the ABS setup. Branches can download this file from within absvision: File Download E-Payments Routing File(s) Generated (For ACH Only) ElecPmts.txt This file is created by absvision during the Daily Initialization process. The purpose of this file is to report electronic payment transactions to a third party vendor for processing. See next section for ABS standard file layout. November 28, 2011 Page 3 of 8

4 2.4. ABS Standard File Layout for ACH Only: ElecPmts.txt Field Name Field Type Required Max Field Length Field Description Customer Last Name String Y 30 The last name of the customer. This is not a required field If the ACH SEC Class Code is ARC or RCK. NOTE: This field represents the bank account owner; this MAY NOT be the borrower law change will require this information. Customer First Name String N 30 Customer Middle Name String N 30 These fields represent Customer Address (Line 1) String N 40 the bank account owner Customer Address (Line 2) String N 40 information and may NOT Customer City String N 25 be the borrower on the loan. Customer State String N 2 Customer Zip Code Zip Code N 9 Zip or Zip + 4 (without dashes) Customer Home Phone Phone N 15 Area code is required. Customer Work Number Phone N 15 Area code is required. ABA Routing Number Numeric Y 9 Must be nine digits. Bank Account Number String Y 17 Checking or Savings Account Number Bank Account Type String N 1 "C" for Checking, "S" for Savings; Default if not specified is Checking. Transaction Amount String - Currency Y 13 Decimal point may be explicit, or implicit in which case the last 2 digits are implied to be the decimals. Debit Credit Type String N 1 "D" for Debit, "C" for Credit. Default is Debit, if not specified. Settle Date Date Y 10 Accepts the following formats: MM/DD/YYYY;MMDDYYYY;YYYYMMDD;MMDDYY Transaction Date Date N 10 The original capture date of the transaction. If this is not provided, it will default to the date of the upload. Transaction formats supported are the same as in the Settle Date. Payee Code String N 3 If not available, defaults to merchant default Payee. Check Serial Number String N 8 The check serial number required for ARC and RCK transactions only. Agent Code String N 5 Code used optionally to identify originating agent. Transaction Fee Amount String - Currency N 13 ACH Class Code String N 3 Valid values include: PPD; RCK; TEL; WEB; CCD; ARC If this is not available in the file, the administrator can setup a default ACH class code. It is recommended, however, that the file specify the class code explicitly. Transaction Reference ID String N 30 An identifier for the transaction in the source system Account Reference ID String N 30 An identifier for the customer account in the source system. Used in cases where the source system allows multiple accounts for a single customer. Customer Reference ID String N 30 An identifier for the customer in the source system. Transaction Reference Note String N 50 Additional note related to transaction in source sys. Account Reference ID String N 50 Additional note related to transaction in source sys. Customer Reference ID String N 50 An additional note related to the customer record in the source system. User Def 1 String N 50 User defined field; data from source system User Def 2 String N 50 2 nd user defined field; data from the source system. November 28, 2011 Page 4 of 8

5 3. Vendors The following Vendors have been approved for automated payment processing. If you re currently working with a vendor not on this list, please let us know. We ll make every attempt to get them approved as an ABS vendor Autoscribe (Payment Vision) Sean Fleming, Key Account Executive Direct: sfleming@autoscribe.com 3.2. Paymaxx Pro, LLC Jon Leedom, Marketing and Accounts Coordinator Direct: john@paymaxxpro.com 3.3. PAYTEK Solutions Stacey Baxter Direct: x242 sbaxter@payteksolutions.com 3.4. REPAY Pam Hendee Direct: phendee@repayonline.com November 28, 2011 Page 5 of 8

6 4. Request a Price Quote To receive a price quote contact Business Services at or via at BusinessServices@alliedbiz.com Usage Requirements (if activating a web-based process feature) High speed internet for adequate speed Agreement with payment processing vendor; ABS discount applies for selecting one of our preferred vendors API for vendor not on the approved list.net Framework V (minimum) loaded to all machines that will process transactions Business Services Agreement 4.2. Database Requirements A Business Services Analyst will be assigned to: Obtain current branch data Assist you with completing the Electronic Payments Questionnaire (last two pages of this document) 4.3. Form(s) Requirements n/a November 28, 2011 Page 6 of 8

7 Electronic Payments Questionnaire (pg 1) For Internal Use Only O P T O Other Basic E-Pay D Draft ACH Check by Phone C Credit Manually enter card data into absvision S Swipe Card Reader Batch Import V E N D O R Autoscribe (PaymentVision) G Paymaxx Pro W Paytek Solutions A REPAY Y NOTE: Annual Maintenance applies if non-approved vendor selected. InterPoynt Payment Vision (Autoscribe) Paytek Solution USAePay Bank Accounts (optional) Will you use a separate bank account for these payments? If yes, please provide the following: Bank Name: Account Number: General Systems Information There is an option to have the system ask you the following question each time you enter the E-Payment screen: Do you want to continue in Electronic Take Payments?. This serves as a reminder to branch personnel that they have selected this option. Do you want this option active? Convenience Fee (if applicable) NOTE: Not allowable in all states. Not allowable on all payment types. NOTE II: absvision requires a unique GL number used ONLY for the Convenience Fee. The GL number cannot be used or associated with any other transaction in the system. If a GL number is not set in the database, the fee cannot be charged. Fee Amount: $ Fee G/L #: Chart of Accounts for ABSGL or GL Interface ONLY We need to know what GL number you will be using for the Electronic Payment Deposits. This GL number can be your regular deposit GL number if you do not want a separate number used for Electronic Payment Deposits. NOTE: GL Interface will be modified as needed. GL # for Electronic Payment Deposits: Is the GL # to be used ONLY for Electronic Payment Deposits? November 28, 2011 Page 7 of 8

8 Security Levels Electronic Payments Questionnaire (pg 2) ELECTRONIC PAYMENTS [MENU Contract Electronic Payments] This setting controls which level of user security can access the Electronic Payments icon (green phone). The default Security Level setting for Electronic Payments is 90. What Electronic Payments Security Level do you want set? REVERSALS [Form E-TakePayments Allow Negatives] This setting controls whether or not negative amounts can be entered in Electronic Take Payments (green phone icon). The default Reversal Security Level is the same as that for Take Payments. What Reversal Security Level do you want set? ELECTRONIC DRAWER BALANCING AND ELECTRONIC DEPOSIT POSTING [Form Checkbook AdjustBal] This setting controls access and posting from the following menu options: (1) Electronic Drawer from Bookkeeping icon; (2) Electronic Miscellaneous Payments from Bookkeeping icon; (3) Adjustment from Checkbook The default AdjustBal security level is 70. What Electronic Drawer Balancing and Electronic Deposit Posting Security Level do you want set? Reverse Reason Code There are three standard Reverse Reason Codes defined: Invalid Account Number (standard default) Invalid Routing Number Refused What Reverse Reason Code do you want set as the default: Additional Reverse Reason Codes (if any): Reports We have two new reports for the Electronic Payments in the Bookkeeping menu Electronic Daily Drawer and Electronic Payments. Report Activate Daily Chain Monthly Chain Electronic Daily Drawer Electronic Payments Block Payment Activation (optional) Would you like to activate the Block Payment feature? This option is available in Edit Contract Block Payment. You must have a security level equal to or above "File Maintenance", "Main Menu", "Security Levels" in order to set, unset or post a payment on a contract with Block Payment set. IF you attempt to post a payment on a contract with Block Payment set and you do not have a high enough security level then you will be given a chance to override. Benefits include, but are not limited to: Make sure customer talks to the manager before making a payment Alert branch personnel to a pressing issue before a payment is applied November 28, 2011 Page 8 of 8