EPayments Project Final Report of Initial Project Work rnib innovation Unit



Download 246.91 Kb.
Page3/10
Date20.10.2016
Size246.91 Kb.
#5754
1   2   3   4   5   6   7   8   9   10

2.3 The Transport Stream

In this stream, an attempt was made to capture any available literature around the accessibility of payment systems in the public transport sector. More information about the various reports can be found in Appendix C.




  • Payment systems based on near field communication technology are extremely popular.

  • There is hardly any research done to ascertain the accessibility of these payment systems for blind and partially sighted users.

  • There are an increased number of self-service terminals in use for ticketing and for information provision and there seems to be no accessibility features in any of the systems in use.



2.4 Existing Standards

While conducting the literature review, the project team also looked at identifying any existing standards and guidelines that are related to the accessibility of ePayment systems in all the above streams. Some of the more relevant standards are listed below.




  • ISO/IEC 7810 (2003) Identification cards: Physical characteristics2

  • ISO 9564: 2002 Banking - Personal Identification Number (PIN) management and security. Parts 1, 2, 3 & 43

  • EBS100 V3 (October 2004) Keyboard Layout for ATM and POS PIN Entry Devices4

  • CEN/TS 15291 (2006) Identification card system - Guidance on design for accessible card-activated devices5

  • Various smart card standards6



3.0 Summary of issues with ePayment methods

So that the top level issues related to ePayment solutions could be better understood, the project team performed a brief review of the various ePayment methods mentioned in the introduction. At this stage the findings are generated by expert opinions from either having used these methods or by performing desk based research on the different solutions.



3.1 ePayment methods




3.1.1 Contactless Cards

An example of the contactless card technology being used is the VISA PayWave7.


The issues associated with contactless cards can be summarised under five headings. Within these five headings are the issues which have been identified as being problematic for blind and partially sighted people.


  1. Location

  • Locating the terminal in the environment




  1. Terminal design (hardware)

  • Locating the trigger on the terminal

  • Confirming payment amount

  • Size of payment screen

  • Type of font used

  • Size of text

  • Lack of text contrast

  • Physical receipt



  1. Terminal design (Software)

  • Size of text on the display

  • Lack of text contrast on the display

  • Clarity of symbols used (e.g. are the symbols clear and unambiguous)

  • Type of font used

  • Lack of adjustability of User Interface (UI) (Cant make font or buttons bigger)

  • Error message reporting (System failure, not enough money etc)

  • Lack of spoken prompts

  • Accessibility of the confirmation of your action (so don’t swipe it twice or possibly not at all and get a fine



  1. Card design

  • Card identification

  • Card orientation (if this is an issue)



  1. Security & audit

  • Unverified payment



As well as the issues mentioned above, it is likely that a contactless card will need to be reloaded with funds. This could be done in a variety of ways from going into a shop which provides this service, using a self service kiosk or using a website. Therefore when this method is considered, the recharging methods also need to be factored in as if the customer cannot add funds onto the card, it is next to useless.


3.1.2 Chip and PIN

An example of Chip and PIN is the Chip and PIN machine at the Post Office.


The issues associated with Chip and PIN systems are somewhat similar to those of contactless cards, however they require a greater interaction between the user and the device. Therefore this method has a larger number of issues associated with it. The issues can be summarised into five headings and are as follows:


  1. Location

  • Locating the terminal




  1. Terminal design (hardware)

  • Inconsistent terminal keypad layout

  • Inconsistent card slot position

  • Type of font used

  • Size of text on keys

  • Lack of text contrast on the keys

  • Lack of accessibility markings according to APACS guidelines

  • Size of payment screen

  • Physical receipt




  1. Terminal design (Software)

  • Inconsistent menu system

  • Confirming payment amount

  • Size of text on the display

  • Type of font used

  • Lack of text contrast on the display

  • Clarity of symbols used (e.g. are the symbols clear and unambiguous)

  • Size of on-screen buttons (touchscreen - I've not seen any but that doesn’t mean its not possible)

  • Lack of adjustability of UI (Cant make font or buttons bigger)

  • Lack of spoken prompts

  • Error message reporting (System failure, not enough money etc)




  1. Card design

  • Card identification

  • Inserting the card the wrong way round




  1. Security & audit

  • Shoulder surfing

  • Forgetting PIN

  • Entering PIN associated with wrong card

  • Incorrectly entering PIN



3.1.3 Self-service Kiosks

An example of a self service kiosk is the Transport for London (TfL) automated ticket machine.


Self service kiosks can be simple or complex solutions depending on their design. For instance, there are several types of kiosk in use on the London Underground and these range from simple push button to select the ticket type to touch screen based solutions. Therefore the issues and challenges can vary. The issues, divided into four categories are as follows:


  1. Location

  • Locating the kiosk




  1. Terminal design (hardware)

  • Lack of text contrast (on the terminal)

  • Size of buttons

  • Button configuration (select/back/payment etc)

  • Locating buttons

  • Type of font used

  • Locating key features (e.g. payment terminal, coin dispenser)

  • Physical receipt




  1. Terminal design (Software)

  • Lack of spoken prompts

  • Clarity of symbols used (e.g. are the symbols clear and unambiguous)

  • Size of text on the display

  • Type of font used

  • UI not accessible

  • Size of on-screen buttons (touchscreen)

  • Button configuration (select/back/payment etc)

  • Lack of adjustability of UI (Cant make font or buttons bigger)

  • Complexity of menu structure




  1. Security & audit

  • Lack of assistance



3.1.4 Pre-paid/gift cards

An example of the gift cards is the boots gift card.

As these cards require the user to hand them over to a cashier, the issues associated with them are restricted. However if one of these cards needs to be used with a chip and PIN machine or self service kiosk, then the issues with these cards will be combined with the issues associated with those solutions. The issues are as follows:


  1. Card design

  • Card identification




  1. Security & audit

  • Transaction receipt

  • Balance enquiry

  • Card stolen



3.1.5 Near Field Communication (NFC)

An example of where NFC is available is the Bay Area Transport system in San Francisco.


Near field communication based systems are relatively new and are therefore not that widespread. However that does not mean that these systems do not have potential problems which would make using these solutions problematic for blind and partially sighted people. As there has not been any close interaction between the experts and these systems, the issues identified have been generalised. The issues have been placed into seven groups as follows:


  1. Location

  • Locating the terminal




  1. Terminal design

  • Location of trigger on terminal (vending machine, ticket barrier)




  1. Reader and transmitter interaction

  • Transmitter (the phone) may have to be placed in correct orientation on the reader to work.




  1. Availability

  • May only work on certain handsets




  1. Design

  • phone software (general) - there are lots of potential issues

  • phone hardware (general) - there are lots of potential issues




  1. Preparation for use

  • Loading/starting NFC application on the mobile device

  • Adding funds onto the NFC device




  1. Security

  • Transmission of funds + success criteria/messages

  • Phone hijacked and credit stolen

  • Phone greater target for thieves



3.1.6 Mobile phone payment (SMS)

An example of SMS payment would be obtaining international calling credit. As this method relies on using a communication method rather than a specific payment method the issues mainly relate to the device being used to send the payment. As such the issues have been generalised somewhat to account for this.




  1. Format of text

  • Html vs. plain text




  1. Flexibility of information

  • Having to copy numbers such as PIN’s and access codes any confirmation text




  1. Design

    Mobile phone software (general) - there are lots of potential issues

  • Mobile phone hardware (general) - there are lots of potential issues

  • If SMS is deleted is credit lost?

  • Confirmation of payment & receipt




  1. Initial information

  • Need to access information in order to get credit or services (e.g. access to the web)



3.1.7 Mobile phone payments (apps requiring bank details)

An example of this would be the Nokia Maps application when purchasing a subscription.


This solution could involve an application requesting card details (such as the Nokia Maps) or involve an application which stores the card details (such as Nokia Wallet) which then interacts with other systems and applications when required. The issues of using this are generally related to the actual device being used rather than the specific payment solution. As such the issues have been generalised somewhat to account for this.


  1. Design

  • Mobile phone software (general) - there are lots of potential issues

  • Mobile phone hardware (general) - there are lots of potential issues

  • Card details application - there are lots of potential issues

  • Confirmation of payment & receipt




  1. Security

  • Transferring card details onto a phone

  • Are card details visible on screen?

  • Are card details spoken?

  • Can card details be lifted from phone via a hijack?




  1. Payment

  • Authorisation + completion information/notification



3.1.8 Online transactions (Cards/Direct Debits etc)

An example of this would be buying tickets for a show.


Using a card online will mean interacting with a payment/eCommerce system on an organisations website (such as Amazon) or a standard banking website or specialist payment website linked to from a website (such as RBS World Pay or PayPal). In some cases there may be an additional interaction if the website links to the MasterCard and visa verification systems (e.g. “Verified by Visa”). As there are a number of ways of making a payment and each website would have subtle differences, the issues have been generalised.


  1. Design

  • Inaccessibility of retail/banking websites

  • Inaccessibility of authentication systems such as the “PIN Entry” system from Barclays.

  • Inaccessibility of software based authentication systems like virtual keyboards for entering PIN/Password.




  1. Security

  • Inaccessibility of software based authentication systems such as on screen keyboards for entering PIN/Password.




Download 246.91 Kb.

Share with your friends:
1   2   3   4   5   6   7   8   9   10




The database is protected by copyright ©ininet.org 2024
send message

    Main page