Difference between revisions of "Rush Approval Mode"

From Payment Processing Software Library
Jump to: navigation, search
(Function)
(Function)
Line 6: Line 6:
  
 
==Function==
 
==Function==
Rush Approval Mode is optional transparent offline mode that allow POS to continue taking credit cards without delays during connectivity failures. After a set number of unsuccessful connections, rush mode is initiated and the credit card transactions are recorded offline for later processing. A countdown timer is initiated to keep the transactions from retrying the connection for some time to speed up the processing and avoid the timeout delays.  At the expiration of the timer, the connection is retried and rush mode is exited if connection is successful.  Rush mode is optional and has to be [[#Enabling|enabled and configured]] to become active.  
+
Rush Approval Mode is an optional transparent offline mode that allow POS to continue taking credit cards without delays during connectivity failures. After a set number of unsuccessful connections, rush mode is initiated and the credit card transactions are recorded offline for later processing. A countdown timer is initiated to keep the transactions from retrying the connection for some time to speed up the processing and avoid the timeout delays.  At the expiration of the timer, the connection is retried and rush mode is exited if connection is successful.  Rush mode is optional and has to be [[#Enabling|enabled and configured]] to become active.  
  
 
→ '''No interface changes are required on the POS side''', as the POS is receiving temporary [[Credit_Card_Glossary#Auth_Code|Authorization Codes]]. Once the connection is back up, the logged transactions are reviewed in [[CreditLine ViewModify Dialog]] and can be retried or [[Credit_Card_Glossary#Forced_Authorization|Forced]] through. At this point,[[Credit_Card_Glossary#Auth_Code|Authorization Codes]] are replaced with live [[Credit_Card_Glossary#Auth_Code|Authorization Codes]].  
 
→ '''No interface changes are required on the POS side''', as the POS is receiving temporary [[Credit_Card_Glossary#Auth_Code|Authorization Codes]]. Once the connection is back up, the logged transactions are reviewed in [[CreditLine ViewModify Dialog]] and can be retried or [[Credit_Card_Glossary#Forced_Authorization|Forced]] through. At this point,[[Credit_Card_Glossary#Auth_Code|Authorization Codes]] are replaced with live [[Credit_Card_Glossary#Auth_Code|Authorization Codes]].  

Revision as of 00:44, 11 September 2007

This article is part of the
Payment Processing Software Library

Categories

Get it...

Credit Card Software
Download

Install it...

Installation
Upgrade & Migration

Connect to it...

Point Of Sale Integration

Set it up...

Quick Start Guide
Setup
Processor Setup

Licensing

Learn to use it...

Manual & User Guide
Knowledge Base
Frequently Asked Questions
Compliance Guide
Merchant Account Rates
User Interface Guides

Fix it...

Errors & Troubleshooting
Knowledge Base
Corrupted Install Repair

Get Help...

Contact
Processor Support Contacts

More Info ...

Glossary
Articles

See also...

911 Software
Help

CreditLine Payment Processing Software Setup. This site can also be reached at http://docs.911software.com

Looking for better rates?   Get a Free Credit Card Processing Cost Comparison!

Compatibility

Requires version 3.03.13+

THIS FEATURE IS CURRENTLY IN BETA TESTING

Function

Rush Approval Mode is an optional transparent offline mode that allow POS to continue taking credit cards without delays during connectivity failures. After a set number of unsuccessful connections, rush mode is initiated and the credit card transactions are recorded offline for later processing. A countdown timer is initiated to keep the transactions from retrying the connection for some time to speed up the processing and avoid the timeout delays. At the expiration of the timer, the connection is retried and rush mode is exited if connection is successful. Rush mode is optional and has to be enabled and configured to become active.

No interface changes are required on the POS side, as the POS is receiving temporary Authorization Codes. Once the connection is back up, the logged transactions are reviewed in CreditLine ViewModify Dialog and can be retried or Forced through. At this point,Authorization Codes are replaced with live Authorization Codes.

See the Flow Chart below for details.

RushAuth.png

→ You can re-try the stored transactions at any time by using CreditLine ViewModify Dialog

Enabling

To enable, uncomment (remove the leading ; before) UseRushApproval=YES in the CreditLine Advanced Setup file and restart the CreditLine Server. See http://www.911software.com/files/911_CCV.INI for the full option list.

Configuration

The following are the configuration settings that you can add to CreditLine Advanced Setup file under [911_ccv] section.

;...............................
; Rush Approval Settings
;..............................
;
;Enable Rush Approval
;Default: NO
;UseRushApproval=YES
;
;The number of errors that will make the server go in to the rush approval mode.
;AutoRushApprovalInvocationErrorCount=3
;
;Number of minutes for the server to come out of the rush approval mode when idle.
;AutoRushApprovalExpiration=40
;
;...............................
; End of Rush Approval Settings
;..............................

Rush Approval

In Rush Approval mode you will get Authorization Codes that start with RUSH.

RushAuthOk.gif

Viewing Rush Approval Transactions

Enter CreditLine ViewModify Dialog

Check Rush Approval Only Button to show only Rush Approval Transactions

Re-Trying Rush Approval Transactions

  1. Enter CreditLine ViewModify Dialog
  2. Check Rush Approval Only Checkbox to show Rush Approval Transactions and Re-Auth Button
    ViewModRushOnly.gif
  3. Select a set of transactions that you want to re-try and hit Real Auth Button
    Check Offline to Force the transaction
    .

You can re-try as many times as you want.