The Connect Card Site will be handed to an independent subsidiary of all of the participating public transit services. The site promoting the Connect Card will be http://www.connectcard.org/ while the patron login site will be http://my.connectcard.org. Each Card Owner will be required to have a unique email address or Google Login. They can also choose to use Google to authenticate. There are three types of entries that can be associated with a card. The Owner (legal card owner), the Primary/Secondary Payer (adding funds), and the User (allowed entity to use the card.
The owner is the person that acquired and registered the card with ACTA. The owner will set up a Question/Answer combination that only they are likely to know. This improves security, while only adding minimal demands on a MySQL database (what is likely holding information now). The owner will also be allowed to do the following
- Edit User information (N/A on half fare cards)
- Edit Payer Information or restrict payer allowances
- Set or change Question/Answer combination
- Change demographic information
- Add card to resource pool
- Disable Card / Destroy Card
- Link with App
- View Usage History
In the case of half fare cards, children cards are owned by a parent. A card must be assigned to a child which the card will be disabled and deleted 1 week after the child’s 12th birthday. For Disabled Half Fare cards, ownership of such a card is restricted to the use of the owner.
Payers can be different from users or owners. For example, a person that receives funds from work for transit will have their employer as a payer. A person receiving financial assistance for Medical Assistance qualified appointments may have MATP or Traveler’s aide as a payer. The owner can restrict adding funds to the Owner and Payers only. This will prevent unauthorized usage, or manage accounting of usage.
The Secret Question/Answer combination is a simple way for dramatically improving security. Only the card owner will be able to see or edit this information. The owner can change demographic information including Owner Contact, or user contact information.
The owner can also create a resource pool, This is funds that can be set in a neutral place and allows the owner to move funds from the resource pool to individual cards. This is good for businesses, or families. Cards can be set to disable which will not deactivate the card, but prevent it from being used. Payers will still be able to add funds. Destroy the card will assume it to be lost or stolen. When a card is destroyed, funds are sent to the owner’s resource pool, and the card can not be used until registered again. ACTA will reserve the right to question anyone possessing a destroyed card and attempting to use it.
With NFC enabled devices and a cellular connection, the card can be linked with an app. This will make the card inactive, and therefore dormant. The owner can then use the web site or app to unlink card. (Un)Linking will take up to 60 minutes to take effect. At this time, only Android will support this feature. This is due to OS level locking of the NFC system in iOS devices to Apple Pay.
Usage History will be in a calendar format, and will show the route (and vehicle number) as well as the times in which the card was used. The owner can allow this information to be viewable to the payer, or user. Also, information to the payer can be limited to certain days or times. This will allow for privacy while allowing the payer with the information required.
A payer is a primary or secondary source other than the owner in which funds can be easily added. This is designed to reduce misuse of easily available payments. The owner can make it possible for anyone to add funds by paying with credit card or Google Wallet and going to http://fund.connectcard.com.
However, a primary or secondary payer will likely have a more reliable and automated method of adding funds to the card. In which case, the payer will see the owner name, user name, owner contact, and the card number. With the owner’s permission, they can also view usage history or get verification authentication.
The user is someone other than the owner who is allowed to use the card. The only time that the user can not be set to owner is in the case of Disabled Adult Cards, or Connect-Silver (Elderly/ACCESS). In both cases, the cards are intended for a particular person. Another instance where a user can not be changed is Fun-Ride (for children). There will be instances such as schools which will implement the Connect Card System. Owner/User is managed by the school, and not by ACTA or Connect Card
The user will be able to view Payer Information, Owner Contact Information, and edit demographic. They will also be able to disable the card (in case it is misplaced or lost). The user will also be able to (Un)Link with the app. The owner will be able to see if the card is disabled, or (Un)Linked. The owner will also be able to see the demographic information of the user. With the owner’s permission, the user can also view usage details, or add funds.