Section 11
Payment Types

This table contains a list of the valid payment methods you will be permitting your cashiers to process. These typically include methods such cash, checks, credit cards, wire transfers, etc. Some Quadrant clients also accept other methods of payment such as coupons, food stamps, gift certificates, etc.

In addition, this table controls whether the drawer opens for each payment method, whether endorsements are performed (checks), etc.

Each field in the table is listed, along with a short description, below:

1. METHOD
   
   This is a code you assign for your various payment methods. The system is hard-coded to use CASH, for cash type payments, and CK for checks, but these methods must still be in the table.
2. DESCRIPTION
   
   This is the plain text description of the METHOD code. For example, you might have a METHOD set to WT and Wire Transfer as the description.
3. OPEN_DRAWER_FLAG
   
   This is a check-mark type setting. If checked the program will open the cash drawer (if attached) for the particular METHOD with which it is associated. If unchecked, the drawer will not open. The drawer will always open anytime CHANGE is due on a receipt, since it knows CHANGE is always CASH.
4. EXCHANGE_RATE_IN
   
   Future use
5. EXCHANGE_RATE_OUT
   
   Future Use
6. CREDIT_CARD_VERIFY
   
   If you are using CHARGEITPRO integrated credit card processing this setting must be set to C in order to link the method to the CHARGEITPRO module. This will happen when you advance to the REFERENCE_NUMBER field after you have selected a method and entered the payment_amount on the payment entry screen. Typically, this will be set on just a couple of entries, such as CC [Credit Card] and DC [Debit Card]. Others, such as CASH, CHECK would be left blank.
   
   Any value other than C will be ignored as far as linking to the credit card processing functions.
7. METHOD_GROUP
   
   This field is used to define what method_group the particular method should be assigned to when the cash recap report is printed. Each such group will be listed separately and subtotaled, by deposit bank when the Payment Totals by Bank is printed.
   
   The method_group CASH is always associated with the payment method CASH, regardless of what setting you may assign in this table. All other payment methods can be assigned to any group you like. For example you might assign payment methods CK and MO to the method_group CHECKS, and payment methods CC-VISA, CC-MASTERCARD and CC-AMEX to the method_group CREDITCARD.
   
   If you elect to print the detail of the various payments, these settings will control what section of the report the payments are listed under, and what sub-totals you get.
   
   As noted above, regardless of what method_group you may assign to cash in the table, the program will internally consider CASH to be in the CASH group. This is done so that proper calculations for cash payments (total cash received less change given out) can be performed. ALL CASH PAYMENTS are considered to be associated with bank #1. If the assigned to the OTHER group (unless the method is CASH.)
8. ENDORSE_MEDIA
   
   This setting controls whether or not endorsements are performed for you various METHODs. In most cases, you only endorse checks or similar items such as money order, travelers checks, etc.
9. BANKCODE Future Use
10. REFNUMREQUIRED
    
    This setting is YES, NO, or OPTIONAL. If set to YES, the program will require that you enter a reference number for the associated METHOD. This would be something like a check number for a CK type payment, or an approval number for a credit card type payment.
11. REFNUMCAPTION
    
    If the REFNUMREQUIRED flag is set to YES or optional, then you need to set a value in the field that prompts the operator to enter a specific type of reference number. For example, # for a CK method, APPROVAL# for a CC (Credit Card) type method, etc.
12. PMT_TYPE_CODE
    
    This is a single digit or letter that is used by the Payment Entry screen in association with the valid list of payment methods for each Tran_Code. Please refer to the PMT_TYPES_LIST description in the Tran Codes maintenance section for further details on how to set this field up.
    
    They are required to be set up if you want to restrict the METHODs that are acceptable for a give TRANCODE.
    
    Each Payment Method should be assigned a unique 1 letter (A-Z) or 1 digit (0-9) code. If you have not created these the program will attempt to automatically assign one for you as a starting point. The way it does this is as follows:
    
    1. First, it will look for a value that is not in the valid list of possible values (A-Z, 0-9).
    2. If the value is not one of those it will then attempt to assign to code as the first left of the payment method. For example, suppose payment method WT has not been assigned a payment type code. The program will try to assign W to this field. If W is already in use by another method it will then start a letter A and try to assign A to the code. If A is in use it will try B, and so on until it finds one that is not used by any other method. When it is all done doing this, you will then have a unique one-letter value in EACH of the PAYMENT TYPE CODE fields.
    3. The program will make sure there are valid codes assigned each time it starts, from any workstation. After this has been done, the codes will not automatically be changed by the program unless you manually assign a value that is not valid via table maintenance.
    4. Note that if you have manually assigned the same one letter code to more than one payment method, the program will eliminate these duplicate codes
    5. If you don't like the values it has assigned, then you can simply type in different values manually. You should make the new code you assign is not used by any other payment method.
13. REFNUM_EDIT_MASK
    
    The REFNUM_EDIT_MASK field allows you to cause the program to force the entry of an reference number in a specific format defined by the EDIT_MASK rule you place in this field. This is active only if the REFNUMREQUIRED flag is set to YES or optional.
    Refer to the EDIT MASKS table documentation for details on how to set up the edit masks.
14. PAYER_NAME_EDIT_MASK
    
    The PAYER_NAME_EDIT_MASK field allows you to cause the program to force the entry of an payer name in a specific format defined by the EDIT_MASK rule you place in this field. This is active only if the PMT-PAYER-NAME-REQUIRED setting is set to YES in the PAYMENT options table.
    Refer to the EDIT MASKS table documentation for details on how to set up the edit masks.