Velocity P2PE Overview

This guide provides integration guidance associated with the Velocity Point-to-Point Encryption (P2PE) Value-Added Service (VAS) supported by the Managed Commerce Services Platform. The Velocity P2PE VAS is a merchant “opt-in” service that enables support for P2PE transaction workflows supported by a service within existing Commerce Web Services (CWS) transaction processing workflows.

Intended Audience

This guide is intended to provide software company developers with an overview of the Velocity Point-to-Point Encryption (P2PE) VAS and some important development considerations associated with the development of Commerce Web Services (CWS) applications that leverage this service.

Prerequisites

The following prerequisites are required to leverage the Velocity P2PE VAS on the Managed Commerce Services Platform:

Additional Resources

The following resources provide additional information that can be referenced as supplemental material to this online guide:

  • Commerce Web Services Developer’s Guide provides an overview of the components and concepts related to the development of client applications that communicate with Commerce Web Services, as well as a step-by-step guide for developing applications that implements the Commerce Web Services SOAP and REST APIs.
  • Integration Guidelines provides guidance associated with the integration to specific certified payment service providers and Value-Added Services (VAS) supported by the Managed Commerce Services Platform.

 


 

Overview

According to some industry sources the breach liability for a merchant handling cardholder data is between $180 to $1000 per cardholder number transmitted and stored. For merchants who store several years’ worth of data this can translate to a potential liability of $150,000 to $600 Million. For many of these companies the cost of being PCI compliant while storing and handling sensitive card data can range from $50,000 to $2 Million. To combat this problem merchants need a multi-faceted approach to handling credit cards transactions that includes a Point-to-Point Encryption solution.

NAB Velocity offers their Point-to-Point Encryption (P2PE) solution as a Value Added Service (VAS) as part of the NAB Velocity Managed Commerce Services Platform.

Point-to-Point Encryption (P2PE) is a solution that encrypts cardholder data at the magnetic read head of a secure card reader device before being transmitted to the application for processing. This protects the track data from the entry point of a merchant’s point-of-sale (POS) to a point of secure decryption outside of the merchant’s environment, effectively removing card data from the merchants environment. The goal of P2PE is to directly address the risk of interception associated with cardholder data in motion by providing secure data transmission along the path of a transaction and thusly lowering the PCI compliance burden for both software companies and merchants.

Supported Features

  • Support for all certified payment service providers supported by the managed Commerce Services Platform (Chase Orbital Retail Processing solution not available due to inability to accept/handle Track 2 data).
  • Simple workflow-based enablement without requiring changes to the software application.
  • Triple DES encryption and DUKPT key management provides a comprehensive solution protecting data while at rest and in motion.

Integration Requirements

  • Requires Commerce Web Services (CWS) application certification 2.0.17 (and above).
  • Support for Bankcard Processing (BCP) transactions only (ECK and SVA service classes are currently not supported).
  • Software companies and their merchants are required to use Velocity-compatible Secure Card Reader Authenticators (SCRA) devices.

Component Architecture

The Velocity P2PE VAS component architecture is illustrated below:

Figure 1: Component Architecture

Production Architecture

The Velocity P2PE VAS production architecture communicates directly with the Velocity Web Service for all card data decryption.

Production Architecture and Workflow

The Velocity P2PE VAS component architecture and associated production environment workflow is illustrated below:

Figure 2: Production Architecture and Workflow

  1. The merchant swipes a consumer’s card through a supported Secure Card Reader Authenticator (SCRA) device at the point-of-sale (POS). Cardholder data is encrypted on the device at the time of swipe and transmitted to the POS application.
  2. The POS application submits the transaction to the Managed Commerce Services Platform via the Commerce Web Services (CWS) Transaction Processing Service (TPS) endpoint that contains a workflowId indicating the enablement of the Velocity P2PE VAS.
  3. 3TPS passes the authorization request to the Transaction Broker (TB). TB accesses the workflow process set for instructions on processing the transaction against the Velocity P2PE Service based on the CWS workflowId passed in the request.
  4. TB transmits the secure card data to the Velocity P2PE VAS Adaptor.
  5. The Velocity P2PE VAS Adaptor transmits the secure card data to the Velocity Decryption Server.
  6. The Velocity Decryption Server decrypts the secure card data and returns the decrypted card data (full track data as present on the swipe) to the Velocity P2PE VAS Adaptor.
  7. The decrypted card data is then returned to TB via the Velocity P2PE VAS Adaptor.
  8. TB sends the transaction request, along with the decrypted card data from the Velocity Service, to the appropriate destination service provider via the Service Provider Adaptor Add-Ins.
    • From this point forward, the transaction is processed in the same manner as any CWS transaction. The service provider processes the authorization request and returns a response to the requesting application via the Transaction Processing Service.
    • In implementations where the merchant’s Service Key also supports the NAB Velocity Tokenization Value-Added Service, the generated cardholder data token will also be returned to the application.

During the Velocity P2PE transaction workflow, destination service providers are completely unaware that P2PE has taken place, and therefore, can be implemented seamlessly with any NAB Velocity payment service provider.

Note: The encrypted card data sent to the Velocity Service is discarded and is never stored with the transaction.

Sandbox Architecture

The Velocity P2PE VAS Sandbox architecture communicates with a Velocity Web Service "test host" that stores magnetic fingerprint values for white-listed cards used to simulate production card data decryption and optional card scoring during testing/certification.

Sandbox Architecture and Workflow

The NAB Velocity Sandbox environment uses a special Velocity P2PE VAS Sandbox Adaptor that routes requests to a Velocity Web Service "test host" that is used to simulate card data decryption processing. Like the production Velocity Web Service, the Velocity test host stores decryption keys associated with all enabled Secure Card Reader devices.

The Velocity P2PE VAS component architecture and associated Sandbox environment workflow is illustrated below:

Figure 3: Sandbox Architecture and Workflow

  1. The merchant swipes a consumer’s card through a supported Secure Card Reader Authenticator (SCRA) device at the point-of-sale (POS). Cardholder data is encrypted on the device at the time of swipe and transmitted to the POS application.
  2. The POS application submits the transaction to the Managed Commerce Services Platform via the Commerce Web Services (CWS) Transaction Processing Service (TPS) endpoint that contains a Sandbox-enabled workflowId indicating the enablement of the Velocity P2PE VAS in the Sandbox environment.
  3. TPS passes the authorization request to the Transaction Broker (TB). TB accesses the workflow process set for instructions on processing the transaction against the Velocity P2PE Service based on the CWS on the CWS workflowId passed in the request.
  4. TB transmits the secure card data to the Velocity P2PE VAS Adaptor.
  5. The Velocity P2PE VAS Adaptor transmits the secure card data to the Velocity Decryption Server test host.
  6. The Velocity Decryption Server test host decrypts the secure card data and returns the full track data as present on the swipe to the Velocity P2PE VAS Adaptor.
  7. The Velocity P2PE VAS Adaptor passes the decrypted card data to the Velocity P2PE VAS Sandbox Adaptor.
  8. The Sandbox environment processes the trigger values contained in the decrypted card data and returns the appropriate response codes to the application.

Refer to Integration Guidelines for specific Velocity integration requirements, the Sandbox environment.

 


 

Implementation

Integration to the Velocity P2PE VAS requires a Velocity P2PE VAS-enabled workflowId that must be passed with each Commerce Web Services (CWS) transaction request. This workflowId is returned to the application in the response to the GetServiceInformation call during the Preparing the Application to Transact process of a CWS integration.

Optionally only for Secure Card Reader Authenticator (SCRA) devices, a ScoreThreshold value can be passed with each transaction request to trigger card authentication.

Setting the ScoreThreshold Value

One of the key features of the MagTek® MagneSafe™ security architecture is MagnePrint® card authentication, which is used to identify counterfeit credit cards, debit cards, gift cards, and other cards at the point of swipe. MagnePrint makes it possible for card issuers to uniquely identify each physical card they produce by analyzing its magnetic "fingerprint". By storing this fingerprint, merchants are able to perform a fingerprint reference check during card swipe to determine if the card is counterfeit, and should therefore be declined.

MagnePrint® card authentication, or card scoring, is performed based on the presence of the CWS BankcardTransactionData.ScoreThreshold parameter in each transaction authorization request.

  • ScoreThreshold Present: Encrypted card data is decrypted and card scoring is performed based on the ScoreThreshold value passed in the transaction request.
  • ScoreThreshold Null: Encrypted card data is decrypted, but no card scoring is performed.

Note: Velocity recommends that software companies use a default ScoreThreshold of 0.4. Negative scores typically fall between -0.1 and 0.3 (peaking at ~0.1), while positive scores typically fall between 0.7 and 0.95 (peaking at ~0.9).

Figure 4: MagnePrint Card Scoring based on Threshold Value
Source: http://www.magtek.com/V2/products/magnesafe/index.asp

Card Scoring Logic

  • Positive Result: If the Velocity Web Service returns a positive score greater than the specified ScoreThreshold value, the transaction workflow continues and the Velocity P2PE VAS returns the appropriate Velocity a <StatusCode> and <StatusMsg> in the transaction response message.
  • Negative Result: If the Velocity Web Service returns a negative score less than the specified ScoreThreshold value, the transaction workflow stops and the Velocity P2PE VAS returns the appropriate Velocity <StatusCode> and <StatusMsg> in the transaction response message.

Note: If no ScoreThreshold value is passed in the transaction authorization request, card scoring processing is ignored and the transaction workflow continues as normal.

Refer to the following Integration Guidelines sections for specific Velocity integration requirements, trigger values, and response codes.

Comments