Documentation You are here: start » static » glossary

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
static:glossary [2011/05/13 08:04] – foxybrettstatic:glossary [2017/04/26 07:02] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
 <wrap todo>This page is a work in progress.</wrap> Please edit this page and add a note about any terms you are unclear on and we'll get them defined asap. Thanks! <wrap todo>This page is a work in progress.</wrap> Please edit this page and add a note about any terms you are unclear on and we'll get them defined asap. Thanks!
 +
 +
 +  ; 3-D Secure
 +  ; Verified by Visa (VbV)
 +  ; MasterCard SecureCode (MCSC)
 +  : 3-D secure is a protocol designed to add a layer of security to online credit and debit card transactions. When 3-D Secure is enabled the customer will be redirected to a 3rd party page (generally at the domain of the MPI used by the customer's card-issuing bank, but sometimes at the bank's domain itself) to verify that the cardholder is the one making the purchase. It may be useful for merchants desiring to reduce their exposure to chargebacks and fraud, but it can be very confusing for the customer for a few reasons (discussed in [[wp>3-D_Secure|the Wikipedia entry]]). 3-D Secure may be required for certain types of transactions in certain countries (notably, the UK).
 +  : [[wp>3-D_Secure|3-D Secure]]
 +
  
   ; AVS   ; AVS
Line 28: Line 36:
   ; MPI   ; MPI
   ; Merchant Plug-In   ; Merchant Plug-In
-  : An MPI is a separate piece of a payment flow that handles 3D-Secure verifications. Some gateways have 3D-Secure capabilities built into the gateway, while others require the use of 3rd party MPIs in order to handle 3D-Secure. (For example, PayPoint's 3D-Secure functionality is built into the gateway, but PayPal's Website Payments Pro uses CardinalCommerce to handle 3D-Secure verifications.)+  : An MPI is a separate piece of a payment flow that handles 3-D Secure verifications. Some gateways have 3-D Secure capabilities built into the gateway, while others require the use of 3rd party MPIs in order to handle 3-D Secure. (For example, PayPoint's 3-D Secure functionality is built into the gateway, but PayPal's Payments Pro (and Merchant eSolutions, and others) uses CardinalCommerce to handle 3-D Secure verifications.)
   : [[wp>Merchant_Plug-In|Merchant Plug-In]]   : [[wp>Merchant_Plug-In|Merchant Plug-In]]
 +
 +
 +  ; PAReq
 +  ; Payer Authentication Request
 +  ; PARes
 +  ; Payer Authentication Response
 +  : The ''PARes'' and ''PAReq'' values are used in the 3-D Secure protocol.
 +
 +
 +  ; VEReq
 +  ; Verify Enrollment Request
 +  ; VERes
 +  ; Verify Enrollment Response
 +  : The ''VEReq'' and ''VERes'' are used in the 3-D Secure protocol to establish whether or not a customer has enrolled in 3-D Secure.

Page Tools

Site Tools