BASE24-eps Transaction Processing

TCS

BASE24-eps Transaction Processing

BASE24-eps

Saikat

4/17/2014

BASE24-eps Transaction Processing

Contents

Preface........................................................................................................................8BASE24-eps Transaction Processing..........................................................................12BASE24-eps Transaction Originators.....................................................................13BASE24-eps Transaction Authorizers.....................................................................14Issuers and Acquirers.............................................................................................15Hosts......................................................................................................................16Authorization Environments....................................................................................17Transactions and Transaction Messages................................................................19Card-based Processors..........................................................................................20Prefixes...........................................................................................................................22What is a Prefix?....................................................................................................23Local (On-Us) and Non-Local (Not-on-Us) Prefixes...............................................24BASE24-eps Prefix Processing..............................................................................25Setting Up On-Us Prefixes.....................................................................................26Setting Up Not-On-Us Prefixes...............................................................................27Payment Instruments, Cards, and Accounts..............................................................28Payment Instruments..............................................................................................29Instrument Types...........................................................................................29Cards......................................................................................................................30Configuring Cards.........................................................................................30How Cards are Identified in BASE24-eps......................................................30Card Information Maintained by BASE24-eps...............................................31Primary and Secondary Cards......................................................................35Refreshing Card Information.........................................................................36Administrative Cards..............................................................................................37Setting Up Administrative Cards for Use with Point-of Sale Terminals..........38Setting Up Administrative Cards for Use with ATMs......................................39Accounts.................................................................................................................40Associating Account with Cards....................................................................40Identifying Accounts to BASE24-eps.............................................................41Account Information Maintained by BASE24-eps in the Card Data Source...42Account Information Maintained by BASE24-eps in the Positive Balance Data Source.44Refreshing Account Information....................................................................45Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 3ContentsAccount Balance Information.........................................................................46Deriving Current Account Balances Using the Account Balance Information.47Refresh Scheduling as it Relates to Account Balances.................................49Account Activity......................................................................................................50Field Masking of Card and Account Information.....................................................51Transactions Allowed....................................................................................................52Acquirer Transactions Allowed Profiles...................................................................53Setting Up an Acquirer Transactions Allowed Profile.....................................53Assigning Acquirer Transactions Allowed Profiles to Acquirer Endpoints......54How Acquirer Transactions Allowed Profiles are Used in Processing...........55Issuer Transactions Allowed Profiles......................................................................56Setting up an Issuer Transactions Allowed Profile.........................................56Assigning Issuer Transactions Allowed Profiles to Endpoints........................57How Issuer Transactions Allowed Profiles are Used in Processing...............58Transaction Routing......................................................................................................60Things to Think About Before Setting Up Transaction Routing...............................62Destination Routing Profiles...................................................................................66Destination Routing Profile Name and Description.............................................67Destination Routing Profile Transaction Table.....................................................68Destination Routing Profile General Information.................................................71Destination Routing Profile Destination Matrix....................................................74Typical Destination Routing Profiles.......................................................................83Transaction Routing Worksheets............................................................................85Tying Destination Routing Profiles to Prefixes........................................................87Source Routing Profiles..........................................................................................88Source Routing Profile Name and Description....................................................89Source Routing Profile Not-on-Us Prefix Selection Tables..................................90Using the table to Recognize a Not-on-us Prefix for Processing ..................90Not-on-Us Prefix Search Methods.................................................................90Selection Table Example...............................................................................93Not-On-Us Processing Parameters...............................................................94Tying Source Routing Profiles to Acquirers............................................................95Prefix Routing Algorithms.......................................................................................96Configure Prefix Routing Algorithms.............................................................96Standard Prefix Routing Algorithms..............................................................97Routing Codes........................................................................................................994 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29ContentsEnabling and Disabling the Use of Routing Codes at the Prefix Level..........99Defining Business Relationships and Routing Codes for Your System.......100File Update Routing....................................................................................................103Defining File Update Routing for Your System......................................................109File Update Transactions Resulting from Authorization Changes to the Card Data Source.111Authorization, Prescreening, and Impacting.............................................................113BASE24-eps Authorization Methods for On-Us Cards.........................................116How Scripts are Identified....................................................................................118Tying Script Sets to Routing.................................................................................121Configuring Script Sets to Use as Routing Destinations......................................122Monitoring Script Set Performance.......................................................................125Enabling and Disabling Authorization Scripts.......................................................130More About Scripts...............................................................................................131Sequential Routing...............................................................................................133Default Authorization............................................................................................139Approval Codes....................................................................................................140BASE24-eps Transaction Limits and Usages............................................................141Limit Profiles - Where Limits are Defined.............................................................143Defining a Single Limit..........................................................................................144Assigning Limit Profiles to Cards, Accounts, and Prefixes...................................149Setting Limits for Cards and Accounts.................................................................150Tracking Transaction Usage..................................................................................152Viewing and Deleting Active Usages....................................................................157What Happens to Expired Usages.......................................................................159Cash Advance Minimums and Increments for an Account...................................160Preauthorization Holds...............................................................................................161What are Preauthorization Transactions?.............................................................162Authorization Scripts Scripting Preauthorization Hold Processing..................167Active and Expired Preauthorization Holds..........................................................168What Information is Stored For Each Preauthorization Hold................................170How Preauthorization Holds Affect Processing....................................................172Additional Optional Processing (Interac)..............................................................175Adding, Deleting, and Modifying Preauthorization Holds from Your Authorization Scripts.176Adding, Viewing, Modifying, and Deleting Preauthorization Holds from the ACI Desktop.178Match and Hold Processing.................................................................................180How Match and Hold Works with the Batch Authorization Process.............180Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 5ContentsWhat It Takes to Identify Holds for Deletion..........................................................182Check Processing.......................................................................................................183MICR Data............................................................................................................186How MICR Data is Used in BASE24-eps Check Processing...............................188Manipulating MICR Data......................................................................................189Preapproved and Predeclined Checks.................................................................192Check Limits/Usages............................................................................................196Stop Payment Processing..........................................................................................197Active and Expired Stop Payments......................................................................198Adding, Modifying, and Removing Stop Payments...............................................201How Stop Payments Affect Processing................................................................204Card and Prefix Blocking............................................................................................206Card and Prefix Block Processing........................................................................208Adding, Viewing, Updating, and Deleting Card Blocks.........................................210Adding, Viewing, Updating, and Deleting Prefix Blocks........................................212German Routing and Authorization (Regional)........................................................214German-Specific Transaction Data.......................................................................219Configuring German Routing and Authorization...................................................221BLZ Mapping........................................................................................................224BASE24-eps Transaction Flows.................................................................................225How BASE24-eps Components Interact Within the Integrated Server Process....226BASE24-eps Transaction Flow Summaries..........................................................230Internal Authorization Request/Response, Card-Initiated....................................231Internal Authorization Request/Response With Advice........................................233Internal Authorization Request/Response/Reversal.............................................235Internal Authorization Request/Response, Sequential Authorization to External Destinations.238External Authorization Request............................................................................241External Authorization Response.........................................................................243External Authorization, Transaction Not Allowed by the Acquirer.........................245External Authorization, Transaction Not Allowed by the Issuer............................246External Authorization, Prescreen (Successful)...................................................248External Authorization, Prescreen (Not Successful)............................................250External Authorization, Response With Impacting...............................................252External Authorization, Request Timeout/Stand-in...............................................254External Authorization, Station Marked Down/Stand-in........................................256External Authorization, Late (Approved) Response.............................................2586 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29ContentsExternal Authorization, Late (Denied) Response.................................................260Primary Transaction Identifiers..................................................................................261Message Type Identifiers (MTIs)...........................................................................262Message Type Identifier (MTI) Structure.....................................................262Message Type Indicators (MTIs) Supported by BASE24-eps.....................266Function Codes....................................................................................................278Function Codes Supported by BASE24-eps...............................................278Message Reason Codes......................................................................................284Message Reason Codes Supported by BASE24-eps.................................284Point of Service Data............................................................................................289Point of Service Data Supported by BASE24-eps.......................................289Processing Codes................................................................................................296Transaction Codes Supported by BASE24-eps...........................................296From and To Account Types Supported by BASE24-eps............................300Action Codes........................................................................................................301Action Codes Supported by BASE24-eps...................................................301

PrefaceThe BASE24-eps Transaction Processing User Guide describes the various features andprocessing concepts associated with BASE24-eps transaction processing. It is intendedto provide a general understanding of BASE24-eps transaction processing and to assistin configuring and implementing various BASE24-eps transaction processing features.AudienceThis user guide is intended for readers seeking an understanding of BASE24-eps transactionprocessing and more specifically for those BASE24-eps business users who handle theconfiguration of transaction processing business data through the ACI Desktop (e.g., settingup prefixes and routing).PrerequisitesThis user guide assumes a familarity with the ACI desktop user interface. Windows andtabs are referenced by name throughout the manual, and menu paths are provided foraccessing windows through the ACI desktop; however, screen shots, information aboutthe ACI desktop, and procedures for basic window functions (e.g., adding, deleting, updatingand viewing records) are generally left to the BASE24-eps online help and these manuals: The ACI DesktopUser Interface Manual describes how to use the ACI desktop userinterface. The BASE24-eps Windows Reference User Guide describes each of the BASE24-epswindows and tabs available through the ACI desktop user interface. Screen shots ofeach window and tab are provided along with information for each field on the windowor tab.Additionally, much of setting up BASE24-eps transaction processing involves writing andconfiguring your own authorization scripts for processing transactions.This manual toucheson different areas where scripts fit into transaction processing, but it does not describehow scripts are designed or written. Because authorization scripts control a significantamount of processing, an understanding of the scripts you plan to use is recommended.8 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29PrefaceMentions are made throughout this manual to the following BASE24-eps manuals whichprovide additional information about scripting. The BASE24-eps Scripting Manual provides detailed information on the scriptingcapability of BASE24-eps, the Script Repository window, the Script Editor, scriptsyntax,scriptable objects, exported operators, and writing standards. The BASE24-eps Sample Fundamental Authorization Scripts Delivery Document providesinformation about delivered sample scripts that are designed for authorization processing,the naming conventions of these scripts, implementation, and scripted authorizationmethods. This manual is delivered with the BASE24-eps install.Additional DocumentationThe following manuals contain supplemental information related to transaction processing: The BASE24-eps Transaction Security Manual describes how to configure and implementBASE24-eps transaction security, including PIN encryption, PIN verification, messageauthentication, message data encryption, card verification, dynamic card verification,EMV card authentication, secure Internet validation, and dynamic key management.The manual also describes how hardware security modules are integrated intoBASE24-eps processing and the duties they can assume as a part of that processing. The BASE24-eps Multiple Currency Manual describes the processing and configurationof the BASE24-eps Multiple Currency add-on module. The BASE24-eps EMV Support Guide provides information about configuringBASE24-eps to process EMV (Europay, MasterCard, and Visa) cards and describesthe processing of BASE24-eps EMV transactions. The BASE24-eps Journal User Guide provides an overview of transaction journals andtheir use in a BASE24-eps system. The BASE24-eps Environment Management User Guide describes environment attributesand how to configure these attributes. The BASE24-eps ISO 8583:1993 Host External Message Manual provides detailedinformation on the layout of the external message used by ISO 8583:1993 hosts.SoftwareThis user guide documents standard processing for the current BASE24-eps version asof its publication date. Software that is not current and custom software modifications(CSMs) may result in processing that differs from the material presented in this manual.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 9PrefaceManual SummaryThe following is a summary of the contents of this user guide: BASE24-eps Transaction Processing on page 12 - provides a set of introductorytopics defining basic terms and concepts related to transaction processing. Prefixes on page 22 - Defines and describes prefixes and how they are used inBASE24-eps transaction processing. Payment Instruments, Cards, and Accounts on page 28 - Defines paymentinstruments, cards, and accounts and describes how they are supported by BASE24-eps.Information is included about how account activity and account balances are handled. Transactions Allowed on page 52 - Defines Transactions allowed, which is a basictransaction screening function that BASE24-eps provides as a part of routing andauthorization, and describes how to configure it for acquirers and issuer endpoints. Transaction Routing on page 60 - Describes transaction routing and how it isconfigured within BASE24-eps. File Update Routing on page 103 - Describes file update routing and how it is configuredwithin BASE24-eps. File update routing is a specialized form of routing--carried out bythe File Update Router component--that enables the routing of file updates and fileupdate transactions in the BASE24-eps system. Authorization, Prescreening, and Impacting on page 113 - Describes the basics ofauthorization, prescreening, and impacting, all of which are carried out by scripts. Basicinformation is provided about how scripts are used and identified for processing.Information is also provided about sequential routing, which is a script-based form ofrouting, and about default authorization. BASE24-eps Transaction Limits and Usages on page 141 - Describes transactionlimits and usages and how they are supported by BASE24-eps. Information is providedabout how limits are set and how usages are tracked. Preauthorization Holds on page 161 - Describes preauthorization holds and how theyare used within BASE24-eps. Information is included about preauthorization transactionsand match and hold process*sing. The latter provides the capability to introduce batchrecords of settled transactions into the BASE24-eps system for the purpose of removingtheir corresponding holds. Check Processing on page 183 - Describes how check processing is supported byBASE24-eps. Information is included about MICR data handling by BASE24-eps andhow preapproved and predeclined checks can be defined to BASE24-eps. Stop Payment Processing on page 197 - Describes how stop payment processing issupported by BASE24-eps. Card and Prefix Blocking on page 206 - Describes how card and prefix blocks aresupported by BASE24-eps.10 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Preface German Routing and Authorization (Regional) on page 214 - Describes the Germanregional routing and authorization support provided by BASE24-eps for German cardsprocessed through German endpoints. BASE24-eps Transaction Flows on page 225 - Provides diagrams and step-by-stepprocessing descriptions of how BASE24-eps handles various types of transactions. Primary Transaction Identifiers on page 261 - Provides reference information forseveral transaction identifiers that are of primary importance to processing: MessageType Identifiers (MTIs), function codes, message reason codes, point of service data,processing codes, and action codes.Publication IdentificationTwo entries appear at the bottom of each page to uniquely identify this BASE24-epspublication: the publication date (for example, Sep-2009 for September 2009) and thepublication number (for example, ES-CS000-29 for the BASE24-eps Transaction ProcessingUser Guide).Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 11PrefaceBASE24-eps Transaction ProcessingBASE24-eps provides the means by which a transaction originator can request and receiveauthorization for an action on a customer card or account from a transaction authorizer.The role of BASE24-eps in transaction processing includes the following: Routing transactions from the transaction originator to the appropriate authorizer. Participating in or carrying out authorization on behalf of the institutions for which itprocesses. Journaling all transactions for later processing and settlement.BASE24-eps can accept transactions from a variety of sources. Likewise, it can involve anumber of different authorizers in its processing.12 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29BASE24-eps Transaction ProcessingBASE24-eps Transaction OriginatorsBASE24-eps can accept transactions for authorization from several different types oforiginators.ATM ChannelsAutomated teller machines (ATMs) can be directly attached to BASE24-eps, in which casetransactions are originated by customers or service personnel at the ATM. Communicationsbetween the ATM and BASE24-eps are controlled by ATM Channel Manager components.Point-of-Sale Device ChannelsPoint-of-sale (POS) devices can be directly attached to BASE24-eps, in which casetransactions are originated by customers, service personnel, or retail clerks at the point ofsale. Communications between the POS device and BASE24-eps are controlled byMerchant Channel Manager components.HostsHost computers can be set up to control ATM or POS device networks and forwardtransactions to BASE24-eps. In this case, communications between these acquirer hosts and BASE24-eps are controlled by an ISO Host Interface component.InterchangesInterchanges can act as switches to forward transactions to BASE24-eps for authorization.In this case, communications between the interchange acquiring the transaction andBASE24-eps are controlled by Interchange Interface components.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 13BASE24-eps Transaction ProcessingBASE24-eps Transaction AuthorizersBASE24-eps can route transactions to several types of authorizers.BASE24-epsBASE24-eps can be set up to authorize transactions in those situations where cardholderfiles are maintained on the BASE24-eps system.HostsHosts can be set up to authorize transactions in situations where cardholder files aremaintained on the host computer. In this case, BASE24-eps can pre-screen the transactionsbefore sending them to the host and can also be set up to stand in and authorizetransactions for a host in situations where communications between BASE24-eps and thehost system are down.InterchangesInterchanges can be used to forward transactions to other networks for authorization.14 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29BASE24-eps Transaction ProcessingIssuers and AcquirersTransaction originators and authorizers are generally defined by the EFT industry termsacquirer and issuer. An acquirer, or transaction acquirer, is the party that originates atransaction. An issuer, or card issuer, is an institution that issues cards or owns accountsthat can be used in EFT transactions.Whether an entity is defined as an issuer or an acquirer depends on the perspective fromwhich the transaction is viewed. Intermediary networks and processors that receivetransactions from a transaction originator and authorize them or forward them elsewherefor authorization can be acting on behalf of both the acquirer and the issuer.From the acquirer point of view, intermediary networks are acting on behalf of the issuer.For example, a cardholder initiates a transaction at an ATM belonging to institution A. Inthis case, institution A is the transaction acquirer. Institution A sends the transaction to anintermediary network that, in turn, sends the transaction to institution B for authorization.Institution B owns the cardholders account and issued the cardholder the card; therefore,institution B is the true issuer. However, from the point of view of institution A, theintermediary network is performing as an issuer on behalf of institution B since institutionA had to send the transaction to the intermediary network before it could reach its authorizingdestination.From the issuer point of view, intermediary networks are acting on behalf of the acquirer.As in the above example, institution B views the intermediary network as an acquirer sincethe intermediary network is the entity that sent it a transaction to be authorized.BASE24-eps can process transactions on behalf of an issuer or an acquirer, dependingon where a transaction originates and who is to authorize the transaction. For example,when BASE24-eps sends a transaction to a back-end host for authorization, BASE24-epsrepresents the acquirer in the message exchange and the back-end host represents theissuer. On the other hand, when a transaction is sent to BASE24-eps for authorization,the sending host represents the acquirer and BASE24-eps represents the issuer.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 15BASE24-eps Transaction ProcessingHostsHosts can play a prominent role in the transaction processing performed by BASE24-eps.A host is an external mainframe computer system with which BASE24-eps interacts, eitheronline or by batched tape, to authorize transactions and/or update cardholder records.Although the term host generally refers to an actual computer or system of computers, theterm also refers to the institution or organization responsible for the host computer systemand its processing. For example, in the phrase, the host can opt to receive advicemessages, the term host actually refers to the BASE24-eps-defined institution in controlof the host computer, rather than the computer itself.Hosts are assigned identification numbers and are defined to BASE24-eps in the HostInterface Configuration data source (HISO93_INTERFACE). Each host must have a recordin the HISO93_INTERFACE to be recognized by BASE24-eps.The HISO93_INTERFACEcontains options that allow you to specify individual processing parameters for each host.16 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29BASE24-eps Transaction ProcessingAuthorization EnvironmentsAuthorization environments define the general level of participation BASE24-eps is to havein the authorization of transactions.You need to be aware of the level of participation youwant BASE24-eps to have when planning your routing and authorization.Online AuthorizationIn an Online Authorization environment, a host performs all authorization processing (i.e.,the host system is the authorizer). If BASE24-eps cannot communicate with the host (i.e.,is unable to send transactions for processing), it declines all transaction requests in whichthe host is the destination.Though BASE24-eps is not the authorizer, it can be configured to prescreen transactionsin an online authorization environment. In this case, if a transaction does not meet theprescreening requirements, the transaction is declined, and BASE24-eps sends a denyresponse to the originator and notifies the host. If the transaction does meet prescreenrequirements, the transaction is then forwarded to the host for authorization.Therefore, in this environment, authorization scripts would be limited to prescreeningfunctions.Offline AuthorizationIn Offline Authorization environments, all authorization processing is performed byBASE24-eps; authorization requests are not forwarded to the host. As a result, scripts willperform more extensive processing and data checking than those scripts used in an onlineauthorization environment.In offline authorization, BASE24-eps maintains account and payment-instrument data andtransaction journal files. As a result, data file information must be exchanged and updatedperiodically between BASE24-eps and the host.In this environment, your authorization scripts would need to handle all aspects oftransaction authorization.Online/Offline AuthorizationIn a combined Online/Offline Authorization environment, BASE24-eps can be configuredto prescreen transactions for a host as in the online authorization environment. However,in this environment, BASE24-eps also stands in for the host and authorizes transactionswhen communication with the host is down. The transactions BASE24-eps authorizes arestored in a store-and-forward (SAF) file for forwarding to the host when communication isrestored.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 17BASE24-eps Transaction ProcessingData file information is exchanged and updated periodically as in the offline authorizationenvironment.In this environment, your authorization scripts would typically be divided betweenprescreening functions to be performed prior to sending a transaction to the host, impactingfunctions to update the BASE24-eps data base once a transaction is returned from thehost, and authorization functions to be performed should the host be offline. The latterfunctions/scripts might impose tighter restrictions given that the host is unavailable.18 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29BASE24-eps Transaction ProcessingTransactions and Transaction MessagesFrom a processing standpoint, transactions are actually carried out through one or moretransaction messages. Messages are the means by which information is exchangedbetween parties, typically in a request/response interaction where one party requests anaction and the other either says yes or no or offers an alternative. In some cases, theremay be additional messages. In some cases, one party may have taken an action andmay simply be notifying the other party. In all cases, however, the messages used arebased on a standard and are exchanged based on the protocols established by the standard.Each message carries pertinent transaction information and is built with uniquecharacteristics that allow transaction processors to identify the intended purpose of themessage and the specific actions or services to be performed related to the message.From a BASE24-eps perspective, each transaction message can be thought of as a discreetrequest for some type of service related to a transaction.BASE24-eps can receive messages from a variety of endpoints or channels to which it isconnected. Endpoints can include ATM or POS devices, hosts, and interchanges.BASE24-eps can also initiate messages as part of its processing. A transaction messagecan represent a request for an authorization or another type of action, a response (andpossible authorization) to a previous request, or a notification that a particular action hastaken place. In any case, the receipt of a message by BASE24-eps from a connectedendpoint, or the creation of a specific transaction message by BASE24-eps, initiates aprescribed set of actions or servicesactions or services as defined by the BASE24-epssystem owner.Primary Identifiers: Message Type Identifier (MTI) and ProcessingCodeAlthough there are many transaction message characteristics that can and do influencethe services provided by BASE24-eps, all messages processed by BASE24-eps aredifferentiated by two primary identifiers: a Message Type Identifier (MTI) and a processingcode. Regardless of the endpoint originating a message, all transaction messages aredefined within BASE24-eps by a set of recognized MTIs andin almost allcasesprocessing codes (network management messages do not carry processing codes).Transactions to and from various endpoints (entities outside the BASE24-eps system)must be translated between the business rules, protocols, and processing requirementsof the respective endpoints and the internally normalized processing values by whichBASE24-eps recognizes and processes the transactions. Message translation is onefunction of the various BASE24-eps channel interfaces on behalf of ATM/POS devices,hosts, or interchanges.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 19BASE24-eps Transaction ProcessingCard-based ProcessorsThere are three broad categories into which BASE24-eps card-based processors typicallyfall: terminal acquirers, financial switches, and card issuers. Each has its own routing andauthorization requirements. A single BASE24-eps institution could fall into a single categoryor any combination of the three.Terminal AcquirersTerminal acquirers are processors that use the BASE24-eps system to drive ATM or POSterminal networks. These processors typically maintain an extensive terminal databaseand route transactions through interfaces to external interchanges. Terminal acquirerstypically have little or no stand-in authorization capabilities and maintain interfaces tomultiple interchanges.Financial SwitchesProcessors who use the BASE24-eps system to route acquired transactions to card issuersact as a financial switch. These processors do not drive terminals and are mainly concernedwith routing transactions acquired from an interchange to a card issuer. Financial switchescan have substantial stand-in authorization capabilities.Card IssuersCard issuers are processors that use the BASE24-eps system to authorize transactions.These processors typically maintain a substantial card database and connect to a host.Card issuers may or may not drive terminals.Their main concern is authorizing transactionsacquired from an interchange. Because the account of record is maintained on a host, thehost is the primary authorization destination. However, card issuers typically have substantialstand-in authorization capabilities when the host link is unavailable.Non-Card-Based ProcessorsTypically, cards or card numbers are used to initiate financial transactions, and in theinterest of clarity, this is the type of processing described throughout the BASE24-epsproduct documentation unless specifically noted to the contrary.Important to note, BASE24-eps is adaptable to other types of instruments. For example,where card-based acquirers use a card prefix obtained from the primary account number(PAN) of a card to determine the issuer, other types of processors might use customizedcomponents to determine the issuer/authorizer of a transaction. For instance, a mobilephone acquiring component might use an entirely different meansperhaps invoking a20 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29BASE24-eps Transaction Processingcustom component to determine the issuer based on the phone number used to initiatethe transaction.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 21BASE24-eps Transaction ProcessingPrefixesMuch of BASE24-eps routing and authorization processing is controlled at the prefix level,meaning that processing can be set up differently for different prefixes. The topics heredescribe prefixes and how they are used in BASE24-eps processing.22 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29PrefixesWhat is a Prefix?A prefix is a numberthe first portion of a larger number, such as the primary accountnumber (PAN) for a credit or debit card account. In BASE24-eps, prefixes are used inconjunction with the overall length of the PAN to identify the issuer of a card account.In the following example, the indicated card number would be recognized as a match onthe values defined for the prefix and length.Card Number Prefix Length5011 1234 1234 1234 5011 16 positionA card issuer can be assigned a single prefix or several. However, with the BASE24-epssystem, each prefix must be unique to a card issuer. That is, no two card issuers can beassigned the same prefix.This uniqueness enables BASE24-eps to use the prefix to identifytransactions that involve local issuers (institutions) defined to the system.Also, because of their fundamental uniqueness within BASE24-eps, a significant portionof authorization processing is defined at the prefix level. That is, BASE24-eps institutionscan specify different processing parameters for each of their prefixes.Note: Cards are a typical form of financial instrument used in transactions. The term cardis used here to mean instrument.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 23PrefixesLocal (On-Us) and Non-Local (Not-on-Us)PrefixesAs part of BASE24-eps transaction processing, prefixes are defined as local (on-us) ornon-local (not-on-us).Note: The BASE24-eps definitions of on-us and not-on-us are different from the strictindustry-standard definition of the terms, where an on-us transaction means the acquirerand issuer institutions are the same, and a not-on-us transaction means the acquirer andissuer institutions are different.Local (On-Us) PrefixesCard issuers can be local to the BASE24-eps system, which means that the issuer isdefined as a BASE24-eps institution and each prefix for which the institution issues cardsis defined as an on-us prefix to the system as well.Transactions acquired by BASE24-epson cards with on-us prefixes are referred to as on-us transactions and are typicallyauthorized by BASE24-eps or a back-end host.On-us prefixes are defined to BASE24-eps using the On-Us Prefix Configuration window(Configure > Prefix > On-Us). The information from this window is used to populate thePrefix data source (Prefix).Non-Local (Not-on-Us)Card issuers can be non-local to the BASE24-eps system, meaning their prefixes are notdefined as on-us prefixes. Prefixes associated with these non-local card issuers, callednot-on-us prefixes, must still be defined to BASE24-eps in order to be be recognized andprocessed.Not-on-us prefixes are defined to BASE24-eps using the System Prefix Configurationwindow (Configure > Prefix > Not-On-Us > System Prefix). The information from thiswindow is used to populate the System Prefix data source (System_Prefix).Transactions acquired by BASE24-eps on cards with these not-on-us prefixes are referredto as not-on-us transactions and are typically sent to an interchange for processing.24 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29PrefixesBASE24-eps Prefix ProcessingThe initial identification of a transaction acquired by BASE24-eps is based on the prefix ofthe transaction PAN in conjunction with the PAN length.Prefixes for acquired transactions fall into the following general categories:On-Us Prefixes Not-On-Us PrefixesPrefixes Recognized by Unrecognized PrefixesAlgorithmInterchange PrefixesA prefix that cannot beidentified by BASE24-eps byany means available to it.A prefix that is notspecifically defined toBASE24-eps, but can beidentified based on analgorithm match.A prefix that is specificallydefined to the BASE24-epsin an Interchange prefix datasource.A prefix that is specificallydefined to the BASE24-epsin the Prefix data source.When the Acquirer Interface component invokes the Prefix component to determine thetransaction issuer, it first determines whether the issuer is a known (recognized) issuer bysearching for a match on the prefix in the Prefix external memory table (Prefix_OLTP).If a match is found, the component invokes the Transaction component to add to thetransaction the Issuer Route Profile and Route Type TDEs, as well as several other TDEsnot specifically used in routing and returns control to the Prefix component.If the Prefix component does not find a match in the Prefix external memory table, it attemptsto find one using the methods defined in the System Prefix external memory table(System_Prefix_OLTP).These methods include searching Interchange Prefix data sources,testing the transaction prefix against an algorithm, or using a default value. The Prefixcomponent uses the methods in the order in which they are defined in the System Prefixexternal memory table.When the Prefix component finds a match on the transaction prefix, it invokes theTransaction component to add to the transaction the Issuer Route Profile and Route TypeTDEs and returns control to the Acquirer Interface component.If a match is not found in either the Prefix or System Prefix external memory tables, thetransaction is denied.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 25PrefixesSetting Up On-Us PrefixesLocal issuers (institutions) must define each on-us prefix to be processed by BASE24-epsusing the On-Us Prefix Configuration window (Configure > Prefix > On-Us). Each prefixmust be explicitly defined, along with the BASE24-eps processing associated with theprefix.Much of BASE24-eps routing and authorization processing is controlled at the prefix level,meaning that processing can be set up differently for different prefixes.The information from the On-Us Prefix Configuration window is used to populate the Prefixdata source, from which the Prefix external memory table is built.Identifying a PrefixThe key used to identify a prefix is actually the prefix itself and length of the PAN in whichthe prefix can be found. Thus, when you define a prefix you are actually defining it incombination with the PAN length.Note: An institution must be defined to which an on-us prefix belongs.Defining On-Us Prefix Routing ParametersThere are only a few routing parameters configured for a prefix, which makes sense becauseat the point the prefix is identified, the issuer is known.On-Us Prefix Configuration Window Setting (for Routing)Tab Field DescriptionThe route type value to be used for the transaction. Values are asfollows:Processing Information Route TypeAcquirer and Issuer Means that a business relationship shouldbe taken into consideration, and transactions will be evaluated for aroute code.Issuer Only Means that a business relationship does not exist forthis prefix and transactions will not be evaluated for a route code.This value is moved to the Route TypeTDE.Refer to Enabling and Disabling the Use of Routing Codes at thePrefix Level on page 99 for more information about how this field isused.The instrument type to be assumed for the transaction.Issuer Information Instrument TypeThis value is moved to the Instrument Type TDE.The name of the Destination Routing Profile to use for the transaction.Destination RoutingProfileThis value is moved to the Issuer Routing Profile TDE.26 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29PrefixesSetting Up Not-On-Us PrefixesThe controls for recognizing and processing transactions with not-on us prefixes are definedthrough the Source Routing Profile, which are assigned to the various acquiring endpoints.Refer to Source Routing Profiles on page 88 for information about the Source RoutingProfile.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 27PrefixesPayment Instruments, Cards, andAccountsThe topics here describe payment instruments, cards, and accounts and how they areused in BASE24-eps processing.28 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsPayment InstrumentsA payment instrument is a device by which consumers can initiate payment transactions.Cards are the typical payment instrument used in the payments industry, and in the interestof clarity, cards are the instrument type assumed throughout the BASE24-eps productdocumentation unless specifically noted to the contrary. Important to note, however,BASE24-eps is adaptable to other types of instruments as well.Instrument TypesInstrument type is a one- or two-character user-defined identifier (code) used throughoutBASE24-eps to identify types of payment instruments. Each instrument defined to thesystem must have a corresponding instrument type associated with it.In a card-based payment system, the instrument type represents the branding of the card,such as Visa Debit, Visa Credit, American Express, and MasterCard, among others.Defining Your Instrument TypesInstrument types are defined for the BASE24-eps system in the Instrument Type(Instrument_Type) data source and can be viewed and managed using the InstrumentType Configuration window (Configure > Instrument Type). Once defined, instrumenttypes can be selected as valid types for the various instruments (i.e., cards) you want todefine.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 29Payment Instruments, Cards, and AccountsCardsCardsthat is plastic debit or credit cardsare a type of payment instrument. They serveas evidence of one or more accounts and act as a mechanism for accessing the accountsusing the many electronic funds transfer (EFT) channels available.Configuring CardsCards are configured on the Card Management window (Customer Management > Card)or the Administrative Card Configuration windows (Configure > Administrative Card).Associating Cards and PrefixesAny cards to be processed by BASE24-eps must have their prefixes defined to the systemas on-us (known) prefixes. For information on on-us prefixes, refer to Setting Up On-UsPrefixes on page 26 for information about setting up on-us prefixes.Prefix definitions specify processing parameters and associated limits for a prefix. Theseparameters and limits can be used in authorization or prescreening processing for cardsthat belong to the prefixif the parameters and limits have not been defined morespecifically for the card.Associating Accounts with CardsBASE24-eps supports up to 80 accounts associated with a single card. Refer to Accountson page 40 for more information about accounts and associating them with cards.How Cards are Identified in BASE24-epsCards are identified to BASE24-eps using several identifiers that are important tounderstand.Primary Account Numbers (PANs)Cards are identified by a primary account number (PAN) that is embossed on the front ofthe card and encoded on the magnetic strip.The PAN is a composite number that contains a prefix consisting of the bank identificationnumber (BIN) of the card issuer followed by a possible regional identifier, an individualaccount identifier that includes part of the account number, and a check digit or code thatverifies the authenticity of the embossed account number or the PAN on the track. Thelength of a PAN varies by card type but is typically 1619 digits.30 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsYou can view the PAN of a card defined to BASE24-eps in the Card Number field on theCard Management window (Customer Management > Card).Member NumbersThe member number is a card sequence number used to identify an individual memberwhen several members have the same card number. This enables you to issue differentplastics with the same PAN, but different member numbers, and define each with its ownunique card record in BASE24-eps. If a card has only one member, the correspondingmember number would be 000, and there would only be one BASE24-eps recordrepresenting the card. If there were multiple members (e.g., 001, 002, 003), each couldhave his or her own plastic and each plastic would have its own BASE24-eps record.The member number associated with a card is identified in the Member Number field ofthe Card Management window (Customer Management > Card).Institution (Card Issuer)The institution that issued a card is identified by its institution ID. All cards defined to theBASE24-eps system must have a corresponding issuer institution defined to thesystemprior to adding the cards.The card issuing institution is identified for the card in the Institution ID field of the CardManagement window (Customer Management > Card).Institution records are accessed and updated using the Institution Configuration window(Configure > Institution).Card Information Maintained by BASE24-epsCard information is maintained in the Card, Card Account, and Card Account Multibytedata sources.Customer IDThe customer ID of the Card record identifies the name of the customer or business towhich the card was issued.You can view or change the customer ID associated with a card on the General tab of theCard Management window.Note: Depending on your environment, a multibyte version of the customer ID can beentered. If present, the multibyte value is carried in the Card Account Multibyte data source.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 31Payment Instruments, Cards, and AccountsDepository TypeThe depository type specifies the preferred type of deposit for the card used by thecustomer: Standard or Commercial.Your scripts can use this value to set the Depository Type TDE. The Depository Type TDEcan then be used by those device handler components that support the capability to specifyto terminals the depository to open for deposit transactions.You can view or change the depository type associated with a card on the General tab ofthe Card Management window.Card TypesCard types are a specific form of instrument type. They are a one- or two-characteruser-defined identifier (code) used throughout BASE24-eps to identify the type of card.Each card defined to the system must have a corresponding card type associated with it.Refer to Payment Instruments on page 29 for information about how available instrumenttypes are defined in the system.You can view or change the card type associated with a card on the General tab of theCard Management window.Note: The INSTRM_TYP Card object script operator returns the one or two-charactercode representing the instrument type of the card used in a transaction.PIN Information/PIN Verification Value (PVV)PIN verification during transaction processing can require the use of a PIN verificationvalue (PVV), which is combined with the customer-entered PIN and other data to allow forverification.BASE24-eps enables you to configureat the prefix levelwhether the PVV will beacquired from the card itself (in the track data), or from the Card record, or not at all. Thisprefix setting is specified in the PIN Location fields on the On-Us Prefix Configurationwindow. If the prefix setting indicates the PVV is to be acquired from the Card record, thePVV needs to be placed in the Card record for those cards associated with the prefix.The PVV is not displayed; it is carried in the Card data source, but you can change it fromthe General tab of the Card Management window. The PIN verification value is maskedon the window and must be entered twice to ensure that it is entered correctly.For information about PIN verification, refer to the BASE24-eps Transaction SecurityManual.32 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsLast PIN Change DateThe date and time of the last PIN and PIN verification value change for the card is displayedin the Last PIN Change field on the General tab of the Card Management window. Thisdate is updated in the following situations: A new PVV is entered on the Card Management window. The new PVV is created as the result of an online PIN change transaction. A new PVV is created as the result of the cardholder choosing a PIN on the first onlinetransaction for the card. The PVV is set by a partial-file refresh or file update transaction. The PVV change date is set explicitly by a partial-file refresh or file update transaction.Check ProcessingBASE24-eps check processing enables you to specify at the prefix and card level whetherto evaluate check-based transactions against your total cash advance and total withdrawallimits. If defined at the card level, these settings are on the General tab of the CardManagement window. For information about these check settings, refer to CheckLimits/Usages on page 196.Card StatusCard status indicates whether a card is open, closed, lost, stolen, or pending activation.This information is critical to authorization processing in that the status of a card is a majorfactor in determining processing allowed on the card. For example, transactions wouldtypically be denied for lost, stolen, and closed status cards, however, transactions on cardsthat are lost or stolen might also provide the opportunity to retain the card on behalf of thecard issuer.Status values are user-defined for your system in the CommonCodesValues.propertiesfile. Values of 0015 are intended for Open statuses; values 16-99 are for other values.The default values here correspond to values in the standard authorization scripts deliveredwith the BASE24-eps application. These values can and should be changed for specificenvironments.Value Description015 Open60 Denied - Lost70 Denied - Stolen80 Denied - ClosedSep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 33Payment Instruments, Cards, and AccountsYou can view or change the card status associated with a primary or secondary card onthe Status tab of the Card Management window.Note: The system tracks the date and time the status last changed for primary andsecondary cards defined in the BASE24-eps system. This information is displayed in theStatus Last Change Date fields on the Status tab of the Card Management window.Effective DateIf you want a card to become usable as of a specific date, you can set an effective datefor the card. The effective date is intended to be the first date BASE24-eps will authorizetransactions on a card and can be used by your authorization scripts for that purpose(currently, the sample authorization scripts do not include this processing).You can view or change the effective date associated with a primary or secondary cardon the Status tab of the Card Management window.Placing a check mark in the Use Effective Date field on that tab enables the associateddate field and can also be used by your authorization scripts to control whether or not touse the effective date field in processing.Note: The system tracks the date and time the effective date last changed for primaryand secondary cards defined in the BASE24-eps system. This information is displayed inthe Effective Last Change Date fields on the Status tab of the Card Management window.Expiration DateIf you want a card to expire as of a specific date, you can set an expiration date for thecard.The expiration date is the last date BASE24-eps will authorize transactions on a card.You can view or change the expiration date associated with a primary or secondary cardon the Status tab of the Card Management window.Placing a check mark in the Use Expiration Date field on that tab enables the associateddate field. The date placed in that date field is the last date the card will be usable.Note: The system tracks the date and time the expiration date last changed for primaryand secondary cards defined in the BASE24-eps system. This information is displayed inthe Expiration Last Change Date fields on the Status tab of the Card Management window.Card LimitsThe limits profile and the limit overrides to be used by a card are specified on the Limitstab of the Card Management window. For information about these limit profiles andoverrides, refer to Assigning Limit Profiles to Cards, Accounts, and Prefixes on page 149.Note that card usages are maintained in their own data source and are not part of the cardrecord.34 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsCardholder Address/Address Verification SettingsThe cardholder address associated with a card consists of two lines of cardholder addressinformation and the postal code for the cardholder address. This information can be enteredfor informational purposes or it can be used in address verification service processing (AVSprocessing).AVS processing gives merchants the capability to use the cardholders address informationto confirm that a customer is entitled to use an account in situations where it is not possibleto physically examine the card and the customers signature.You can view or change the address information on the Address tab of the CardManagement window.If you want to use the cardholder address information for address verification, place acheck mark in the Use Address Verification field on the Address tab of the CardManagement window. Leaving this field blank means the cardholder address informationis being used for informational purposes only and will not be used for address verification.Note: Depending on your environment, multibyte versions of the two customer addresslines and postal codes can be entered. If present, these multibyte values are carried in theCard Account Multibyte data source.Note: The CRD_AVS_FLG Card object script operator is used to check the Use AddressVerification field. If the flag is enabled, the ADDR_VRFY Card object script operator canbe used to invoke address verification processing.AccountsBASE24-eps supports up to 80 accounts associated with a single card. These are set upon the Accounts tab of the Card Management window. Refer to Accounts on page 40 formore information about accounts and associating them with cards.Primary and Secondary CardsWhen institutions reissue cards, there can be a period of time when two physical cardsare in circulation with the same card number (and member number), but different expirationdates.BASE24-eps enables you to configure the following information separately for primary andsecondary cards in the same Card record. Card Status Effective Date Expiration DateSep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 35Payment Instruments, Cards, and AccountsIn processing, the primary and secondary cards are differentiated by their expiration date(i.e., the expiration date on the card can be compared to the expiration dates for the primaryand secondary cards in the Card record).You can view or change the primary and secondary card information on the Status tab ofthe Card Management window.Script OperatorsThe following Card object script operators are used in support of primary and secondarycards:SCND_STATSCND_STAT_SETPRI_STATPRI_STAT_SETIS_PRI_EFFIS_PRI_EXPIS_SCND_EFF PRI_STAT_SET_NOTIFY SCND_STAT_SET_NOTIFYIS_SCND_EXPThese operators can be used to determine whether the card used to initiate a transactionis the primary (original) or secondary (reissued) card by comparing the expiration date ofthe card to the primary and secondary card expiration dates in the Card data source. Theoperators can also be used to activate the secondary card when the first transaction usingthe card is received and/or the operators can be used to promote the secondary card tobecome the primary card. Refer to the BASE24-eps Scripting Manual for more informationabout these and other script operators.Refreshing Card InformationCard information is carried in the Card (Card), Card Account(Card_Account), and CardAccount Multibyte (Card_Account_Multibyte) data sources. These data sources can berefreshed using full-file or partial-file refreshes.For information about refreshes, refer to the BASE24-eps File Refresh User Guide.The Last Time the Card Information Was RefreshedAt the bottom of the General tab on the Card Management Window is information aboutthe last time (Refresh Timestamp) the card record was refreshed from a host and theidentifier of the batch (Refresh ID) used to refresh the record.If timestamp and ID information is not provided, it indicates that the card record has notbeen updated by a refresh.Note: Card information in the Card (Card), Card Account(Card_Account), and Card AccountMultibyte (Card_Account_Multibyte) data sources can also be updated using file updatetransactions. This type of update does not update the refresh date information.36 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsAdministrative CardsAdministrative cards are a special type of card identified within BASE24-eps for differentforms of administrative channel processing.The processing and configuration requirements of an administrative card can vary dependingon the type of channel in which they are used: ATM terminal-owning institutions issue administrative cards for servicing and settlingterminals. Point-of-sale terminal owners typically issue administrative cards at the merchant levelfor settlement purposes.Administrative cards enable terminal-owning institutions or merchants to initiateadministrative transactions at an ATM or point-of-sale terminal, respectively. Cardholdertransactions, such as a return or an adjustment, can be configured to require the input ofan administrative card as well as the cardholders card.For transactions acquired in the BASE24-eps system from a channel device (e.g., ATMsor point-of-sale terminals) using an administrative card, transactions are authorized inscripts using the same Card script operators in scripts that are used to accessnon-administrative card information.Transactions AllowedThe Admin Card Required field on the Acquirer Transactions Allowed Profile Configurationwindow (Configure > Transactions Allowed > Acquirer Transactions Allowed) specifieswhether an administrative card is required to enter a transaction.Prefix ConsiderationsLarge ATM or point-of-sale network owners may want to issue administrative cards usinga card prefix reserved for just administrative cards while smaller ATM or point-of-salenetwork owners may want to designate a range of card numbers from within their cardholderbase to be used as administrative cards. In either case, the card prefix for administrativecards must be configured as an on-us prefix.If an entire card prefix is configured to be used exclusively for ATM administrative cards,set the Instrument Type field on the Issuer Information tab of the On-Us Prefix Configurationwindow to AD (Administrative).Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 37Payment Instruments, Cards, and AccountsSetting Up Administrative Cards for Use with Point-ofSale TerminalsAdministrative cards for point-of-sale terminals are configured and accessed on theAdministrative Card Configuration window (Configure > Administrative Card). Data fromthis window is stored in the Administrative Card data source (Admin_Card).Before entering an administrative card record, you must configure the on-us card prefix tobe used to recognize the administrative card number and the merchant with which theadministrative card is associated.Identification InformationThe following information identifies the administrative card.Field DescriptionCard Number The number of the administrative card.User Name The user name associated with the administrative card.The merchant ID associated with this administrative card. The administrative card canonly be used at POS terminals associated with this merchant.Merchant IDPIN InformationThe following information identifies the PIN information associated with the administrativecard.Field DescriptionThis is not displayed, but can be changed on the Administrative Card Configurationwindow. To change it, the value must be entered twice.PVVPVV Key Index Specify the PVV Key Index to be used with the PVV.Usage InformationThe following information identifies the usage information associated with the administrativecard.Field DescriptionLast Used The date the card was last used.The number of bad PIN tries attempted for the administrative card since the bad PIN trieswas last reset.Bad PIN TriesThe date the bad PIN tries were last reset. Typically, the entry of a correct PIN causesthe bad PIN tries to reset to zero.Last Reset38 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsAllowed TransactionsAdministrative cards can only be used to initiate those transaction types that are specificallyenabled for the card.The check boxes in the Allowed Transaction Types section of the Administrative CardConfiguration window indicate the transactions the administrative cardholder is allowed toperform with the card. A check mark in the box next to the transaction type means theadministrative cardholder is allowed to perform that transaction; otherwise, the transactionis not allowed. The following is a list of transaction types that can be enabled for anadministrative card.Allowed Transaction TypesAdministrative Shift Close 95 (Administrative Subtotal)(94)Administrative Day Close(93)Administrative Batch Close(92)30 (Available Funds Inquiry 31 (Balance Inquiry) 38 (Card Verification Inquiry) 03 (Check Guarantee)04 (Check Verification) 22 (Credit Adjustment) 02 (Debit Adjustment) 00 (Purchase)01 (Withdrawal/Cash 20 (Return) A0 (Activation)Advance)09 (Purchase with CashBack)5C (Bulk Authorization) 2A (Funds Disbursement) 9U (Offline Phone Top Up) 0A (Phone Top Up)Setting Up Administrative Cards for Use with ATMsAdministrative cards for ATM terminals are configured and accessed on the CardManagement window and are stored in the Card data source (Card). They are similar tocustomer cardsthe major difference is that the Card Type field on the General tab of theCard Management window must be set to a value of AD - Administrative. Also, a usagewould typically be configured for the administrative card to accumulate bad PIN tries onthe Usages Management window.Before entering an administrative card record, you must configure the on-us card prefix tobe used to recognize the administrative card number.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 39Payment Instruments, Cards, and AccountsAccountsAccounts, in the context of the BASE24-eps configuration, typically refer to the accountstied to a card rather than to the card itself. Accounts basically represent the underlyingcard-issuer institutional accounts to which a card has access, such as the cardholderschecking, savings, and credit accounts.Associating Account with CardsThe association, or tying, of accounts to cards within BASE24-eps is very flexible. A cardcan have single account tied to it, it can have up to 80 different accounts tied to it of varyingtypes, or it can have no accounts tied to it at all.Accounts are set up on the Accounts tab of the Card Management window. Account balanceinformation is accessed using the Positive Balance Management window.The reason for associating accounts with cards is that while transactions are initiated usingcards, transactions also typically involve or affect different types of accounts (e.g., withdrawalfrom savings, a purchase on a credit account, or a transfer from savings to checking).By associating one or more accounts with cards, your authorization scripts can involvespecific account information in authorizing transactions initiated with the card.The followingare typical purposes for which account information is used.Verifying Cardholders Have Access to an Appropriate AccountThe presence of accounts can enable your authorization scripts to determine whether acardholder has access to the type of account(s) needed for a particular transaction. Everyaccount defined to BASE24-eps has a type and status associated with it. Thus, if atransaction is attempted on a card that does not have access to an account of the requiredtype and status, the transaction can be denied. For example, on an attempted withdrawalfrom savings, authorization scripts can check for the presence of an open savings accountassociated with the card and deny the transaction if one is not found.Enabling Cardholders to Access and Select From Multiple AccountsAssociating multiple accounts with a card can enable a card to transact business ondifferentand sometimes many differentaccounts. A straightforward example might besetting up a checking and credit account for the card to be used for debit and credittransactions. A more involved example might be used in processing environments wherethe transaction-originating devices support multiple account selectionalso know as OpenAccount Relationships (AOR). In these cases, BASE24-eps can be configured to returnall of a cardholders defined accounts to the transaction-originating device to allow thecardholder to choose the account to be used for the transaction.40 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsThe latter approach might be useful, if for example, a cardholder was set up to make certaintypes of purchases for a number of clients. In this case, each client might establish his orher own account and each of those accounts would be associated with the card. Then, fortransactions on the cardassuming the originating device supports itthe accounts wouldbe passed back to allow the cardholder to choose the account for making the purchase.Verifying Cardholders Have Sufficient Funds Available on TheirAccountsBeyond simply associating accounts with the card, BASE24-eps also supports the capabilityof maintaining balance and usage information for each of these accountsas well as otheraccount-level activity information. This is supported through the Positive Balance datasource, which enables authorization processing to take balance information intoconsideration when evaluating a transaction for approval. In this case, once the accountis chosen for a transaction, the authorization scripts can take additional stepsusing thePositive Balance data source and account balance usagesto determine whether sufficientfunds are available to allow the transaction.Identifying Accounts to BASE24-epsAccounts are identified to BASE24-eps using several identifiers that are important tounderstand. These identifiers are used in both the Card record and the Positive Balancerecords to identify an account.Institution IDThe institution ID is the identifier of the institution that owns the account. This institutionID must match the institution ID of the card with which the account is associated.Account NumberThe account number is the primary identifier for the account. The length of an accountnumber varies but is typically 1116 digits.You can view the account numbers of the accounts associated with a card in the AccountNumber field on the Accounts tab of the the Card Management window (CustomerManagement > Card).Account TypesThe account type is a code used to identify the type of account represented by the accountnumber.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 41Payment Instruments, Cards, and AccountsIf the same account number is used to access different types of accounts, the positivebalance data for each type of account is configured in a separate Positive_Balance record.If an account number has only one type of account or if only one positive balance recordis to be used as the default for an account number with several associated types ofaccounts, set the account type to Default Account (00).Note: The account type affects which fields are displayed on the Balances tab as discussedbelow.The following table shows which account types are considered debit and credit.Debit-Type Accounts Credit-Type Accounts30 = Credit38 = Line of Credit00 = Default/None10 = Savings11 = Savings - Money Market 9B = Installment Loan12 = Savings - Certificate of Deposit 9C = Mortgage Loan20 = Checking21 = Checking - Money Market39 = Corporate Card40 = Universal Account50 = Investment Account58 = CD60 = Stored Value - Reloadable67 = Stored Value - Disposable9M = OtherNote: The DFLT_ACCT_TYP Card script operator can be used access the account typeduring transaction processing.Account Information Maintained by BASE24-eps in theCard Data SourceThe information maintained for an account in the Card data source is minimal. Additionalinformation relating to an account is carried in the Positive Balance data source.Note: This account information can be refreshed using a Card refresh.Account StatusThe account status is a value assigned to each account to be able to determine certaincharacteristics of the account.42 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsAccount status values are Open or Closed. An account must have an open account statusto be used in processing.The status change date is the date and time on which the accountstatus was last changed.Status values are user-defined for your system in the CommonCodesValues.propertiesfile. Values of 0015 are intended for Open statuses; values 16-99 are for other values.The default values here correspond to values in the standard authorization scripts deliveredwith the BASE24-eps application. These values can and should be changed for specificenvironments.Status Description015 Open90 ClosedNote: Changes to the account status on the Card data source do not affect the accountstatus in the Positive Balance data source and vice versa.Note: If you create new status values for your institution, it is important that you alsoevaluate your script logic to ensure that those values are interpreted correctly.Note: The system tracks the date and time the status last changed. This information isdisplayed in the Status Last Change Date fields on the Status tab of the Card Managementwindow (Customer Management > Card).Account DescriptionYour authorization scripts can be set up to use a default account type for a card. Forexample, if you want all POS transactions for a cardholder to use a default account ofchecking, you would set the default account type to checking.Note: Depending on your environment, multibyte versions of the account descriptions canbe entered. If present, these multibyte values are carried in the Card Account Multibytedata source.Account Type DefaultYour authorization scripts can be set up to use a default account type for a card. Forexample, if you want all POS transactions for a cardholder to use a default account ofchecking, you would set the default account type to checking.Basically, the default account type is used if there is no account type supplied in an incomingmessage. Having an account type is important because it used in authorization (e.g.different limits/usages are typically used for credit and debit accounts).You can view or change the Account Type Default on the Accounts tab of the CardManagement window.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 43Payment Instruments, Cards, and AccountsAccount Information Maintained by BASE24-eps in thePositive Balance Data SourceThe BASE24-eps system maintains account balance data and other information in thePositive Balance data source (Positive_Balance) for each account belonging to a cardholderwhose card issuer uses the Positive Balance Authorization method.Account Currency CodeEach account has associated with it the currency code denoting the currency in which thevarious balances and amount information are displayed.You can view or change the currency code on the General tab of the Positive BalanceManagement window.Script Information: To access currency code information in scripts, use the CRNCY_CDEPBAL object script operator. Refer to the BASE24-eps Scripting Manual for more informationabout the PBAL object.Account StatusThe account status is a value assigned to each account to be able to determine certaincharacteristics of the account.Account status values are Open or Closed. An account must have an open account statusto be used in processing.The status change date is the date and time on which the accountstatus was last changed.Status values are user-defined for your system in the CommonCodesValues.propertiesfile. Values of 0015 are intended for Open statuses; values 16-99 are for other values.The default values here correspond to values in the standard authorization scripts deliveredwith the BASE24-eps application. These values can and should be changed for specificenvironments.Status Description015 Open90 ClosedYou can view or change the account status on the Status tab of the Positive BalanceManagement window.Note: If you create new status values for your institution, it is important that you alsoevaluate your script logic to ensure that those new values are interpreted correctly.Note: Changes to the account status on the Card data source do not change affect theaccount status in the Positive Balance data source and vice versa.44 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsNote: The system tracks the date and time the status last changed. This information isdisplayed in the Status Last Change Date fields on the Status tab of the Positive BalanceManagement window (Customer Management > Positive Balance).BalancesRefer to Account Balance Information on page 46.LimitsThe limits profile and the limit overrides to be used by an account are specified on theLimits tab of the Positive Balance Management window. For information about these limitprofiles and overrides, refer to Assigning Limit Profiles to Cards, Accounts, and Prefixeson page 149. Note that balance usages are maintained in their own data source and arenot part of the positive balance record.ActivityRefer to Account Activity on page 50.Refreshing Account InformationAccount balance records are carried in the Positive Balance (Positive_Balance) datasource. This data source can be refreshed using full-file or partial-file refreshes.For information about refreshes, refer to the BASE24-eps File Refresh User Guide.The Last Time the Positive Balance Information Was RefreshedAt the bottom of the General tab on the Positive Balance Management Window is informationabout the last time (Refresh Timestamp) the account record was refreshed from a hostand the identifier of the batch (Refresh ID) used to refresh the record.If timestamp and ID information is not provided, it indicates that the account record hasnot been updated by a refresh.Note: The Positive Balance data source can also be updated using file update transactions.This type of update does not update the refresh date information.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 45Payment Instruments, Cards, and AccountsAccount Balance InformationBASE24-eps maintains basic account balance information in the Positive Balance datasource. The balance information differs based on whether the account type is considereda debit or credit account.Refer to Identifying Accounts to BASE24-eps on page 41 for a listing of available debitand credit account types.You can view balance information for an account on the Balances tab of the PositiveBalance Management window (Customer Management > Positive Balance).Debit Account Balance InformationThe following balance information is either maintained, or derived from information, in thePositive Balance data source for debit accounts.Debit Account Balance InformationAvailable Balance Start of Day The available balance on the account at the start of the indicated date.Date The business date whose available balance information is presented.The derived current available balance on the account. This balance isnot stored in the Positive Balance data source; it is computed using theCurrentstart of day balance plus or minus any active usages since the start ofthe business day specified in the Date field.Ledger Balance Start of Day The ledger balance on the account at the start of the indicated date.Date The business date whose ledger balance information is presented.The derived current ledger balance on the account. This balance is notstored in the Positive Balance data source; it is computed using the startCurrentof day balance plus or minus any active usages since the start of thebusiness day specified in the Date field.Credit Account Balance InformationThe following balance information is either maintained, or derived from information, in thePositive Balance data source for credit accounts.Credit Account Balance InformationAvailable Credit Start of Day The available credit on the account at the start of the indicated date.Date The business date whose credit balance information is presented.The derived current available credit on the account. This balance is notstored in the Positive Balance data source; it is computed using the startCurrentof day balance plus or minus any active usages since the start of thebusiness day specified in the Date field.Credit Limit The credit limit on the account.46 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsDeriving Current Account Balances Using the AccountBalance InformationCurrent account balances are not maintained in the Positive Balance data source. Ratherthey are freshly calculated whenever they are needed for processing or display. Currentbalances are based on start of day balanceswhich are maintained in the Positive Balancedata sourceplus or minus any applicable active usages.Start of day balances and their corresponding dates are static data in the online transactionpath and are not updated during transaction processing. As such, the Positive Balancedata source is not undergoing updates as transaction processing affects balances. If acurrent balance is needed for transaction processing, applicable active usages are retrievedand applied to the start-of-day balance to derive the current balance.The start of day balance and data can be provided by refresh or file update or set usingthe ACI desktop.Example of Deriving a Current BalanceThere are three usage names that are system-defined specifically for the purpose of trackingbalance changes. Their formats are as follows: AVAIL_yyyymmdd For available balances of debit accounts LEDG_yyyymmdd For ledger balances of debit accounts AVAILCR_yyyymmdd For available credit of credit accountsThe following is a sample list of active usages on a debit account based on a set oftransaction processed on the account. In this case, the processors authorization scriptsare set up to create available and ledger balance usages for debit accounts. For informationon active versus expired usages, refer to Tracking Transaction Usage on page 152.Active Usages# Transaction Name Amount Name Amount1 Purchase AVAIL_20090305 -$500 LEDG_20090305 -$5002 Purchase AVAIL_20090305 -$50 LEDG_20090305 -$503 Purchase AVAIL_20090306 -$20 LEDG_20090306 -$204 Deposit AVAIL_20090306 $200 LEDG_20090306 $8005 Purchase AVAIL_20090307 -$40 LEDG_20090307 -$406 Purchase AVAIL_20090307 -$60 LEDG_20090307 -$607 Withdrawal AVAIL_20090308 -$100 LEDG_20090308 -$1008 Purchase AVAIL_20090308 -$10 LEDG_20090308 -$109 Purchase AVAIL_20090308 -$300 LEDG_20090308 -$300Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 47Payment Instruments, Cards, and AccountsNote: Transaction #4 is a deposit, and this case, the authorization scripts are set up toadd the full amount of the $800 deposit to the ledger balance but only a percentage of thedeposit to the available balance ($200 in this case).Based on the active usages in the table above, current balances would be computed asfollows using the indicated start of day information.Debit Account Balance InformationAvailable Balance Start of Day $4,000Date March 6, 2009Current $4,000 Start of Day-$20 Usages 39(Usages 1-2, although active,are not applied because theirdate is prior to March 6.)$200-$40-$60-$100-$10-$300$3,670 Derived BalanceLedger Balance Start of Day $5,000Date March 6, 2009Current $5,000 Start of Day-$20 Usages 39(Usages 1-2, although active,are not applied because theirdate is prior to March 6.)$800-$40-$60-$100-$10-$300$5,270 Derived BalanceBecause current balances are derived by applying active usages that were created withdates on or after the date of the start-of-day balance, it is assumed that the host-providedstart-of-day balances would always include any transaction activity that occurred prior tothe date. Thus, in this example, usages 1 and 2 represent transactions that would havealready been processed and included in the host-provided start-of-day balances.48 | Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29Payment Instruments, Cards, and AccountsRefresh Scheduling as it Relates to Account BalancesBecause current balances are derived by applying active usages that were created withdates on or after the date of the start-of-day balance, it is assumed that the host-providedstart-of-day balances always include any transaction activity that occurred prior to the date.Also, your usage retention needs to be long enough to keep usages active until they canbe processed and reflected in the host-provided start-of-day balances. For instance, if yourretention period was set to one day and you refreshed your start-of-day balances everythree days, your usages would expire two days before being included in your start-of-daybalancesresulting in inaccurate current balances. Generally, it is better to have usageretention periods longer than your refresh cycle rather than shorter. Thus, you need toevaluate your refresh cycle against your usage retention.Sep-2009, Release 1.0 Version 09.2 Publication Number: ES-CS000-29 | 49Payment Instruments, Cards, and AccountsAccount ActivityThe Positive Balance data source contains the account activity information.The account activity information is described in the following table. All of this informationcan be accessed by your authorization scripts, and some of it can be updated. The tableidentifies those fields that can be updated by your authorization scripts.All of it can be refreshed or updated by file update, and all of it can be viewed for an accountfrom the Activity tab of the Positive Balance Management window (Customer Management> Positive Balance).Updated byScript?Group Field DescriptionDeposit Last Deposit Amount The amount of the last deposit on the account. YesLast Deposit Date The date of the last deposit on the account. YesThe minimum amount for a payment from