Elavon Payment Gateway MCC 6012 Recipient Information User Guide



Similar documents
MCC 6012 Recipient Information User Guide. December 15

How To Use The Elavon Payment Gateway Virtual Terminal On A Credit Card Over The Phone

Elavon Payment Gateway - Navigation User Guide

MCC 6012 Recipient Information

Elavon Payment Gateway Integration Guide- Mail Order/Telephone Order Only

Elavon Payment Gateway- Secure Data Vault User Guide

Elavon Payment Gateway Integration Guide 3D Secure

Elavon Payment Gateway Integration Guide- Remote

Elavon Payment Gateway- 3D Secure

Elavon Payment Gateway - Redirect Integration Guide

Elavon Payment Gateway- edcc Developer s Guide

Virtual Terminal Guide

Secure XML API Integration Guide. (with FraudGuard add in)

CREDIT / DEBIT CARD PROCESSING FOR ONLINE APPLICATIONS. Step 1: Customer connects to agency s web storefront via the Internet.

MySagePay. User Manual. Page 1 of 48

Realex Payments Integration Guide - Ecommerce Remote Integration. Version: v1.1

Elavon Payment Gateway- Fraud Management User Guide

Global Iris Virtual Terminal User Guide. October 15

Elavon Payment Gateway- Reporting User Guide

DIRECT INTEGRATION GUIDE DIRECT INTEGRATION GUIDE. Version: 9.16

Merchant Operating Guide ROI. Elavon Merchant Services PO Box 56 IDA Business Park Arklow Co. Wicklow. Authorisations (ROI): Tel.

How To Use Fis Payment Gateway

Merchant Operating Guide

OXY GEN GROUP. pay. payment solutions

Bank and SecurePay Response Codes

Card Sales & Refunds Quick Guide VeriFone Vx520

Global Iris Integration Guide ecommerce Remote Integration

Virtual Terminal User Guide

Sage Pay Fraud Prevention Guide

Dynamic Currency Conversion (DCC) Best Rate Guarantee

Swedbank Payment Portal Implementation Overview

Secure XML API Integration Guide - Periodic and Triggered add in

TRANSAXpay Online Safer ecommerce & MOTO Payments FIS RETAIL PAYMENTS

Web Services Credit Card Errors A Troubleshooter

RealAuth Hosted Payment Page

Accepting Ecommerce Payments & Taking Online Transactions

Web Services Credit Card Errors A Troubleshooter

HOSTED INTEGRATION GUIDE HOSTED INTEGRATION GUIDE. Version: 9.16

Virtual Payment Client Integration Reference. April 2009 Software version:

Simple Integration Mobile Ready Cutting-edge Innovation

RealControl. User Guide. Version: v3.3

Web Services Credit Card Errors A Troubleshooter

Magento Extension User Guide: Payment Pages. This document explains how to install the official Secure Trading extension on your Magento store.

Mail & Telephone Order Payments Service (WorldAccess) Guide. Version 4.3 February 2014 Business Gateway

REALCONTROL CUSTOMERS

merchant payments and reconciliation your guide

increase your resistance How card not present gaming companies can minimise the risk of losing money through chargebacks

PAYMENT GATEWAY AND MERCHANT ACCOUNT APPLICATION FORM

ANZ egate Merchant Administration. Quick Reference Guide

Elavon Payment Gateway Hosted Payment Page

Cardholder Authentication Guide. Version 4.3 August 2013 Business Gateway

Realex Payments Resource Document. Version: v1.1

NAB TRANSACT. XML API Integration Guide

Recurring Transactions Enquiry Service. Merchant Implementation Guide

RealAuth. Developers Guide. Version: 4.9

MASTERCARD SECURECODE ISSUER BEST PRACTICES

Internet Payment SOLUTIONS. Dependable. Simple. Efficient.

Internet Authentication Procedure Guide

Recurring Credit Card Billing

Realex Payments. Magento Community / Enterprise Plugin. Configuration Guide. Version: 1.1

ANZ Secure Gateway Virtual Terminal QUICK REFERENCE GUIDE NOVEMBER 2015

Direct Payment Protocol Errors A Troubleshooter

Payment Status Definitions

API Integration Payment21 Button

Test and Go Live User Guide. Version 4.3 February 2014 Business Gateway

Merchant Card Payment Engine

First Data Merchant Solutions Virtual Terminal & Manager

Account Management System Guide

ARGOFIRE REFERENCE GUIDE

Fraud Detection Module (basic)

Merchant Account Set-up Guide

Merchant Account Service

EMS E-COMMERCE GATEWAY API TECHNICAL INSTALLATION MANUAL FEBRUARY 2016

Fraud Detection. Configuration Guide for the Fraud Detection Module v epdq 2014, All rights reserved.

Payment Processor Errors A Troubleshooter

Your Guide. to doing business with American Express

Your Guide. to doing business with American Express

Merchant Console User Guide. November 2013 CRXE-MCNT-MCON-UG07

Risk Management Service Guide. Version 4.2 August 2013 Business Gateway

Advanced Credit Card processing Service

Order Notifications - reporting a payment status

Credomatic Integration Resources. Browser Redirect API Documentation June 2007

a CyberSource solution Merchant Payment Solutions

Back Office. Back-Office User Guide v epdq 2015, All rights reserved.

Your Gateway to Online Success

ipayment Gateway API (IPG API)

ROYAL BOROUGH OF WINDSOR AND MAIDENHEAD SECURITY POLICY. Processing Electronic Card Payments

The Online Payment Process

Guide to BBPS and BBMS Blackbaud Payment Services and Blackbaud Merchant Services explained.

e Merchant Plug-in (MPI) Integration & User Guide

ANZ egate Virtual Payment Client

Current Account Conditions and AccounT Information.

6. REPONSE CODE DEFINITION

Transcription:

Elavon Payment Gateway MCC 6012 Recipient Information User Guide Version v1.1

Table of Contents 1 About This Guide.3 1.1 Purpose 3 1.2 Audience..3 1.3 Terminology 3 2 Overview of the MCC 6012 Mandate..4 3 Elavon Payment Gateway Virtual Terminal 5 3.1 Virtual Terminal Screen 5 4 Reporting..6 4.1 Terminal Screen 6 4.2 Take Payment Screen..7 5 Remote XML 8 5.1 Requests 8 6 Hosted Payment Page..10 6.1 Additional Fields in the HTTP Post Request..10 Page 2

1 About This Guide This section outlines the purpose and aim of the guide, target audience, any source materials or terminology used, and a general document description. Please note that this document is regarded as confidential and is for customer use only. It has been supplied under the conditions of your Card Processing Agreement. 1.1 Purpose The purpose of this guide is to provide all of the details required to submit the additional recipient information mandated by VISA using the Elavon Payment Gateway Virtual Terminal and Reporting applications. The additional details can be provided for card to card and card to account transactions. 1.2 Audience The target audience for this guide is merchants who take card payments over the telephone and mail order or use the Reporting application. 1.3 Terminology Term MCC 6012 Description Merchant category code denoting a Financial Institution Recipient Information The information of the person who is receiving the funds Remote XML Application Programming Interface (API) which allows for the remote submission of authorisation requests Virtual Terminal Application used to take card payments over the phone Reporting Application used for online reporting and reconciliation Page 3

2 Overview of the MCC 6012 Mandate The Merchant Category Code (MCC) 6012 Financial Institution is used for variety of payments initiated by financial institutions. MCC 6012 is the most fraudulent MCC in the UK market. As advised by VISA, the majority of fraud perpetrated on the MCC 6012 is on compromised VISA debit card details that are used to pay or transfer balances to other cards. Acquirers are therefore unable to confirm whether a payment is genuine, despite matching of full CVV2 with AVS. To address this situation, additional data for MCC 6012 is to be captured and submitted, unchanged, to the card issuer for Visa transactions to assist in authorisation decisions. The additional information required is: Recipient Date of Birth Recipient Account Number Recipient Post Code Recipient Last Name The new fields are NOT MANDATORY and VISA will not decline any transaction that is missing the information. This mandate will only affect UK 6012 Merchants. Page 4

3 Elavon Payment Gateway Virtual Terminal Elavon Payment Gateway Virtual Terminal is a solution for merchants taking card payments over the telephone or mail order, either in a small office or a larger operation such as a call centre. The Virtual Terminal application allows your agents to enter card details and order information, then authorise the card for payment. This section describes the following: Additional fields associated with MCC 6012 Merchants 3.1 Virtual Terminal Screen The Recipient Information fields will only be displayed if the transaction is using a VISA Card The Recipient Information is NOT mandatory Field Format Length Description Surname a-z A-Z 0-6 Only the first 6 characters of the surname are required Date of Birth 0-9, yyyymmdd 0-8 Date of Birth of the Recipient Post Code a-z A-Z 0-9 0-6 Only the first part of the post code is required PAN/Account Number 0-9 0-10 The account number or the card that is receiving the funds Page 5

4 Reporting Reporting is the online reporting and reconciliation tool for merchants who use Elavon Payment Gateway. 4 new fields have been added to the Terminal and Take Payment Screens. 4.1 Terminal Screen The Recipient Information is NOT mandatory The Recipient Information fields will only be displayed if the transaction is using a VISA Card. Field Format Length Description Surname a-z A-Z 0-6 Only the first 6 characters of the surname are required Date of Birth 0-9, yyyymmdd 0-8 Post Code a-z A-Z 0-6 Only the first part of the post code is required PAN/Account Number 0-9 0-10 The account number or the card that is receiving the funds Page 6

4.2 Take Payment Screen The Recipient Information is NOT mandatory Field Format Length Field Description Surname a-z A-Z 0-6 Only the first 6 characters of the surname are required Date of Birth 0-9, yyyymmdd 8 Recipients date of birth Post Code a-z A-Z 0-9 0-6 Only the first part of the post code is required PAN/Account Number 0-9 0-10 The first 6 and last 4 numbers of the card that is receiving the funds or the full account number Page 7

5 Remote XML Elavon Payment Gateway uses a generic XML element called supplementary data to facilitate the transmission of extra informational data to the Elavon Payment Gateway systems. This supplementary data element will be used to submit all extra MCC information. <request type="auth" timestamp="20060704122345"> <supplementarydata> <item type=" "> <field01> </field01> <field02> </field02> </item> <item type=" "> </item> </supplementarydata> </request> 5.1 Requests The "supplementarydata" element will be included in Authorisation, Refund, Credit, Rebate, and Settlement XML Requests. It will be ignored in other requests. Example: <request type="auth" timestamp="20060704122354"> <supplementarydata> <item type="mcc 6012 "> <field01>primary _recipient _DOB</field01> <field02>primary_recipient_surname</field02> <field03>primary_recipient_account_number</field03> <field04>primary_recipient_postalcode_partial</field04> </item> </supplementarydata> </request> The following indicators are used to show whether or not an element is required or optional. Page 8

M O C Required for this request type Optional Required depending on another optional field Line Per Description M/O/C Format Length Details </supplementarydata> M a-z A-Z 0-9 "" _ -., @ Top-level element. <item type="mcc 6012 " > O primary_recipient_dob O 0-8 8 yyyymmdd (year month date) Note No default date is captured primary_recipient_surname O a-z A-Z 6 First 6 characters of the recipient surname. Only alpha characters to be used (namely Latin characters such as A,B,C or a,b,c, etc) primary_recipient _postalcode O a-z A-Z 0-9 6 First part of the post code (the district) which UK acquirers are required to populate. For example in the post code KA27 8AA, specify only KA27 primary_recipient _account number O 0-9 10 Card to card payments: First 6 and last 4 characters of recipient PAN (no spaces) Card to non-card payments: Up to 10 characters of recipient account number details. Page 9

6 Hosted Payment Page The Hosted Payment Page (HPP) is a simple and straightforward way of taking payments. In addition to processing card payments, HPP also allows you to accept transactions from alternative payment methods. Using this method, the customer will be redirected to the Elavon Payment Gateway secure server to enter their details and complete the transaction. 4 new fields in the Merchant HTTP Post will be used to submit the additional MCC 6012 recipient information. 6.1 Additional Fields in the HTTP Post Request <input type="hidden" name="pr_dob" value="yyyymmdd"> <input type="hidden" name="pr_account" value="pan or account number"> <input type="hidden" name="pr_postcode" value="post code"> <input type="hidden" name="pr_surname" value="surname"> Field Format Length M/O Field Description PR_SURNAME a-z A-Z 0-6 O Only the first 6 characters of the surname are required PR_DOB 0-9, yyyymmdd 8 O Recipients date of birth PR_POSTCODE a-z A-Z 0-9 0-6 O Only the first part of the post code is required PR_ACCOUNT 0-9 0-10 O The first 6 and last 4 numbers of the card that is receiving the funds or the full account number Page 10

Elavon Financial Services Limited is registered in Ireland Number 418442. Registered Office: Block E, 1st Floor, Cherrywood Business Park, Loughlinstown, Co. Dublin, Ireland. Elavon Financial Services Limited is regulated by the Central Bank of Ireland. United Kingdom branch registered in England and Wales under the number BR009373. Elavon Merchant Services is a trading name of Elavon Financial Services Limited. Directors: Kurt Adams (USA), John Collins, Craig Gifford (USA), Bryan Calder (USA), Pamela Joseph (USA), Declan Lynch, John McNally, Malcolm Towlson Page 11