<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>June 2026 on AFCS Blog</title>
		<link>https://afcsblog.ingonoka.com/2026/06/</link>
		<description>Recent content in June 2026 on AFCS Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="https://afcsblog.ingonoka.com/2026/06/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Account-Based QR Ticketing - How to Match QR Entry and Exit Records</title>
				<link>https://afcsblog.ingonoka.com/post/account-based-ticket-matching/</link>
				<pubDate>Thu, 11 Jun 2026 00:00:00 +0800</pubDate>
				<guid>https://afcsblog.ingonoka.com/post/account-based-ticket-matching/</guid>
				<description>&lt;div id=&#34;preamble&#34;&gt;&#xA;&lt;div class=&#34;sectionbody&#34;&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;Account-based QR ticketing is surprisingly challenging to implement.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;The timing and throughput requirements of a mass transit system such as the LRT and MRT lines in Manila  require an offline decision by the gate or validator. We also have to accept that delayed uploads and missing records cannot entirely be avoided.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;As a result, the matching algorithm for entry and exit records gets riddled with exceptions. In fact, no matter how we design the system, a certain number of records will refuse any attempt of matching and fare calculation.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;While I will focus on the matching of entry and exit records, a complete solution must also consider liability allocation and requires a certain amount of risk acceptance. Any attempt to make an QR account-based ticketing system fool prove with no chance of even the tiniest loss will fail!&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;I have gathered my thoughts on the topic, but I feel that there is a lot more to say. Please do not consider this little write-up the be-all and end-all on the subject.&lt;/p&gt;&#xA;&lt;/div&gt;</description>
			</item>
			<item>
				<title>Account Based QR Ticketing - My Grand Design</title>
				<link>https://afcsblog.ingonoka.com/post/design-for-account-based-transit-card/</link>
				<pubDate>Tue, 02 Jun 2026 00:00:00 +0800</pubDate>
				<guid>https://afcsblog.ingonoka.com/post/design-for-account-based-transit-card/</guid>
				<description>&lt;div id=&#34;preamble&#34;&gt;&#xA;&lt;div class=&#34;sectionbody&#34;&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;I was asked recently how I would design an account-based QR code ticketing solution. That is a simple question. But it would require more than one article to even just scratch the surface.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;It brought back memories of discussions about static offline authentication and other topics which I thought are buried and forgotten under the thousands of pages of EMV specification and the long-winded migration from magnetic stripe to chip cards.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;But here we go again. The good old magnetic stripe swipe under the &amp;#34;modern&amp;#34; guise of a QR code scan.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;Nevertheless, I am old enough to remember most of it and decided to take a quick shot in this article.&lt;/p&gt;&#xA;&lt;/div&gt;</description>
			</item>
			<item>
				<title>Account-Based Ticketing - Too much Fraud Potential?</title>
				<link>https://afcsblog.ingonoka.com/post/account-based-transit-risk/</link>
				<pubDate>Mon, 01 Jun 2026 00:00:00 +0800</pubDate>
				<guid>https://afcsblog.ingonoka.com/post/account-based-transit-risk/</guid>
				<description>&lt;div id=&#34;preamble&#34;&gt;&#xA;&lt;div class=&#34;sectionbody&#34;&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;A message exchange on FaceBook prompted me to write a response to my friend Regie, which became so long that I turned it into an article.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;I already talked about the risk of anonymous account-based transit cards in my previous &lt;a href=&#34;https://afcsblog.ingonoka.com/post/account-based-vs-stored-value/&#34;&gt;article&lt;/a&gt; &lt;span class=&#34;citation&#34;&gt;(&lt;a href=&#34;#Noka:2026ad&#34;&gt;1&lt;/a&gt;)&lt;/span&gt;. In this piece I am adding a couple thoughts on the topic.&lt;/p&gt;&#xA;&lt;/div&gt;</description>
			</item>
	</channel>
</rss>
