Difference between revisions of "One-Behind Transaction Confirmation"

From Payment Processing Software Library
Jump to: navigation, search
(New page: This processor transaction confirmation is one-behind, meaning that one transaction is valid as long as the next transaction sends the previous sequence number to confirm it. Otherwise...)
 
(Support Dependency)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
{{CreditLine Header|Processor Setup - One-Behind Transaction Confirmation}}
 +
==Definition==
 +
Most host based processors use one-behind transaction confirmation, meaning that one transaction is valid as long as the next transaction sends the previous sequence number to confirm it.  Otherwise it is voided.
  
This processor transaction confirmation is one-behind, meaning that one
 
transaction is valid as long as the next transaction sends the previous
 
sequence number to confirm it.  Otherwise it is voided.
 
 
For example:
 
For example:
 
;Send transaction 001 :  Approved.
 
;Send transaction 001 :  Approved.
;Send transaction 002 : Send in correctly, but in the message, there is a previous seq number field and 001 is filled in. If it matches the previous transaction, then transaction 001 stays as approved. If it does not match, the 001 is voided.
+
;Send transaction 002 : In the message, there is a previous sequence number field. If it matches the previous transaction, then the previous transaction stays as approved. If it does not match, the previous transaction is voided.
  
CreditLine stores the sequence number in [[CreditLine Advanced Setup|911_CCV.INI]] file.  So each time it is  
+
CreditLine stores the sequence number in [[CreditLine Advanced Setup|911_CCV.INI]] file, to make sure that each time it is correct.  
correct. However, the problem comes when the site needs support. When debugging this account, support needs  to grab 911_CCV.INI as well as other config files. Also, support can not run transactions while the site is also running transactions.
+
  
This is typical of host-capture systems.
+
==Support Dependency==
 +
 
 +
{{One-Behind Support Dependency}}
 +
 
 +
[[Category:Glossary|B]]

Latest revision as of 16:47, 11 February 2008

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 Processor Setup - One-Behind Transaction Confirmation. This site can also be reached at http://docs.911software.com

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

Definition

Most host based processors use one-behind transaction confirmation, meaning that one transaction is valid as long as the next transaction sends the previous sequence number to confirm it. Otherwise it is voided.

For example:

Send transaction 001 
Approved.
Send transaction 002 
In the message, there is a previous sequence number field. If it matches the previous transaction, then the previous transaction stays as approved. If it does not match, the previous transaction is voided.

CreditLine stores the sequence number in 911_CCV.INI file, to make sure that each time it is correct.

Support Dependency

One-Behind Transaction Confirmation creates a support dependency on the CreditLine Advanced Setup file:

  1. When debugging this account, support needs to grab CreditLine Advanced Setup, as well as other config files.
  2. Support can not run transactions while the site is also running transactions.
  3. The accounts may not be setup as auto-close.

This is typical of host-capture systems.
Make sure that this account is not setup for auto-close or this may result in Invalid Lane Validation errors