Multiple Accounts for Processing Functions

Mass transit systems can have multiple accounts for each processing function.

Account 1

: Processes tap token create only. For this option, the validators communicate directly with

Cybersource

. Using a separate account allows you to deploy a separate security key to the validator system.

Account 2

: 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

: Processes card hash retrieval requests only. The responses include the full unmasked card hash value. Using a separate account allows you to deploy a separate security key to the validator system.

Account 4

: Operates a customer service web portal where riders make journey history enquiries. The riders provide the card number to a hosted payment service (such as

Cybersource

Secure Acceptance) where they register themselves. 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: