MCC 6012 Recipient Information User Guide. December 15

Similar documents
MCC 6012 Recipient Information

Elavon Payment Gateway MCC 6012 Recipient Information User Guide

Global Iris Integration Guide ecommerce Remote Integration

Global Iris Virtual Terminal User Guide. October 15

Recurring Transactions Enquiry Service. Merchant Implementation Guide

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

Virtual Terminal Guide

RealAuth Hosted Payment Page

PAYMENTS AND HOSPITALITY. globalpaymentsinc.co.uk

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

MySagePay. User Manual. Page 1 of 48

THE EVOLUTION OF CARD PAYMENTS IN THE TOURISM SECTOR

DIRECT INTEGRATION GUIDE DIRECT INTEGRATION GUIDE. Version: 9.16

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

Elavon Payment Gateway- Fraud Management User Guide

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

MASTERCARD SECURECODE ISSUER BEST PRACTICES

REALCONTROL CUSTOMERS

Virtual Terminal User Guide

How to pay VAT. Update: changes to cheque payments by post. Update: HMRC s old bank accounts are closing. 1 of 9 13/07/ :12

Bank and SecurePay Response Codes

Cardholder Authentication Guide. Version 4.3 August 2013 Business Gateway

Secure XML API Integration Guide - Periodic and Triggered add in

HOSTED INTEGRATION GUIDE HOSTED INTEGRATION GUIDE. Version: 9.16

Fraud Detection Module (basic)

Sage Pay Fraud Prevention Guide

PayPoint.net Gateway Guide to Identifying Fraud Risks

OXY GEN GROUP. pay. payment solutions

Elavon Payment Gateway Integration Guide- Remote

RealAuth. Developers Guide. Version: 4.9

Basic Account Basic Account

HSBC Merchant Services

Elavon Payment Gateway - Redirect Integration Guide

Accepting Ecommerce Payments & Taking Online Transactions

Elavon Payment Gateway- Reporting User Guide

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

Swedbank Payment Portal Implementation Overview

Internet Authentication Procedure Guide

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

Advanced Credit Card processing Service

RealControl. User Guide. Version: v3.3

API Integration Payment21 Button

Elavon Payment Gateway- Secure Data Vault User Guide

DalPay Internet Billing. Technical Integration Overview

Virtual Payment Client Integration Reference. April 2009 Software version:

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

Recurring Credit Card Billing

Recurring Billing. Using the Simple Order API for CyberSource Essentials. March 2016

EMS E-COMMERCE GATEWAY API TECHNICAL INSTALLATION MANUAL FEBRUARY 2016

Merchant Card Payment Engine

Realex Payments Resource Document. Version: v1.1

This Annex uses the definitions set out in the Agreement on service of payment cards on the Internet (hereinafter the Agreement).

Elavon Payment Gateway Hosted Payment Page

Link ALL UOB Accounts to BIB: All active UOB accounts held by the Applicant as at the date of this BIB application will be linked.

Electronic Funds Transfer (EFT) Guide

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

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

WESTMINSTER ABBEY ASSOCIATION TERMS AND CONDITIONS

Order Notifications - reporting a payment status

E-payment. Service description

Risk Management Service Guide. Version 4.2 August 2013 Business Gateway

Elavon Payment Gateway Integration Guide 3D Secure

Address Verification and Security Code Guide. AVS Guide

NAB TRANSACT. XML API Integration Guide

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

Merchant Account Glossary of Terms

THE UNIVERSITY OF HONG KONG. Arrangements for Collection of Certificate/Diploma

Web Services Credit Card Errors A Troubleshooter

Merchant Account Service

GRANITE SCHOOL DISTRICT PURCHASING CARD PROGRAM POLICIES AND PROCEDURES MANUAL

Web Services Credit Card Errors A Troubleshooter

A multi-layered approach to payment card security.

Internet Payment SOLUTIONS. Dependable. Simple. Efficient.

Card Sales & Refunds Quick Guide VeriFone Vx520

Account Management System Guide

Barclaycard SmartPay. Hosted Payment Page Integration Guide. Version 3.0 released April 2012

ANZ egate Virtual Payment Client

ANZ Secure Gateway Virtual Terminal QUICK REFERENCE GUIDE NOVEMBER 2015

Payment Processor Errors A Troubleshooter

HSBC Merchant Services

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

Payment Status Definitions

A BETTER WAY TO PAY Unified Merchants API (UMAPI).Net Integration Manual

Transcription:

MCC 6012 Recipient Information User Guide December 15

Table of Contents 1 About This Guide... 3 1.1 Purpose... 3 1.2 Audience... 3 1.3 Terminology... 3 2 Overview of the MCC6012 Mandate... 4 3 Global Iris Virtual Terminal... 5 3.1 Virtual Terminal Screen... 5 3.2 Scheduler Screen... 6 4 Real Control 2... 7 4.1 Terminal Screen... 7 4.2 Take Payment Screen... 8 5 Remote XML... 9 5.1 Requests... 9 6 Hosted Payment Page... 11 6.1 Additional Fields in the HTTP Post Request... 11 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 Global Payments Virtual Terminal and Real Control 2. 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 new Real Control application. 1.3 Terminology Term MCC 6012 Recipient Information Remote XML Virtual Terminal RealControl Hosted Payment Page Description Merchant category code denoting a Financial Institution The information of the person who is receiving the funds Application Programming Interface (API) which allows for the remote submission of authorisation requests Application used to take card payments over the phone Application used for online reporting and reconciliation Application used to take card and alternative payments 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. 4

3 Global Iris Virtual Terminal Global Iris 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 1.4 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 5

1.5 Scheduler 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 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 6

4 Real Control 2 RealControl is the online reporting and reconciliation tool for merchants who use Global Iris. 4 new fields have been added to the Terminal and Take Payment Screens 4.1 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 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 7

4.2 Take Payment Screen Field Format Length M/O Field Description Surname a-z A-Z 0-6 O Only the first 6 characters of the surname are required Date of Birth 0-9, 8 O Recipients date of birth yyyymmdd Post Code a-z A-Z 0-9 0-6 O Only the first part of the post code is required PAN/Account Number 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 8

5 Remote XML Global Iris uses a generic XML element called supplementary data to facilitate the transmission of extra informational data to the Global Iris 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 the Authorisation XML Requests. It will be ignored in other requests. Example: <request type="auth" timestamp="20060704122354"> <supplementarydata> <item type="mcc6012 "> <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. M O C Required for this request type Optional Required depending on another optional field 9

Line Per Description M/O/C Format Length Details </supplementarydata> M a-z A-Z 0-9 "" _ -., @ Top-level element. <item type="mcc6012 " > 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. 10

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 Global Iris 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, 8 O Recipients date of birth yyyymmdd 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 11

Global Payments 51 De Montfort Street Leicester LE1 7BB Tel 0845 702 3344* Textphone 0845 602 4818 Email globaliris@realexpayments.com Global Payments is HSBC s preferred supplier for card processing in the UK. Global Payments is a trading name of GPUK LLP. GPUK LLP is authorised by the Financial Conduct Authority under the Payment Services Regulations 2009 (504290) for the provision of payment services. GPUK LLP is a limited liability partnership registered in England number OC337146. Registered Office: 51, De Montfort Street, Leicester, LE1 7BB. The members are Global Payments U.K. Limited and Global Payments U.K. 2 Limited. Service of any documents relating to the business will be effective if served at the Registered Office. *Lines are open between 9am 5pm Monday to Friday excluding public holidays. To help us continually improve our service and in the interests of security, we may monitor and/or record your telephone calls with us. Any recordings remain our sole property. We also provide a Textphone service on 0845 602 4818. GPUK LLP. All rights reserved. GP023 02/2013