<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>EMVX Blog &#187; low-value transaction</title>
	<atom:link href="http://blog.emvx.co.uk/index.php/tag/low-value-transaction/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.emvx.co.uk</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 11 Aug 2010 09:55:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>EMV Unattended Payments</title>
		<link>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/emv-unattended-payments/</link>
		<comments>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/emv-unattended-payments/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 11:03:13 +0000</pubDate>
		<dc:creator>palcock</dc:creator>
				<category><![CDATA[EMV Certification and Approvals]]></category>
		<category><![CDATA[Chip and PIN terminal]]></category>
		<category><![CDATA[EMV Kernal]]></category>
		<category><![CDATA[EMV Parking]]></category>
		<category><![CDATA[EMV Ticketing]]></category>
		<category><![CDATA[EMV Transaction]]></category>
		<category><![CDATA[kiosk payment]]></category>
		<category><![CDATA[low-value transaction]]></category>
		<category><![CDATA[Parking payment]]></category>
		<category><![CDATA[Unattended payment terminal]]></category>
		<category><![CDATA[UPT]]></category>
		<category><![CDATA[Vending Payment]]></category>

		<guid isPermaLink="false">http://blog.emvx.co.uk/?p=30</guid>
		<description><![CDATA[Although much of the publicity  surrounding EMV “Chip and PIN” migration has related to its use in retail  outlets, another market sector that has benefitted from EMV migration is Unattended Payment Terminals (UPT).
Unattended payments, where a  customer uses an unsupervised terminal to pay for goods or services such as parking and vending [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_34" class="wp-caption alignleft" style="width: 205px"><img class="size-full wp-image-34" title="Chip and PIN Parking Meter" src="http://blog.emvx.co.uk/wp-content/uploads/2010/02/Metric-Aura-PD-Machine.jpg" alt="Metric &quot;Aura&quot; EMV equipped Pay-and-Display machine" width="195" height="312" /><p class="wp-caption-text">Metric &quot;Aura&quot; EMV equipped Pay-and-Display machine</p></div>
<p>Although much of the publicity  surrounding EMV “Chip and PIN” migration has related to its use in retail  outlets, another market sector that has benefitted from EMV migration is Unattended Payment Terminals (UPT).</p>
<p>Unattended payments, where a  customer uses an unsupervised terminal to pay for goods or services such as parking and vending machines or self-service kiosks, have  traditionally been processed using cash. Where card payment has been supported  this has been achieved by using the data from the magnetic stripe on a  customer’s card, with no cardholder verification. This means that such machines  are an obvious target for fraudsters trying to use stolen and cloned cards and,  as there are no attendants to monitor these environments, it has been extremely  difficult to crackdown on this illegal activity. This has therefore limited the  growth of unattended card payments.</p>
<p>However, the advent of EMV cards  means that secure PIN entry can now be used to verify the cardholder, and  advances in communications technology means that it is also possible to quickly  and safely authorise transactions with the card issuer even when there is no  fixed communications infrastructure on site.</p>
<p>Together, these developments have  fuelled a large growth in a number of unattended environments, including car  parking, transport ticketing, automated supermarket lanes and other self-service  kiosks vending higher value goods, as vendors can now have confidence that every  transaction is genuine and they will always receive their  payment.</p>
<p><strong>This is just one  example of the benefits that EMV migration can bring. The CreditCall EMV Kernels  provide a simple but powerful way to add EMV Level 2 capability to payment devices. Check  out <span style="text-decoration: underline;"><a title="http://www.emvx.co.uk/" href="http://www.emvx.co.uk/">www.emvx.co.uk</a></span> for further  details of these EMV Level 2 Kernels.</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/emv-unattended-payments/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>EMV Cardholder Verification Methods</title>
		<link>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/emv-cardholder-verification-methods/</link>
		<comments>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/emv-cardholder-verification-methods/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 10:58:05 +0000</pubDate>
		<dc:creator>palcock</dc:creator>
				<category><![CDATA[EMV Certification and Approvals]]></category>
		<category><![CDATA[Cardholder verification]]></category>
		<category><![CDATA[CVM]]></category>
		<category><![CDATA[CVM method]]></category>
		<category><![CDATA[CVM Processing]]></category>
		<category><![CDATA[EMV Kernal]]></category>
		<category><![CDATA[EMV Kernel]]></category>
		<category><![CDATA[emv level 2]]></category>
		<category><![CDATA[EMV Transaction]]></category>
		<category><![CDATA[EmvX]]></category>
		<category><![CDATA[low-value transaction]]></category>
		<category><![CDATA[offline PIN]]></category>
		<category><![CDATA[online PIN]]></category>

		<guid isPermaLink="false">http://blog.emvx.co.uk/?p=18</guid>
		<description><![CDATA[Although EMV is often referred to as  “Chip and PIN”, in fact EMV supports several different methods of verifying the  identity of the cardholder, known as Cardholder Verification Methods (CVM).  Every card contains a list of the CVM that it supports, and when they need to be  applied (e.g. Use online [...]]]></description>
			<content:encoded><![CDATA[<p>Although EMV is often referred to as  “Chip and PIN”, in fact EMV supports several different methods of verifying the  identity of the cardholder, known as Cardholder Verification Methods (CVM).  Every card contains a list of the CVM that it supports, and when they need to be  applied (e.g. Use online PIN if the transaction is an ATM cash withdrawal, else  use signature).</p>
<p>Whenever an EMV transaction is performed, the terminal’s EMV  Level 2 Kernel processes the CVM list in order, until it finds a CVM that it  supports and can process. In the event that no supported CVM is found or an  error occurs during CVM processing (e.g. the PIN-Pad was malfunctioning), the  EMV kernel will flag this in the Terminal Verification Results, which may cause  the transaction to be declined or sent online for authorisation by the card  issuer.</p>
<p>The CVM that EMV currently supports  are Online PIN (required in certain countries for all transactions, and also for  all ATM cash withdrawals), Offline PIN verified by the chip card (required in  certain countries for all payment transactions), signature (for attended payment  terminals in some countries), or a combination of both PIN and signature if  additional verification is required.</p>
<p>Also, in some environments it  is permissible to use no CVM for low-value transactions or for terminals that do  not support any of the CVM on the cards.</p>
<p><strong>CreditCall’s EMV  Kernels support every EMV-defined CVM, and provide a simple yet powerful way to  add EMV level 2 to payment devices. Check out <span style="text-decoration: underline;"><a title="http://www.emvx.co.uk/" href="http://www.emvx.co.uk/">www.emvx.co.uk</a></span> for further  details of these EMV Level 2 Kernels.</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/emv-cardholder-verification-methods/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>EMV Online Security</title>
		<link>http://blog.emvx.co.uk/index.php/security/emv-online-security/</link>
		<comments>http://blog.emvx.co.uk/index.php/security/emv-online-security/#comments</comments>
		<pubDate>Wed, 09 Dec 2009 14:00:18 +0000</pubDate>
		<dc:creator>palcock</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[authorisation response cryptogram]]></category>
		<category><![CDATA[EMV Kernal]]></category>
		<category><![CDATA[EMV Kernel]]></category>
		<category><![CDATA[emv level 2]]></category>
		<category><![CDATA[EMV Transaction]]></category>
		<category><![CDATA[EmvX]]></category>
		<category><![CDATA[kiosk payment]]></category>
		<category><![CDATA[low-value transaction]]></category>
		<category><![CDATA[offline PIN]]></category>
		<category><![CDATA[online PIN]]></category>

		<guid isPermaLink="false">http://blog.emvx.co.uk/?p=7</guid>
		<description><![CDATA[If you are familiar with magnetic  stripe card processing, you may not be aware that the online processing of an  EMV “Chip and PIN” card allows the authenticity of a payment card to be  verified, in addition to checking whether there are sufficient funds available  for the payment.
An EMV card generates [...]]]></description>
			<content:encoded><![CDATA[<p>If you are familiar with magnetic  stripe card processing, you may not be aware that the online processing of an  EMV “Chip and PIN” card allows the authenticity of a payment card to be  verified, in addition to checking whether there are sufficient funds available  for the payment.</p>
<p>An EMV card generates a unique  “Authorisation Request Cryptogram” for each transaction that requires online  authorisation. This is calculated by encrypting the card and transaction data  using a secret key that is known only to the card and the card issuer. When the  transaction details are sent to the issuer during the authorisation process, the  issuer can then use its copy of the secret key to verify that the cryptogram for  the transaction is correct, and that therefore the card is genuine.</p>
<p>Once the issuer is satisfied that  the request is genuine and they wish to authorise the transaction, they will  generate an authorisation response cryptogram, which the card can then use to  authenticate that the authorisation for the payment came from the genuine issuer  of the card.</p>
<p>These checks allow the EMV card and  the issuer to verify the authenticity of each other, and thus protect the  cardholder from being debited for fraudulent  transactions.</p>
<p>This is just one of the many  benefits that EMV migration can bring. The CreditCall EMV kernels provide a  simple but powerful way to add EMV level 2 to ATMs, PoS devices and unattended payment terminals such as kiosks.</p>
<p>Check out <span style="text-decoration: underline;"><a title="http://www.emvx.co.uk/" href="http://www.emvx.co.uk/">www.emvx.co.uk</a></span> for further  details of these EMV Level 2 Kernels.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.emvx.co.uk/index.php/security/emv-online-security/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>EMV Approval Expiry</title>
		<link>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/emv-approval-expiry/</link>
		<comments>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/emv-approval-expiry/#comments</comments>
		<pubDate>Thu, 03 Dec 2009 15:51:52 +0000</pubDate>
		<dc:creator>palcock</dc:creator>
				<category><![CDATA[EMV Certification and Approvals]]></category>
		<category><![CDATA[emv complinace]]></category>
		<category><![CDATA[EMV Kernal]]></category>
		<category><![CDATA[EMV Kernel]]></category>
		<category><![CDATA[EMV Kernel approval]]></category>
		<category><![CDATA[EMV Kernel expiry]]></category>
		<category><![CDATA[emv level 2]]></category>
		<category><![CDATA[EMV Transaction]]></category>
		<category><![CDATA[EmvX]]></category>
		<category><![CDATA[Level 2 Kernel]]></category>
		<category><![CDATA[low-value transaction]]></category>

		<guid isPermaLink="false">http://blog.emvx.co.uk/?p=4</guid>
		<description><![CDATA[This year, for the first time, EMVCo have implemented a policy of revoking all EMV Level 2 letters of approval that are more than 3 years old. Although EMVCo offer the option to renew an existing EMV Kernel approval by submitting it for retesting, the fact that they regularly issue specification update bulletins effectively means [...]]]></description>
			<content:encoded><![CDATA[<p>This year, for the first time, EMVCo have implemented a policy of revoking all EMV Level 2 letters of approval that are more than 3 years old. Although EMVCo offer the option to renew an existing EMV Kernel approval by submitting it for retesting, the fact that they regularly issue specification update bulletins effectively means that this option is not possible. Therefore, any EMV Level 2 Kernels greater than 3 years old can no longer claim to be EMV-compliant, which is a problem when trying to market and deploy new terminals.</p>
<p>It is of course possible to update an existing EMV solution to meet the latest specifications, but the sheer volume of specification changes means that this is a significant task. A better approach therefore, is to migrate to an EMV Kernel that is compliant with the latest EMV standards, such as the CreditCall EMV Kernels. Check out <a href="http://www.emvx.co.uk/">www.emvx.co.uk</a> for further details of these EMV Level 2 Kernels.</p>
<p>Found this Interesting, but struggling with the terminology? Why not consult the helpful Glossary of Terms at <a href="http://www.emvx.co.uk/glossary.aspx">http://www.emvx.co.uk/glossary.aspx</a> EMV de-mystified!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/emv-approval-expiry/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
