{"id":251052,"date":"2026-07-13T00:55:34","date_gmt":"2026-07-12T21:55:34","guid":{"rendered":"https:\/\/1kitap1.com\/en\/acquiring-card-payments-ilya-dubinsky\/"},"modified":"2026-07-13T00:55:34","modified_gmt":"2026-07-12T21:55:34","slug":"acquiring-card-payments-ilya-dubinsky","status":"publish","type":"post","link":"https:\/\/1kitap1.com\/en\/acquiring-card-payments-ilya-dubinsky\/","title":{"rendered":"Acquiring Card Payments – Ilya Dubinsky"},"content":{"rendered":"
\"<\/figure>\n

The standard actually speaks of \u201cDF Name\u201d rather than application ID, but from practical point of view the terms are interchangeable. The FID is a 2-byte value which can be thought of as a reference to physical location of the dedicated file. For instance, the master file always has FID of 0x3F00, the first dedicated file immediately beneath it has a FID of 0x7F01 and so the forth so a terminal needs to know the exact structure and order of the DF tree on the card to be able to reference it correctly.<\/p>\n

That requires a certain level of knowledge of card internals complicating interoperability. In contrast to it, the AID or DF name is a byte string of up to 16 bytes which does not depend on the application location in the chip file system. To better understand the difference between the two reference methods, consider the task of invoking a browser from within a program on a personal computer to navigate to a website.<\/p>\n

Knowing the full path to the browser executable is one way of launching it, but it requires some knowledge regarding browsers deployed on the particular machine as well as their executable locations and filenames. That is similar to referencing a dedicated file using FID or an FID path. Alternatively, many operating systems provide URL handlers and a program could invoke a generic URL handler and pass the web page address to it leaving it to the OS to locate and launch the correct browser.<\/p>\n

The AID can be either registered or proprietary. Its format and registration process are defined in ISO\/IEC 7814-5. Obviously, the proprietary AID can be of arbitrary format occupying anywhere between 1 to 16 bytes. A registered AID consists of two parts: the registered application provider identifier (RID) and the proprietary application identifier extension (PIX). The rationale behind that is as follows: first, to avoid AIDs colliding each application provider is assigned an RID by a registering entity.<\/p>\n

Then the application provider can optionally use the PIX to identify individual applications. The structure of a standard compliant AID is shown in figure 5.2. Figure 5.2: ISO\/IEC 7814-5 compliant AID CAT denotes registration category. It is a 4-bit field with all possible values listed in the ISO\/IEC 7816-5 standard. Two of those are worth mentioning here: A for international registration and D for national registration.<\/p>\n

In the case of international registration, the RID consists of a 4-bit registration category indicator, with A coded as 1010 and the identifier itself consisting of 9 BCD digits spanning 36 bits. The PIX that can optionally follow the RID can be anywhere between 0 to 11 bytes (in whole bytes).<\/p>\n

\n

Taylor & Francis Group 6000 Broken Sound Parkway NW, Suite 300 Boca Raton, FL 33487-2742 \u00a9 2019 by Taylor & Francis Group, LLC CRC Press is an imprint of Taylor & Francis Group, an Informa business No claim to original U.S. Government works Printed on acid-free paper International Standard Book Number-13: 978-0-3673-4284-5 (Hardback) This book contains information obtained from authentic and highly regarded sources. Reasonable efforts have been made to publish reliable data and information, but the author and publisher cannot assume responsibility for the validity of all materials or the consequences of their use.<\/p>\n

The authors and publishers have attempted to trace the copyright holders of all material reproduced in this publication and apologize to copyright holders if permission to publish in this form has not been obtained. If any copyright material has not been acknowledged please write and let us know so we may rectify in any future reprint. Except as permitted under U.S. Copyright Law, no part of this book may be reprinted, reproduced, transmitted, or utilized in any form by any electronic, mechanical, or other means, now known or hereafter invented, including photocopying, microfilming, and recording, or in any information storage or retrieval system, without written permission from the publishers.<\/p>\n

For permission to photocopy or use material electronically from this work, please access www.copyright.com (http:\/\/www.copyright.com\/) or contact the Copyright Clearance Center, Inc. (CCC), 222 Rosewood Drive, Danvers, MA 01923, 978-750-8400. CCC is a not-for-profit organization that provides licenses and registration for a variety of users. For organizations that have been granted a photocopy license by the CCC, a separate system of payment has been arranged. Trademark Notice: Product or corporate names may be trademarks or registered trademarks, and are used only for identification and explanation without intent to infringe.<\/p>\n

Visit the Taylor & Francis Web site at http:\/\/www.taylorandfrancis.com and the CRC Press Web site at http:\/\/www.crcpress.com 1kitap1.com\/en To my father.<\/p>\n<\/blockquote>\n

This is a short excerpt from the opening of “” by Unknown, quoted for review and introduction purposes. All rights belong to the copyright holders.<\/em><\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n