Page tree
Skip to end of metadata
Go to start of metadata
On This Page

Overview

This page is intended to walk a user through a detailed explanation of the FasCard Test and Trust logic and how to configure the feature.

Test and Trust Feature Logic

The Test and Trust feature is an authorization mode that charges retail customers a small fee when using their credit cards to "Test" they have a legitimate bank account to complete transactions.  This small fee is $0.29, and cannot be changed.  Once the card is charged the $0.29 and is successful, the card is validated, and the test amount is voided. Now, the customer can spend up to a designated "Trust" amount and will not be charged the 'Test" amount again until the system resets.  The reset occurs when the two-hour idle time has passed with no activity from the same customer.  Once the two hours has passed, the system captures the amount the customer has spent and the system will reset, and be ready to accept the customer's next spending activity.

If at any time the FasCard system attempts to capture the amount a customer has spent, but fails (See below Failed Scenarios #2), the lost amount will show on the Credit Card Captures Report under the Reports tab in the FasCard Admin site.)

Where to access the Test and Trust Authorization mode

This feature is found in the Server Management Screen.

  1. To access this function, log into your FasCard admin site.
  2. Select the Setup tab to access the server management screen.
  3. Scroll down to the Credit Card section.

The fields

There are three fields that are utilized when the Test and Trust mode is selected. The fields are Authorization Mode, Auth/Hold Amount, and Trust Amount.  The fields are described below.

    • Authorization Mode - This allows an owner to choose which type of authorization mode to use for their entire system.  When Test and Trust mode is selected,  the customer's card is temporarily charged a pre-set amount of $0.29 to test that the card is valid. If the test is successful, the $0.29 is voided, and the customer can now spend up to the designated Trust Amount in a set of transactions. 
    • Authorization/Hold Amount - This field is primarily used when the Pre-Auth mode is selected.  However, it can be used while in Test-and-Trust mode if a customer's card is charged the test amount, $0.29 and fails.  When the customer's card is charged the $0.29 test amount and fails, the system reverts to the Pre-Auth mode for that specific card for the day.  Any subsequent swipes for that day must be pre-authorized before transactions can be accepted.  This Auth/Hold amount must be set to accommodate this instance.  The Auth/Hold amount must be greater than or equal to the highest priced machine.  It cannot be set to $0.
    • Trust Amount - This is the amount a customer can spend up to in a set of transactions.  This field is only displayed when the "Test and Trust" mode is selected and saved.  This field is not the same as the Max Daily Auth Amount.

How to Configure the Test and Trust and Auth/Hold fields

Authorization mode

Choose the Test and Trust mode from the drop-down menu and click save so that the trust amount appears.

Auth/Hold Amount

Set this amount to serve as a pre-authorization hold in the event a customer's card is declined while in Test and Trust mode.  When setting the Auth/Hold amount, it must be greater than or equal to the highest priced machine and cannot be set to $0.

 

Even though the Auth/Hold Amount field is primarily used when Pre-Auth mode is selected, it is activated in the Test and Trust mode when a customer's card is declined.  When a customer's card is charged the $0.29 test amount and is successful, but fails during the capture of the trust amount, the system reverts to the Pre-Auth mode for that specific card for the day.  Any subsequent swipes of that card for that day must be pre-authorized before transactions can be accepted. This Auth/Hold amount must always be set to accommodate this instance.  

Trust Amount

Set this amount as the maximum amount a customer can spend in a set of transactions.  After their card has been charged the tested amount of $0.29 and is successful, they can spend up to this amount.  When setting the Trust Amount, it needs to be greater than or equal to the Auth/Hold amount.  (If the Trust amount is less than the Auth/Hold amount, the system will revert to the original Pre-Authorization logic.)

Click Save.

Examples of Test and Trust Configurations and Customer Spending Scenarios

Successful Scenarios

Example 1

Mode:  Test and Trust

Auth/Hold Amount:  $20

Trust Amount: $40

  1. Customer swipes their credit card
  2. $0.29 Test Amount is approved and voided, and the customer can now spend up to the Trust Maximum Amount of $40.
  3. Customer spends $32.00 total.
  4. Customer doesn't spend any more money.
  5. The 2-hour idle time expires.
  6. Customer card is charged the total amount of $32.

Example 2

Mode:  Test and Trust

Auth/Hold Amount:  $20

Trust Amount:  $40

  1. Customer swipes their credit card
  2. $0.29 Test Amount is approved and voided, and the customer can now spend up to $40
  3. The customer spends $38 and attempts to purchase another $4 to put them at $42.
    1. The system captures the amount spent so far, $38, and if successful, then charges a new "test" amount of $0.29.  If the $0.29 is successful, the customer can continue their purchase of $4.
  4. The customer doesn't spend any more money.
  5. 2 hour idle time expires
  6. The customer's card is charged the 2nd amount of $4 for a total of $42.

Failed Scenarios

Example 1

Mode:  Test and Trust

Auth/Hold Amount:  $20

Trust Amount:  $40

  1. Customer swipes their card
  2. $0.29 Test Amount is charged, and declined
  3. FasCard then reverts to pre-auth-only mode for this credit card for the rest of the day
  4. Any subsequent swipes of this card must be Pre-Authorized for $20 (This is the Auth/Hold Amount) before transactions will be accepted.

Example 2

Mode:  Test and Trust

Auth/Hold Amount: $20

Trust Amount:  $40

  1. Customer swipes card,
  2. $0.29 Test Amount is approved and voided, and the customer can now spend up to $40
  3. Customer spends $32.00
  4. 2-hour idle time expires with no additional spending activity
  5. System attempts to capture the$32.
  6. Customer's card gets declined the $32 charge
    1. FasCard begins to decrement the $32 charge by $3 and retries
      1. If successful, store owner recovers $29 but loses $3 
      2. If the $29 fails, FasCard decrements charge by another $3 and retries
        1. FasCard will keep attempting to capture the charge.  If the decreasing attempted charge falls below $5, FasCard stops retrying and store owner loses the full amount of $32.
        2. The failed capture amount will display on the Credit Card Captures report. 

Other Resources

FasCard Credit Transaction Processing

Authorization Hold



  • No labels