Difference between revisions of "MasterCard Unique Lane ID / Terminal ID Mandate"
| Line 7: | Line 7: | ||
must contain a unique terminal identifier. This will help with the auditing process, identifying the source of the fraud for every transaction. | must contain a unique terminal identifier. This will help with the auditing process, identifying the source of the fraud for every transaction. | ||
| − | We have worked with processors to comply with their individual implementations of this mandate. | + | We have worked with processors to comply with their individual implementations of this mandate. We made sure that multiple batches are not required in a multi-terminal environment, despite the initial suggestion by the processors to setup every terminal as a separate merchant account with a unique Terminal ID, often requiring its own end-of-day settlement. |
Some processors received a significant extension and others have an internal understanding with MasterCard that will provide ample warning before any penalties are charged. In general, MasterCard considers EMV to be a deeper level of protection, although EMV is still not ready across all the processors. However, the mandate will begin to be enforced in December 2014 for most merchants. | Some processors received a significant extension and others have an internal understanding with MasterCard that will provide ample warning before any penalties are charged. In general, MasterCard considers EMV to be a deeper level of protection, although EMV is still not ready across all the processors. However, the mandate will begin to be enforced in December 2014 for most merchants. | ||
Revision as of 20:45, 21 November 2014
| This article is part of the Payment Processing Software Library |
|
| Get it... | |
| Install it... | |
| Connect to it... | |
| Set it up... | |
| Learn to use it... | |
|
→ Manual & User Guide | |
| Fix it... | |
|
→ Errors & Troubleshooting | |
| Get Help... | |
| More Info ... | |
| See also... | |
CreditLine Payment Processing Software MasterCard Unique Terminal ID Mandate. This site can also be reached at http://docs.911software.com
→ Looking for better rates? Get a Free Credit Card Processing Cost Comparison!
Contents
MasterCard has issued a mandate called "Authorization Data Accuracy Card Acceptor Terminal ID". The purpose of this mandate, which the industry is referring to as the MasterCard Unique Lane ID or Terminal ID Mandate is to identify and monitor transaction level data elements critical to the detection, prevention, prediction, and research of fraud related payment processing activity. As part of the data accuracy mandate, MasterCard requires that when a merchant location has multiple card acceptor devices in use (i.e. workstations, lanes, or peripheral terminals), each must contain a unique terminal identifier. This will help with the auditing process, identifying the source of the fraud for every transaction.
We have worked with processors to comply with their individual implementations of this mandate. We made sure that multiple batches are not required in a multi-terminal environment, despite the initial suggestion by the processors to setup every terminal as a separate merchant account with a unique Terminal ID, often requiring its own end-of-day settlement. Some processors received a significant extension and others have an internal understanding with MasterCard that will provide ample warning before any penalties are charged. In general, MasterCard considers EMV to be a deeper level of protection, although EMV is still not ready across all the processors. However, the mandate will begin to be enforced in December 2014 for most merchants.
We have released a version that satisfies the mandate for all major IP supported processors. See below for details.
Important List of Changes in the MC Mandate Compliant Version
See Upgrading_to_4.1.3_Build_1186 for a complete list
