Chip&PIN

Chip&PIN

This document is a technical introduction to the Chip and PIN Service. It assumes the reader has some familiarity with the Cardholder Not Present Bank Card service. Further detailed information to assist integration with the Service is available in the Developers Guide.

The MasterCard Payment Gateway supports Card Holder Present transactions using the following input methods:

  • legacy Magnetic Stripe - the data is swiped from the magetic card stripe
  • legacy PAN Key Entry - the data is keyed into the terminal
  • Chip and PIN - the data is taken from the chip while the card is parked in the POS terminal

There are three different ways in which authorisations for the Service may be submitted: always off-line, always on-line and predominantly off-line

 

Always Off-Line


In this mode of operation, no transactions are submitted to the DPG for authorisation. The transactions are manually authorised and their details are stored in a log. At the end of the day, all the transactions in the log are submitted to the DPG for settlement, along with the authorisation code. This can be done using the Batch Input Service if required.

 

Always On-Line


Using this mode of operation, all transactions are submitted to the DPG for authorisation in real time.

 

Predominantly Off-Line


In this mode of operation, some of the transactions are processed in on-line mode and the remainder are processed off-line.

 

Requirements


Before you can go live with this service you will need the following:

  • an account set up with MasterCard Payment Gateway Services,
  • the ability to send XML transactions to the DPG

 

Transaction Processing Models


There are two different models for processing transactions:

  • one transaction authorisation - the transaction is sent to MasterCard Payment Gateway Services and is automatically settled.
  • two transaction authorisation - the initial transaction is sent to MasterCard Payment Gateway Services for authorisation, but is not settled. A subsequent transaction is submitted to settle the transaction. This is only available for on-line tranasctions.

The transaction types which are used for the Service are:

 

Transaction Type

Effect

Uses

creditcheck

Obtains authorisation without settlement

The initial transaction of the two transaction on-line model

auth

Obtains authorisation and is automatically settled

One transaction on-line model

Uses previously issued authorisation code to settle transaction

Off-line transactions. Or the second transaction for the two transaction on-line model

cancel

Cancels and reverses existing unsettled transaction

Any transactions

 

 

Always Off-Line


In this mode of operation, auth transactions are manually authorised and are entered into the retailers log. They are submitted to the DPG at the end of the day, and are automatically settled. The transactions may be cancelled before settlement if required.

 

Always On-Line


Using this mode of processing, there are two ways to achieve authorisation:

  1. creditcheck - the transactions are submitted for authorisation codes and are not settled. The auth transaction type is then submitted using the authorisation code of the initial transaction and the auth is automatically settled.
  2. auth - the transactions are submitted for authorisation and are automatically settled.

Both transaction types may be cancelled, though in practice as only auth are settled, these are the only ones which may need cancelling.

 

Predominantly Off-Line


In this mode of operation, most of the transactions are processed off-line as auth transactions. They are manually authorised and are retained in a log which is submitted at the end of the day.

The remainder of the transactions are processed in on-line mode. There are two ways in which the online transactions may be submitted.

  1. creditcheck - the online transactions are submitted for authorisation and are not automatically settled. The authorisation code obtained is then added to the retailers log as an auth transaction type and are submitted for settlement later along with the off-line transactions
  2. auth - the online transactions are automatically settled.

Both auth and creditcheck transaction types may be cancelled, though in practice as only auth are settled, these are the only ones which may need cancelling.

 

Performing Transactions


Each transaction type requires specific information to be provided. In addition to those listed, each requires a client and password - these are security details which identify your account.

 

On-Line and Off-Line Transactions


The following information can be provided for transactions:

  • the transaction method, either auth or creditcheck
  • the value and currency of the sale
  • the cashback amount, if requested by the customer
  • details of the terminals capabilities
  • the technique used to obtain the data from the card, either parked, keyed or swiped

Additional details about the card must be obtained from the chip or magnetic stripe if the card is parked or swiped. Please refer to the Developers Guide for full details.

When the transaction has been authorised, the authorisation code should also be presented.

If the XML Batch Input Service is being used to submit the off-line transactions, the same fields can be provided.

 

Cancellation & Reversal of Transactions


A transaction can be cancelled by providing the same information as for the Bank Card Service. If you require the transaction to also be reversed, can also be indicated in the transaction.

 

Return Codes


The three basic Bank Responses for authorisation requests are the same as for the Bank Card:

  • Accepted
  • Declined
  • Referred

In addition there are various error codes that can be returned. Many of these are general error codes which may also be generated by the Bank Card Service, but there are some errors that are specific to the Card Holder Present Service.

The Support Centre also contains extensive examples for most error codes. Illustrations and suggestions are given to help you prevent them from occurring.

 

Reporting


The transactions are detailed in the Bank Card section of the MasterCard Payment Gateway Services Reporting system. There are three main pages:

  • Summary - gives a summary of the transactions
  • List - shows specific details of the transactions
  • Details - shows most details of each transaction

The Support Centre contains full hints and tips to help you get the most out of Reporting.