<?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; EMV application label</title>
	<atom:link href="http://blog.emvx.co.uk/index.php/tag/emv-application-label/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>Application Selection &#8211; Name Display</title>
		<link>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/application-name-displayed-during-emv-application-selection/</link>
		<comments>http://blog.emvx.co.uk/index.php/emv-certification-and-approvals/application-name-displayed-during-emv-application-selection/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 10:33:39 +0000</pubDate>
		<dc:creator>palcock</dc:creator>
				<category><![CDATA[EMV Certification and Approvals]]></category>
		<category><![CDATA[Application Selection]]></category>
		<category><![CDATA[EMV application label]]></category>
		<category><![CDATA[emv complinace]]></category>
		<category><![CDATA[EMV Kernel]]></category>
		<category><![CDATA[EMV Specification Update]]></category>
		<category><![CDATA[EMV Transaction]]></category>
		<category><![CDATA[Level 2 Kernel]]></category>

		<guid isPermaLink="false">http://blog.emvx.co.uk/?p=26</guid>
		<description><![CDATA[EMVCo have finally corrected one of  the longest standing anomalies in the EMV specifications, with the release of  EMVCo Specification Update Bulletin No. 71.
When there are multiple payment  applications present on an EMV card, or the card configuration requires  cardholder confirmation, payment terminals will display the list of applications  to [...]]]></description>
			<content:encoded><![CDATA[<p>EMVCo have finally corrected one of  the longest standing anomalies in the EMV specifications, with the release of  EMVCo Specification Update Bulletin No. 71.</p>
<p>When there are multiple payment  applications present on an EMV card, or the card configuration requires  cardholder confirmation, payment terminals will display the list of applications  to the cardholder to allow them to select an EMV application to use for the  transaction.</p>
<p>EMV cards will often include an  ‘application preferred name’, which is the name of the card application in the  cardholder’s local language. Although this is the preferred name to display to  the cardholder, it will not always be possible to do so as the name may use an  ‘issuer code table’ that is not supported by the terminal. For example,  a  terminal in Europe may not contain a display  font that allows Arabic characters to be displayed.</p>
<p>Therefore, normally all EMV card  applications will contain an ‘application label’ which contains only characters  in the common character set that all EMV-capable terminals are required to  support, which should ensure that there will always be a name that can be  displayed to the cardholder.</p>
<p>Unfortunately, although the presence  of the application label on the EMV card is mandatory when using the PSE  directory method during application selection, it was only defined as optional  when selecting the application using the list of Applications method. Therefore   it has never been possible to guarantee the presence of the application label on  a chip card – until now! EMVCo have finally resolved this by issuing <em>Specification Update Bulletin No. 71</em> that  now makes the application label mandatory on all new EMV-compliant cards. This  will finally mean that EMV Level 2 Kernels used by payment terminal vendors will  always have a name to display during application selection, and should no longer  need to implement default name processing.</p>
<p><strong>The CreditCall  EMV kernels are compliant with all the latest industry requirements, and provide  a simple but powerful way to add EMV Level 2 compliance to payment devices. Check out  <a title="http://www.emvx.co.uk/" href="http://www.emvx.co.uk/">www.emvx.co.uk</a> 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/application-name-displayed-during-emv-application-selection/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>
