Warning: Declaration of Jetpack_IXR_Client::query() should be compatible with IXR_Client::query(...$args) in /home/uali2451/public_html/mobileafc.net/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php on line 54

Warning: Cannot modify header information - headers already sent by (output started at /home/uali2451/public_html/mobileafc.net/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php:122) in /home/uali2451/public_html/mobileafc.net/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home/uali2451/public_html/mobileafc.net/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php:122) in /home/uali2451/public_html/mobileafc.net/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home/uali2451/public_html/mobileafc.net/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php:122) in /home/uali2451/public_html/mobileafc.net/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home/uali2451/public_html/mobileafc.net/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php:122) in /home/uali2451/public_html/mobileafc.net/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home/uali2451/public_html/mobileafc.net/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php:122) in /home/uali2451/public_html/mobileafc.net/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home/uali2451/public_html/mobileafc.net/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php:122) in /home/uali2451/public_html/mobileafc.net/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home/uali2451/public_html/mobileafc.net/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php:122) in /home/uali2451/public_html/mobileafc.net/wp-includes/rest-api/class-wp-rest-server.php on line 1673

Warning: Cannot modify header information - headers already sent by (output started at /home/uali2451/public_html/mobileafc.net/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php:122) in /home/uali2451/public_html/mobileafc.net/wp-includes/rest-api/class-wp-rest-server.php on line 1673
{"id":353,"date":"2020-03-04T13:59:21","date_gmt":"2020-03-04T13:59:21","guid":{"rendered":"http:\/\/mobileafc.net\/?p=353"},"modified":"2020-03-04T14:25:12","modified_gmt":"2020-03-04T14:25:12","slug":"benefits-and-drawback-of-emv-contactless-account-based-ticketing","status":"publish","type":"post","link":"https:\/\/mobileafc.net\/?p=353","title":{"rendered":"Benefits and drawback of EMV Contactless Account-based Ticketing"},"content":{"rendered":"\n

EMV Contactless Account-based Ticketing <\/h3>\n\n\n\n

Source: Calypso<\/a><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The major benefit of EMV Contactless certification <\/h4>\n\n\n\n

It relies on cards for which the certification is very thorough and a virtual guarantee of interoperability between cards and terminals. <\/p>\n\n\n\n

However, for EMV, the validator (and the whole chain up to the Acquirer) must be PCI DSS Certified. <\/p>\n\n\n\n

Using EMV contactless bank cards as secure ID media<\/h3>\n\n\n\n

It is a common way of using EMV contactless bank cards for public transportation.<\/p>\n\n\n\n

This approach is employed by TFL (Transport For London). It consists of checking that a card is genuine and has not been black-listed when it is used for validating. <\/p>\n\n\n\n

In standard EMV contactless transactions, the card has authorization for a small amount until the next chip and PIN transaction, typically a maximum of 20 Euros and when it is used, the counter is decreased from the amount paid. The transaction can be done offline. When the amount is reached, an online connection and\/or PIN transaction is necessary to authorize the payment and reset the counter. <\/p>\n\n\n\n

On the other hand, in transport, validators check that the card is genuine, acceptable and not hotlisted. This is performed in real-time and does not require an online transaction. Then a \u00a30 transaction is triggered for every tap. Validators\u2019 hotlists are regularly updated. <\/p>\n\n\n\n

An authorization for an amount greater than the maximum trip is requested from the back-office to the bank. If the requested is accepted, this reserves the amount and therefore guarantees payment. If the request is denied, the information is then sent to validators to update the hotlist. This has for consequence that the first usage is always allowed. <\/p>\n\n\n\n

The issuing bank will cover the cost of the very first trip, even when the account was blocked. <\/p>\n\n\n\n

Major shortcomings of ABT <\/h3>\n\n\n\n

Network availability shortcoming<\/h4>\n\n\n\n

Traditional ABT systems rely heavily on networks as transactions are processed in a back-office server, which is not available when the network is down. <\/p>\n\n\n\n

ABT terminals can buffer the transaction request and send the request to the back-office when the network connection is resumed. In that case, the terminal takes the risk of emulating a successful transaction for media that are linked to accounts that cannot be charged for lack of funds or for any other reason. <\/p>\n\n\n\n

Concessionary profiles<\/h4>\n\n\n\n

As \u201cpure\u201d ABT POs only contain an ID, unless a network connection is available, there is no way for a terminal to ascertain whether the PO holder is entitled to concessionary fares.<\/p>\n\n\n\n

Ticket inspection<\/h4>\n\n\n\n

As the information relative to ABT transactions is registered in back-office (and optionally in validators in addition to being stored in back-office), inspecting POs also requires accessing the back-office system. <\/p>\n\n\n\n

In the metro, train, and in some bus and tram networks, ticket inspection is performed away from the validator\/gate which means that relying on accessing the data directly from the validator\/gate used by the traveler for inspection purposes is simply not feasible.<\/p>\n\n\n\n

Others generic issues related to EMV : <\/h4>\n\n\n\n