On This Page

{#jumplink-list}  
[Markdown](/content/cybsdeveloper2021/amer/en/docs/cybs/en-us/urban-mobility/developer/ctv/rest/mass-transit/um-intro-overview/um-intro-models/um-intro-mult-accts.md)  
Filter  
FILTER BY TAG

Multiple Accounts for Processing Functions {#um-intro-mult-accts}
=================================================================

Mass transit systems can use multiple accounts to support a variety of processing functions. Processing functions include these types of tasks:

* Creating tap tokens
* Processing payment requests
* Retrieving card hash values
* Supporting customer journey history inquiries
  Each processing function is handled by a separate account to improve security, isolation, and operational clarity. These accounts are available in the Mass Transit solution:  
  **Account 1** : This account processes tap token create requests only. For this option, the validators communicate directly with `Cybersource`. Using a separate account enables you to deploy a separate security key to the validator system.  
  **Account 2** : This account processes payment requests using tokens. You can also choose to further separate debt recovery transactions from standard payment transactions. In that case, **account 2a** is dedicated to standard payment transactions, and **account 2b** is dedicated to debt recovery transactions.  
  **Account 3**: This account processes card hash retrieval requests only. The responses include the full, unmasked card hash value. Using a separate account enables you to deploy a separate security key to the validator system.  
  **Account 4** : This account operates a customer service web portal where riders can make journey history inquiries. The riders provide the card number to a hosted payment service (such as `Cybersource` Secure Acceptance) where they register as a user. Registration produces the `TMS` instrument identifier token and the card scheme PAR value. These values can be used by your back-office system to look up journey and billing information.

#### Figure:

Journey History Request with Token Creation Workflow  
![Workflow diagram showing journey history service using tokens process.](/content/dam/documentation/cybs/en-us/topics/payments-processing/card-processing/mass-transit/images/mtt-journey-history-390x375.svg/jcr:content/renditions/original)  
RELATED TO THIS PAGE