<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Payment Systems Blog &#187; Store and Forward</title>
	<atom:link href="http://www.paymentsystemsblog.com/topics/store-and-forward/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.paymentsystemsblog.com</link>
	<description>David D. Bergert</description>
	<lastBuildDate>Sat, 10 Apr 2010 13:32:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<!-- podcast_generator="podPress/8.8" - maintenance_release="8.8.4" -->
		<copyright>Copyright &#xA9; 2010 Payment Systems Blog </copyright>
		<managingEditor>podcast@paymentsystemsblog.com (Dave Bergert)</managingEditor>
		<webMaster>podcast@paymentsystemsblog.com (Dave Bergert)</webMaster>
		<category>posts</category>
		<ttl>1440</ttl>
		<itunes:keywords>Payment Systems, ISO8583, PABP, PA-DSS, PCI, Security, Credit, Debit</itunes:keywords>
		<itunes:subtitle></itunes:subtitle>
		<itunes:summary>Payment Systems Podcast is a podcast that address the subject of Payments Systems, their operations, development, security and other experiences related to payment processing.</itunes:summary>
		<itunes:author>Dave Bergert</itunes:author>
		<itunes:category text="Technology"/>
<itunes:category text="Business"/>
<itunes:category text="Technology">
	<itunes:category text="Software How-To"/>
</itunes:category>
		<itunes:owner>
			<itunes:name>Dave Bergert</itunes:name>
			<itunes:email>podcast@paymentsystemsblog.com</itunes:email>
		</itunes:owner>
		<itunes:block>No</itunes:block>
		<itunes:explicit>no</itunes:explicit>
		<itunes:image href="http://www.paymentsystemsblog.com/images/pspodcast.png" />
		<image>
			<url>http://www.paymentsystemsblog.com/images/pspodcast.png</url>
			<title>Payment Systems Blog</title>
			<link>http://www.paymentsystemsblog.com</link>
			<width>144</width>
			<height>144</height>
		</image>
		<item>
		<title>PCI PA-DSS &#8211; Changes to Store and Forward processing</title>
		<link>http://www.paymentsystemsblog.com/2008/05/05/pci-pa-dss-changes-to-store-and-forward-processing/</link>
		<comments>http://www.paymentsystemsblog.com/2008/05/05/pci-pa-dss-changes-to-store-and-forward-processing/#comments</comments>
		<pubDate>Tue, 06 May 2008 02:37:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[PA-DSS]]></category>
		<category><![CDATA[PABP]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Store and Forward]]></category>
		<category><![CDATA[SAF]]></category>

		<guid isPermaLink="false">http://www.paymentsystemsblog.com/?p=37</guid>
		<description><![CDATA[If you read the PCI standards carefully and hang out with PCI geeks here or here you will notice that PCI applies to post-auth data and not necessarily pre-authorization data. &#8212; I think the official language is &#8220;subsequent to the authorization&#8221;
On May 1st, a payment processor modified their message formats as a part of their [...]]]></description>
			<content:encoded><![CDATA[<p>If you read the PCI standards carefully and hang out with PCI geeks <a href="http://forum.aegenis.com/">here</a> or <a href="http://groups.yahoo.com/group/PCI_standards/">here</a> you will notice that PCI applies to post-auth data and not necessarily pre-authorization data. &#8212; I think the official language is &#8220;subsequent to the authorization&#8221;</p>
<p>On May 1st, a payment processor modified their message formats as a part of their PCI compliance to not send Field 35 in SAF Advice transactions and would just send the PAN in field 2 and Expiration Date in field 14, instead of DE 35.</p>
<p>Also, from a <a href="http://forum.aegenis.com/showthread.php?t=465">forum post</a> from &#8220;<a href="http://www.withamlabs.com/">andrewj</a>&#8221;</p>
<blockquote><p>Another update on this (if you are from Australia) &#8211; there is a change being made to <a href="http://www.saiglobal.com/shop/Script/Details.asp?DocN=AS0733779980AT">AS2805.2</a> to change the track 2 field from mandatory to optional in 04&#215;0 messages. This should be released sometime this month.</p></blockquote>
<p>This is a good trend in the industry, hopefully others will take this example and continue to trend.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.paymentsystemsblog.com/2008/05/05/pci-pa-dss-changes-to-store-and-forward-processing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
