Book contents
- Frontmatter
- Contents
- Foreword by Kevin Gillick
- Acknowledgements
- Part I Introduction
- Part II Technology
- 4 Biometrics
- 5 Security and cryptography
- 6 Card technology
- 7 Readers and terminals
- 8 Application selection: the ISO 7816 family
- 9 JavaCard and GlobalPlatform
- 10 Multos
- 11 Other operating systems
- 12 Card management systems
- Part III Business requirements
- Part IV Implementation
- Appendix A Glossary
- Appendix B Further reading
- Appendix C Standards
- Index
- References
12 - Card management systems
from Part II - Technology
Published online by Cambridge University Press: 11 August 2009
- Frontmatter
- Contents
- Foreword by Kevin Gillick
- Acknowledgements
- Part I Introduction
- Part II Technology
- 4 Biometrics
- 5 Security and cryptography
- 6 Card technology
- 7 Readers and terminals
- 8 Application selection: the ISO 7816 family
- 9 JavaCard and GlobalPlatform
- 10 Multos
- 11 Other operating systems
- 12 Card management systems
- Part III Business requirements
- Part IV Implementation
- Appendix A Glossary
- Appendix B Further reading
- Appendix C Standards
- Index
- References
Summary
Legacy card management functions
Most card issuers will need some form of card management system (CMS), that allows them to keep track of the cards they have issued, expiry dates, etc. The CMS may also contain the details on the card, or may refer to another database (for example, a personnel database) that contains this information. The CMS may also include functions for maintaining the data (for example, name and address data), but for larger systems this is more often regarded as a separate customer management function.
For complex applications such as credit-card issuing, the CMS may link to several other systems, such as an authorisation system, call centre, statement and mailing management.
A CMS for magnetic stripe cards is usually a fairly simple ‘flat’ file structure, providing a link between the card number and the external data. With this kind of structure it is quite easy to give a call centre, for example, limited read-only access and the ability to make notes linked to the card or account, but they cannot affect transactions carried out by the card. The CMS can also act as the interface to a bureau or outside processor, so that the card issuer maintains the database but the bureau handles all the card-related functions.
Additional functions for smart-card management
When an issuer moves to a smart-card platform, it often assumes that it will need a smart-card management system (SCMS).
- Type
- Chapter
- Information
- Multi-application Smart CardsTechnology and Applications, pp. 104 - 116Publisher: Cambridge University PressPrint publication year: 2007