RDP Certified for Protobase 6.01
July 24, 2009
The latest releases of RDPWin and IRMNet (2.092.15) have met the integration
guidelines Elavon has established in order to interface with Protobase 6.01. The
upgrade to these products must be coordinated and scheduled through our sales
department. It will involve scheduling the upgrade with RDP as well as Elavon.
The following RDPWin features must be implemented to be PCI compliant:
- Use TCP/IP Gateway to transmit requests
Protobase 6.01 no longer
uses Fileserver Gateway to send information between Protobase and RDP. RDP
Support can install the TCP/IP Gateway on your credit card bridge computer,
turn on the Use TCP/IP Gateway switch, and set the Server Name and Port#
used for TCP/IP communication. Elavon no longer supports Fileserver Gateway, since it is not PCI compliant.
- Require CID# on all non-swiped credit cards
This switch is
located on the System -> Configuration -> Protobase configuration screen in
RDPWin. In order to get
lower rates, the CID# should be entered whenever a credit card is not
swiped. With this switch set, the CID# will be required and payments or
authorizations will not be allowed without it when a credit card
number is typed in. The CID# field is displayed when the credit card
is swiped, but it is not required and the payment can be processed without
it.
- Turn on Address Verification on all non-swiped credit cards
This
switch is located on the System -> Configuration -> Protobase configuration screen
in RDPWin. This
feature requires the billing zip code to be entered on payments or
authorizations when the credit card is not swiped. If the Zip Code field on
the reservation is populated, a link below the Zip Code field will appear.
Clicking on this link, will populate the billing zip code field from the
reservation information. When the billing zip code is used, there are 2
transactions sent to Protobase. The first transaction is an authorization
for 1.00 to verify the billing zip code is correct. If that passes, the
authorization or sale transaction is processed as a second transaction.
- Internet Merchant Num and Terminal ID for IRM.Net
These fields are on the
Card Detail tab on each credit card master. In order to be PCI compliant,
card associations are requiring merchants to provide an indicator to
identify a credit card transaction made over the Internet (an e-Commerce
transaction) and the method of authentication used to secure the transaction
(i.e. SSL certificate). These transactions are not classified as e-Commerce
by Elavon or RDP, but by the card associations.
Visa International Operating
Regulations defines an Electronic Commerce (e-Commerce) Transaction as a
transaction between a merchant and cardholder over the Internet and other
networks using a Cardholder Access Device (a terminal, personal computer, or
other device). Visa International Operating Regulations defines an
Electronic Commerce Merchant as a merchant that conducts the sale of goods
or services electronically over the Internet and other networks. These
regulations can be found at
http://usa.visa.com/download/merchants/visa-international-operating-regulations.pdf.
Customers using IRM.Net must have a separate merchant ID for e-Commerce
transactions. This e-Commerce merchant ID can be acquired through RDP
Sales and will result in a
merchant file change. Processing e-Commerce transactions without a valid
indicator can result in penalties. At worst, the merchant’s account may be
blocked until the web site can demonstrate the ability to properly process
e-Commerce transactions and can provide a minimum of cardholder security.
Return
to News List
|
