[vc_row css=”.vc_custom_1418699243331{margin-bottom: 0px !important;padding-top: 65px !important;}” gmbt_prlx_bg_type=”parallax” gmbt_prlx_break_parents=”0″ gmbt_prlx_video_youtube_loop_trigger=”0″ gmbt_prlx_video_aspect_ratio=”16:9″ gmbt_prlx_parallax=”none” gmbt_prlx_speed=”0.3″ container_class=”container”][vc_column width=”1/2″][vc_single_image image=”3154″ border_color=”grey” img_link_target=”_self” img_size=”full” img_link_large=””][/vc_column][vc_column width=”1/2″][themestudio_title title=”MERCHANT DEFENDER” align_title=”text-left” title_color=”#252525″ des_color=”#737373″ css=”.vc_custom_1432536160359{margin-bottom: 45px !important;}” fontsize_title=”30″]Merchant Defender™ eliminates clear text credit card information from a merchant’s environment, regardless of their processing method.
How does it work?

Once activated, Keyed-In transactions (MOTO), Swiped transactions (Card Present), and E-Commerce transactions (Card Not-Present) function only using encrypted card data. If a merchant attempts to process an actual unencrypted credit card, Merchant Defender™ will defend the transaction attempt by disallowing any data transmissionor processing.

  • Keyed-In transactions (MOTO)
  • An encrypted keypad will be supplied to any users that will manually be Keying-In credit cards to process or search for transactions.
  • Swiped transactions (Card Present)

An encrypted card reader and licensed Gateway SwIPesoftware will be supplied to any users that will be performing card present swiped transactions.

iProcess™ Mobile Payments application will be supplied to any users that will be performing Mobile Payments (Important Note: an encrypted mobile card reader will be required [see supported hardware devices below] to use iProcess™ with Merchant Defender™ activated. Keying-In of transactions is disallowed).

  • E-Commerce (Card Not-Present)
  • Lock down all web based consumer entered payment
    data to require collection via patent pending Three
    Step API™.