Use this program to define setting for the various Card Brands accepted by your rental operation.

NOTE: Thermeon Customer Support will set up the records and users should not change them.

To access the Edit Card Definitions program, type EDITCC (RET) at any menu "OPTION:" field or the appropriate line number on the CCard Control Record Sub Menu on the Rental Control Files Menu. The screen will then display:


OPTION: __ EDIT CARD DEFINITIONS

1 Card Brand
2 Eff date
3 Description
4 FOP Name 18 Placeholder? N
5 Handler program 19 Underauth: New auth? N
6 Check digit? 20 Can Cancel Sale? N
7 CC Proc. Flag 21 Can Preauth Sale? N
8 Allowable Pct 22 Reauth Required? N
9 Require Security ID(Y/N) 23 Settle Immediately N
10 Clearing House 24 Refund Req Auth N
11 Batch with others (Y/N) 25 Load Card on Swipe
12 Do DCC 26 Capture over auth
13 S Sub window
14 Charge Fee Code
15 Chg fee on Debit
16 Auth Expire Days
17 Payback



1SAVE 2NEXT 3ERASE 4DELETE 5BACKUP 6 7HELP 8NXT PAGE


Enter data as follows:

1. CARD BRAND

Enter the Card Brand as set up in Edit Card Brand Records.

EXAMPLE: Type MC (RET)
2. EFF DATE

Enter the effective date for this record.

EXAMPLE: Type 010118 (RET)
3. DESCRIPTION
 Enter the description for the brand entered in Field 1.

EXAMPLE: Type MASTERCARD (RET)
4. FOP NAME

Enter the FOP (Form of Payment) Code for this credit card as previously set-up in the Customer File.

EXAMPLE: Type MC (RET)
5. HANDLER PROGRAM
 For users doing Electronic Draft Capture, enter the name of the program that is used to submit authorization requests for this credit card.

EXAMPLE: Type FDC (RET)
6. CHECK DIGIT?

Many credit cards have a built-in method for checking for errors when entering the card number. This is done by most U.S. credit card companies with a mathematical algorithm called "Double-Add-Double MOD 10". This field asks whether or not the Double-Add-Double MOD 10 logic should be applied to the credit card being defined.

Y = The credit card being defined is one of the domestic U.S. credit cards listed on the chart on the previous page or it is a card whose number uses "Double-Add-Double MOD 10" check digit logic. Therefore, each card number entered into CARS+ will be checked for data entry errors.

N = Do not apply the check digit logic test to this credit card.

EXAMPLE: Type Y (RET)
7. CC PROC. FLAG
 Enter one of the following:

1 = Auth Only: Automatic credit card approvals will be requested from the Reservation, RA Open and RA Close screens.

2 = Auth/Settle: In addition to approvals, this credit card will be settled at the end of the day by the CARS+ Electronic Draft Capture programs.

EXAMPLE: Type 2 (RET)
8. ALLOWABLE PCT

Some credit cards allow the authorized amount to be short of the actual charges by a specified percentage at the time of RA Close. If this credit card allows this, enter the percentage by which the authorization can be short.

Math involved:

The payment amount is multiplied by this percentage. The result is added to the authorization amount. The transaction is allowed is the total is equal to or more than the payment amount.

Example:

Authorized amount = $250

Payment amount = $292

Allowable percentage = 15%

Payment amount $292 * .15 = 43.80

Authorized amount $250 + 43.80 = 293.80. Therefore, payment of $292 is allowed.

EXAMPLE: Type 5 (RET)
9. REQUIRE SECURITY ID (Y/N)

This field should only be used if you are using the Electronic Draft Capture (EDC) feature of CARS+.

In addition to the embossed credit card number, many credit cards have a 3 or 4 digit non-embossed number printed on the face or back of the card. This is the Security ID number (called the CVV or CID number).

This field is used to designate whether or not a security ID number from the credit card must be entered when a credit card is manually keyed in rather than being swiped in a transaction screen (Reservations, RA Open, RA Close, etc. but NOT Customer File Update, Edit Corporate Accounts, etc.). For a more complete description of this feature, see the chapter Overview - Electronic Draft Capture for North America.

Enter:

Y = Yes, when this FOP is manually entered into any transaction screen, call the Security Pop-up window and ask for the security code and the billing zip code for this card.

N (or blank) = No, do not call the security Pop-up when this FOP is manually keyed into a transaction screen.

EXAMPLE: Type Y (RET)
10. CLEARING HOUSE
 If you are using Electronic Draft Capture through CARS+, enter the code for the logic to be used to authorize and settle this type of credit card. Thermeon's Customer Support Dept will set up this field.
11. BATCH WITH OTHERS (Y/N)

If you are using Electronic Draft Capture through CARS+, this field designates whether or not this type of card must be settled in its own batch. Enter:

Y = Yes, this card can be combined with other types of cards cleared by the same clearing house.

N = No, this card must be settled in its own unique batch with your credit card clearing house.

EXAMPLE: Type Y (RET)
12. DO DCC
 This field is reserved for certain Thermeon customers who make use of the CARS+ DCC feature. Other users should skip this field.
13. S SUB WINDOW
 Use this field to specify if certain cards are entered in the Main window of RA Open (on the FOP line) or if they must be entered in the Special Documents subwindow. Enter:

Y = Yes, this card can only be entered using the Special Documents subwindow.

N (or blank) = No, this card can be used in the FOP field on the main window of RA Open.

EXAMPLE: Type Y (RET)
14. CHARGE FEE CODE

Note: The system must be configured by Thermeon’s Customer Support Dept. in order for this field to appear.

This field is used by those operations that charge the renter a processing cost for using credit cards as either a deposit or payment on a rental. In this case, an Optional Item is set up to define how the fee is calculated. Enter the Optional Item Code in this field.

EXAMPLE: Type CCFEE (RET)

User tip: Refer to the chapter of the manual titled Overview- Credit Card Processing Fee for details on how to set up and use this feature.
15. CHG FEE ON DEBIT
 This field is used in conjunction with the previous one. This field is used to specify if the fee should be applied to different types of cards. Enter:

N = No, the option defined in Field 14 WILL NOT be applied to the transaction if the card is defined as a Debit Card. The fee is only applied to Credit Card transactions.

Y (or blank) = Yes, the option in Field 14 will be applied to both Debit and Credit Card transactions.

D = Debit card only, the option in Field 14 will only be applied to Debit Card transactions.

EXAMPLE: Type Y (RET)
16. AUTH EXPIRE DAYS
 For vehicle rental merchants, a pre-authorization may be limited to a certain number of days. Enter in this field the number of days a pre-authorization is valid.

When opening a RA, if the length of the rental exceeds this value, the card cannot be used to pre-auth the rental. It must be used as a deposit.

If a shorter rental is extended beyond this number of days, the limit on the pre-auth days must be kept in mind. Rentals with pre-auths that exceed the number of days may be subject to charge backs for no authorizations unless the authorization is completed with a deposit on or before the last day it is valid. Another authorization can then be obtained for the next period of days.

EXAMPLE: Type 14 (RET)
17. PAYBACK
 This field is used for American Express cards that have a Payback membership number embedded in the magnetic stripe (not all AX card ranges support Payback). For cards of this nature, enter the Frequent Traveler Code "PB" which must already be defined in Edit Frequent Traveler Codes for the Payback program.

EXAMPLE: Type PB (RET)

Refer to the chapter Edit Payback Control Record for more details.
18. PLACEHOLDER?

Certain systems handle credit cards in such a way that the actual credit card number is not sent to or present in CARS+. The card number entered on the CARS+ transaction is not the true card number nor a reference, but rather simply a "placeholder". The 'placeholder' credit card number range must still be set up in this field in order for CARS+ to accept it. Enter:

Y = Yes, this card number is really only a placeholder. There is not an actual credit card behind it. Card numbers falling in to this range cannot be manually entered on an transaction.

N (or blank) = No, the CARS+ card number is a true card number or a reference to the card number.

EXAMPLE: Type (RET)
19. UNDERAUTH: NEW AUTH?

IN RA OPEN: This field controls how the credit card authorizations are handled when the original pre-authorized amount is not enough to cover the total charges on an edited RA. Enter:

Y = Yes, a new authorization must be made for the new total charges on the RA. The previous authorization must be deleted by pressing F3 (Erase) while the cursor is on the authorization fields of the Main Window.

N (or blank) = No, an incremental authorization can be made for the difference between the new RA total and the previous authorized amount.

IN RA CLOSE: This field controls how the credit card payment is handled at Close when the pre-authorized amount is not enough to cover the total charges on the RA. Enter:

Y = Yes, a new authorization must be made for the amount above what was pre-authorized. A payment will be entered for the pre-auth amount and a second payment record will be created for the balance.

N (or blank) = No, an incremental authorization can be made for the total.

EXAMPLE: Type (RET)
20. CAN CANCEL SALE?

This flag enables or disables CARS+ from trying to cancel a settlement. Enter:

Y = Yes, the card handler has the ability to cancel a settlement.

N (or blank) = No, do not attempt to cancel a settlement.

EXAMPLE: Type (RET)
21. CAN PREAUTH SALE?

The flag enables or disables RA Close from trying to settle an authorization when saving with F1. Enter:

Y = Yes, the handler can accept a pre-authorized sale type transaction (a settlement when closing a RA with F1).

N (or blank) = No, settlement will happen at posting/settlement time.

EXAMPLE: Type (RET)
22. REAUTH REQUIRED
 This flag means that it is required to reauthorize an authorization before settling it. Enter:

Y = Yes, one is required to reauthorize an authorization before settlement.

N (or blank) = No, one is not required to reauthorize before settlement.

EXAMPLE: Type (RET)
23. SETTLE IMMEDIATELY
 This flag indicates if you wish to settle deposits and payments immediately or not. Enter:

Y = Yes, settle deposits immediately.

N (or blank) = No, merely ask for an authorization, and get the settlement after posting.

EXAMPLE: Type (RET)

Note: Only select this if the handler is capable of "sales".
24. REFUND REQ AUTH
 This flag indicates whether the bank requires refund authorization prior to allow for refunds.

Y = Yes, the bank requires prior refund authorization.

N (or blank) = No, the bank does not require authorization prior to allow for refunds.

EXAMPLE: Type (RET)

Note: Only select this if the handler is capable of "sales".
25. LOAD CARD ON SWIPE This flag indicates if you wish to have Cars+ automatically load the credit card number when the swipes are in use. Enter:

Y = Yes, Load the credit card automatically when the swipe is used.

N (or blank) = No, do not load the credit card.

EXAMPLE: Type (RET)

Note: Only select this if the handler is capable of "sales".
26. CAPTURE OVER AUTH
 This field is ONLY for Hertz corporate run locations who use STRIPE to authorize credit cards. Place a "Y" in this field for the Card definition record for American Express. FOR ALL OTHER CARD BRANDS LEAVE THIS FIELD BLANK. Because American Express can not issue incremental authorizations, Hertz has negotiated with AX that they will accept for settlement a transaction whose amount is greater than the original auth amount. It causes the system to treat additional original auths as incremental auths.

WARNING: Use of this field by other users or for other card brands besides AX may cause transactions to be declined when settling.


PRESS "F1"AT "OPTION:" TO SAVE THE RECORD.

Additional programs:

Edit Card Type Records

Edit Card Brand Records

Edit BIN Range Records