New RDP PCI Compliant Credit Card Interface Subscription

8/1/2016

RDP software utilizes several credit card gateways to process credit card authorizations, deposits, payments, refunds and other transactions.  Credit card gateways are used with RDPWin, Internet Booking Engine (IRM.Net), Mobile IRM for SmartPhone and Tablets, and various Global Distribution Interfaces.

RDP software has been certified by Trustwave to be fully PCI (Payment Card Industry) Compliant when using one of our new credit card interfaces from Shift4 or Tenerum.    See Certification Letter.    Customers using RDP's legacy credit card interfaces from Vacation Rent Payments (VRP) and Southern Data Comm (SDC/Protobase) must convert to the new RDP credit card interface ASAP or face large fines for non-PCI compliance.   Please read this article carefully for details. 

RDP Credit Card Interface Subscription Required

The very complex new PCI/EMV requirements forced RDP to replace our legacy credit card gateways to VRP and SDC with two new gateways for customers to choose from.  In addition, RDP now offers reduced credit card processing fees with our preferred processor, Chosen Payments.   The new RDP interface is licensed to customers on a yearly subscription basis which includes:

Reduced Fees with RDP Preferred Processor - Chosen Payments/First Data

RDP customers process over ten million credit card transactions a year.  RDP has negotiated with Chosen Payments, a representative of First Data, to leverage this volume and offer RDP customers lower credit card processing rates.  While any processor can be used that is supported by the gateway company, it is suggested to get a quote from RDP's sales department to evaluate the savings available.  Customers savings are usually measured in thousands of dollars per year.  In addition to potentially saving RDP customers a significant amount of credit card fees, RDP has developed a close relationship with Chosen Payments which allows RDP to provide faster and better overall support than with a credit card vendors for which there is no relationship.

Liability Shift Starting October, 2015

One of the major PCI changes is a liability shift from the credit card company to the RDP customer for fraudulent transactions.  For each fraudulent incident, fault will be determined, and the liability will fall on whichever party has the lesser PCI compliance.  For example, currently if a guest uses a stolen credit card, it is usually the credit card company or processor that pays, not the RDP customer.  After October 2015, if the RDP customer has not implemented the new RDP Credit Card Interface, the liability will move to the RDP customer.  This liability can potentially include all purchases made with credit card information stolen from your company. The following industry articles provide more information on this topic.

http://www.tsys.com/acquiring/engage/white-papers/United-States-EMV-Adoption.cfm

https://www.chasepaymentech.com/faq_emv_chip_card_technology.html

http://www.level2kernel.com/flow_chart.html

Credit Card Interface Transactions

The RDP Credit Card Interface supports a wide range of transactions, including:

• Advance deposits, using either RDPWin or the Internet Reservation Module
• Additional deposits
• Transfer of advance deposits to in-house guest ledger
• Authorization at check-in
• Set guest credit limit to authorization amount
• Additional guest authorizations
• Payments on in-house guests linked to prior authorized amounts to release credit to guest
• Payment and credits to guests after checkout
• Payments from owners
• Supports new EMV devices (chip cards)

New Credit Card Devices Required for all Customers

In order to provide point-to-point encryption (PtoPE), all credit card information must be entered using a separate device, not the keyboard.  There are two phases of the rollout of these new credit card devices:

1. To convert to RDPWin version 4, all locations that accept a credit card must have either an IDTECH M130 or IDTECH SREDKey device.  These devices can scan magnetic stripe credit cards or allow manual input of the credit card information.  At locations where the physical card is not present, such as accounting or reservations, the M130 or SREDKey devices can be used today and into future.
    
2. At card present locations, such as a front desk, an EMV ready device that is capable of reading the new chip embedded credit cards is required.  One such device is the ISC250 pictured below.  These devices must be injected with software from both the Gateway and your processor to function.  Many processors do not have EMV devices available yet, so the M130 or SREDKey devices can be purchased now from RDP and then changed to EMV devices when available from the processor. 

Use the deposit bank of your choice

With the new RDP Credit Card Interface, any bank can be used for payment deposits.

Multiple Credit Cards allowed for one guest

RDPWin version 4 and the new RDP Credit Card Interface allow for multiple credit cards for each guest.  This feature can also be used to process one-time credit cards from Expedia and other on-line travel agents (OTA's). 

Internet Reservation Module (IRM.Net) and Mobile IRM for SmartPhone and Tablets

The new RDP Credit Card Interface can be used with the RDPWin product and also with the Internet Booking Engine (IRM.Net) and the Mobile IRM for SmartPhone and Tablets

Credit Cards and Owners or Members

For customers using RDP's Vacation Rental System, Condo-Hotel System, or Timeshare/Fractional System, owners or members can pay annual fees and settle statements using the new RDP Credit Card interface over the Internet.  The tokenized credit card can be stored and reused. 

For more information on credit card processing, contact Rita Gale at RitaG@Resortdata.com or 970-845-1143.