Home

Debit Card Interface User Manual

1. sss 2 17 Function ID 5 22 2 3 1 1 1 1 2 1 3 1 4 1 Preface Introduction This manual is designed to help acquaint you with the interface between Oracle FLEXCUBE and the other systems within your bank This manual provides you extensive explanations about the various maintenances required for the smooth exchange of data between Oracle FLEXCUBE and the applicable systems through the interface It also gives you an insight into the processes involved in the actual exchange of data Audience This manual is intended for the following User User Roles Role Function Back office clerk Input functions for contracts Back office managers officers Authorization functions Product Managers Product definition and authorization End of day operators Processing during end of day beginning of day Financial Controller Product Manag Generation of reports ers Documentation Accessibility For information about Oracle s commitment to accessibility visit the Oracle Accessibility Program website at http www oracle com pls topic lookup ctx acc amp id docacc Organization This manual is organized as follows About this Manual gives information on the intended audience It Chapter also lists the various chapters covered in this User Manual Debit Card Interface explains the process of capturing debit card Cha
2. 2 9 If Card Management System needs extra fields the same can be maintained as UDF s using the Fields screen Click Fields Button to invoke the Fields screen User Defined Fields Field Name System validates the following e if any card customer is open at customer closure level if any card customer is open that card customer needs to be closed before customer closure e if any card customer is closed during customer reopen if the customer is closed system will not allow the card customer to be reopened Maintaining Card Master Details The life cycle of the card is maintained using the Card Master Maintenance screen right from raising card request to the card expiry renewal You can invoke the Card Master Maintenance screen by typing STDCRDMSSTDCRDMSSTDCRDMS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button This is the master table which stores the card request and further life cycle details This screen is used for the following e create new card requests e amend the card status manually or through online upload e To query the Card to accounts Account to Cards linkages by Oracle FLEXCUBE e generate the hand off file new card requests e To generate the renewal file 20 ORACLE Card Master Detailed New Card Master Branch Code Request Reference Number
3. Customer No Account No Card products Card BIN Customer Card Status Name On Card Card Number Dispatch Status Owner ID Number Card Sequence Number Pin Mailed Status Additional Holder ID Card Application Date Last Status Updated Number Card Issued Date Last Operation ime Card Renewal Date anditiis Additional Holder ID Type Card Expiry Date Hold Bill Indicator Recovery Account Activation Date Delivery Channel For y Primary Card Card Additional Holder Issuer Delivery Channel For Pin Additional Holder Plastic Type DriCr indicator Relation Credit Card Limit Cr Primary Card No Renewal ATM POS Remarks ATM Limit Unit v POS Limit Unit X Renewal Unit hd ATM Count Limit POS Count Limit Renewal Cycle ATM Amount Limit POS Amount Limit Bill Cycle Remote ATM Count Limit Remote POS Limit Unit v Remote ATM Amount Remote POS Count Limit Remote POS Amount Limit Maker Date Time Mod No Checker Record Status Date Time Authorization Status Specify the following details Branch Code Branch code gets defaulted to current branch Card Product Specify the product code of the card Request Reference Number This is a system generated number This reference number is used while doing updates based on response from CMS Customer No Specify the customer number in case of request renewal Account No Specify the Customer Account Number It is
4. Specify the description of the Card type zn ORACLE 2 5 BIN Details Specify the BIN details here Card BIN Select the BIN for the card issued from the option list You can associate multiple BINs to the same card type Maintaining Debit Card Products You can maintain debit card product in the Debit Card Product Maintenance screen This screen links a given card type to a card product one to one You are not allowed to link multiple card types to same card products Card products are linked to uniquely identify the card nature that is requested You can invoke the Debit Card Product Maintenance screen by typing STDCPROD in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Debit Card Product Maintenance Card Product Description Card Type Card BIN Expiry Date Debit Credit Card Debit Card Credit Card GL Account GL Account Transaction code Excess Payment GL Excess Debit GL Acc Debit Transaction Code Excess Credit GL Acc Credit Transaction Code Card Agreement External Product Ref No Date Time Checker Date Time Mod No Record Status Authorization Status Specify the following details in this screen Card Product Specify the Product Code Description Specify the description of the specified Card product Card Type Specify the type of Card allowed for the card product Expiry Date Specify the date after which
5. the top right corner of the Application tool bar and clicking the adjoining arrow button This batch can be configured as either ad hoc run or EOD run It generates the Oracle FLEXCUBE Specific CMS Handoff Format 28 ORACLE 2 10 1 Hand Off Batch Click Run button in this screen to run the handoff batch File Format The format of the hand off file generated is broadly structured as given below Request 1 lt Customer record gt CRLF lt Account record gt CRLF Card record gt CRLF Request 2 lt Customer record gt CRLF lt Account record gt CRL Card record gt CRLF Seq Field Name Size Remarks Customer Record Source STTM_CUSTOMER 1 Bank code 10 DCTM_CARD_ISS_BIN BANK_INST ID 2 Branch code 3 Customer local branch 3 customer code 9 4 customer type 1 0 bank 1 individual 2 corporate 5 Last name FC size 6 First name FC size 7 Short name FC size 8 Sex 1 0 male 1 female 2 15 ORACLE Seq Field Name Size Remarks 9 Married 1 0 single 1 married 2 divorced 3 seperatd 10 Address 1 FC size 11 Address 2 FC size 12 Address 3 FC size 13 Address 4 FC size 14 City FC size 15 Pin Code FC size 16 work Phone FC size 17 Home Telephone FC size Account Record Source STTM_CUST_ACCOUNT 1 Bank code 10 DCTM_CARD_ISS_BIN BANK_INST ID 2 Branch cod
6. validated against the customer account marked with ATM Facility Card BIN Select the Card BIN from the option list Customer As part of specifying the details pertaining to customer you can specify the following Name on Card Customer name gets displayed as maintained in Card Customer Maintenance screen However you are allowed to modify it en ORACLE Owner ID Type Specify the type of ID produced For example PAN Passport DL etc Owner ID Number Specify the identification number of the applicant Additional Holder ID Type Specify the type of ID produced by additional holder For example PAN Passport DL etc Additional Holder ID Number Specify the Identification Number of the additional holder Recovery Account Specify the recovery account here Additional Holder Date of Birth Specify the date of birth of the additional holder from the adjoining calendar Additional Holder Relation Specify the relation of the additional holder with the card holder Card As part of specifying the card details you can specify the following Primary Card No In case of Secondary Cards system displays the Primary Card Number here Card Number It is generated by CMS when the mode is Request renewal However you are allowed to specify the card number Card Sequence Number Card Sequence Number is generated and displayed by the system It is the running number 1 2 3 Primary Card By default sy
7. ORACLE Debit Card Interface User Guide Oracle FLEXCUBE Universal Banking Release 12 0 3 0 0 Part No E53393 01 April 2014 Debit Card Interface User Guide April 2014 Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon East Mumbai Maharashtra 400 063 India Worldwide Inquiries Phone 91 22 6718 3000 Fax 91 22 6718 3001 www oracle com financialservices Copyright 2007 2014 Oracle and or its affiliates All rights reserved Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently
8. affiliates will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services Contents Preface onn ea eee eee 1 1 ie Fo GP net Ete c ec o ee M e 1 1 1 2 Auden acere ou eere e E cte ie oed es 1 1 1 3 Documentation Accessibility sese 1 1 TA OrgatillzatUOr eret ree einer ter D a e RR EES e eee 1 1 1 5 Abbreviations iere Ip e ERE D RD i Es 1 2 1 6 Glossary ot Cons anco a Ia means 1 2 T1 Related Doc ments onere tee en einsdem cedet 1 2 Debit Card Interface oco aoc eee eee 2 1 24 Arodu ana er eO Oba ie t teas 2 1 2 2 Process HOP Mu uuu 2 1 2 3 Maintairi rig Card BIN 2 2 24 Maintaining Card Type ennemi enne 2 5 2 5 Maintaining Debit Card Products eene 2 6 2 6 Maintaining Card Status Details emen 2 7 2 Maintaining Card Customer essen nennen enne 2 8 2 8 Maintaining Card ener enne enne 2 9 2 8 1 Viewing Cards Summary sse nennen nennen nns 2 9 2 9 Maintaining Card Master Details sse 2 10 2 10 Generating Card Handoff Files ener 2 14 2 10 1 File Format tanen ga nee Rena ado 2 15 2 10 2 Uploading Card Status Details
9. dangerous applications including applications that may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate failsafe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing This software or hardware and documentation may provide access to or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services Oracle Corporation and its
10. ded to bank typically by networks like VISA MasterCard or by ISO organization ATM and POS transaction count and amount limits are maintained for every BIN in this maintenance Card Type Maintenance Card Types should be created to uniquely identify the set of Issuer BINs maintained For example Visa might issue 433333 and 422222 under Classic type and 455555 and 466666 under Gold type etc Card Product Maintenance Card product maintenance is to link a given card type to a card product You are not able to link multiple card types to same card products Card products are linked in Debit Card Product Maintenance to uniquely identify the card nature that is requested Card Status Maintenance Card status has to be defined as card applied closed card issued activated and blocked Card Customers Maintenance Card customer should be maintained Card Accounts Maintenance This maintenance is required for creating the customer account who wishes to avail the card Card Requests Maintenance This is the master table which stores the card request and further life cycle details Process Flow The following flow diagram depicts the working of the Debit Card Interface 2 ORACLE NN Define Card Define Card Define Card Bins with Customers Status Limits Define Card YES Accounts Define Card Products a 14 TY Create Debit Card Request Maintenance Card Bin Product Limits C
11. e FC size Account branch 3 Customer code FC size 4 Account number FC size 5 Account currency FC size 6 Account currency FC size numeric 7 Account type 2 10 current 20 savings Card Record Source DCTM_CARD_MASTER 1 bank code 10 2 FC_reference_no This need to be used by CMS when sending card status change 3 Branch code FC size 4 customer code FC size 5 Account number FC size 6 Card Product code 4 DCTM_CARD_MASTER CARD_PRO DUCT 7 Primary secondary 1 0 primary 1 secondary card 8 Card status 1 1 request 9 PAN Not used 20 ORACLE You can define the required format for the handoff file through the Generic Interface module in case a different format is required 2 10 2 Uploading Card Status Details You can upload the new card details into Card Master Maintenance through Incoming Generic Interface module Similarly you can upload card status details or any amendments through Generic Interface module E ORACLE 3 Function ID Glossary D DCDBATCH 2 14 STDGARDYA 2 9 STDCPROD 2 6 2 11 SIDORDMS 2 10 LINK2 2 41 STDOUSTM 2 8 STDSTATM 2 7 STDTYMNT 2 5 STDBINMT 2 2 s ORACLE
12. ecify the following details pertaining to POS limit POS Limit Unit Select the unit of POS Limit count for transactions control from the drop down list This list displays the following values e Year e Month e Week e Day POS Count Limit Specify the number of POS transactions allowed for the unit defined for POS POS Amount Limit Specify the maximum permissible amount for the unit defined for POS e ORACLE Example Specify 1000 to indicate 1000 account currency per unit Remote POS Limit Unit Select the unit of POS Limit count for transactions control from the drop down list This list displays the following values e Year e Month e Week e Day Remote POS Count Limit Specify the number of transactions allowed from a remote POS Remote POS Amount Limit Specify maximum permissible amount for the unit defined for remote POS Example Specify 1000 to indicate 1000 account currency per unit 2 4 Maintaining Card Type You can maintain the card type in the Card Type Maintenance screen You can invoke the Card Type Maintenance screen by typing STDTYMNT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Card Type Card Type Description BIN Details card BIN Authorized By Date Time Date Time Specify the following details in this screen Card Type Specify the type of the card Description
13. he card master screen If Card Management System needs extra fields the same can be maintained as UDFs using this screen Click the UDF button to maintain User Defined Fields for the CMS System validates the following e if any card customer is open at customer closure level if any card customer is open that card customer needs to be closed before customer closure is ORACLE e if any card customer is closed during customer reopen if the customer is closed system will not allow the card customer to be reopened 2 8 Maintaining Card Accounts You can maintain the customer accounts which can be linked to cards in the Card Accounts Detail screen Also you can view the various cards attached to the same account using this screen You can invoke the Card Accounts Detail screen by typing STDCARDA in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Card Account Detail New Branch Code _ Customer Id az Customer Account Number Debit Credit Indicator Debit Credit Specify the following details in this screen Branch Code Specify the branch code Customer ID Select the Customer ID from the option list Customer Account Number Select the customer account number from the option list 2 8 1 Viewing Cards Summary In query mode you can click Cards button to see the summary of the cards related to the account ae ORACLE
14. ld be different Renewal As part of the details pertaining to renewal you can specify the following Remarks Specify comments if any Renewal Unit Renewal unit gets defaulted here Renewal Cycle Renewal cycle gets defaulted here 2 13 ORACLE Bill Cycle ATM The following details are displayed ATM Limit Unit ATM Limit Unit gets defaulted from BIN ATM Count Limit ATM Count Unit gets defaulted from BIN AMT Amount Limit AMT Amount Unit gets defaulted from BIN Remote ATM Limit Unit Remote transactions allowed through ATM unit gets defaulted Remote ATM Count Limit Remote transactions unit allowed through ATM gets defaulted Remote ATM Amount Limit Remote transactions allowed amount through ATM gets defaulted POS The following details are displayed POS Limit Unit POS Limit Unit gets defaulted from BIN POS Count Limit POS Count Unit gets defaulted from BIN POS Amount Limit POS Amount Unit gets defaulted from BIN Remote POS Limit Unit Remote transactions allowed through POS unit gets defaulted Remote POS Count Limit Remote transactions unit allowed through POS gets defaulted Remote POS Amount Limit Remote transactions allowed amount through POS gets defaulted 2 10 Generating Card Handoff Files You can generate handoff files in Card Info handoff file format using the Card Handoff Batch screen You can invoke the Card Handoff Batch screen by typing DCDBATCH in the field at
15. pter 2 transactions originating from Automatic Teller Machines ATM and POS terminals attached to different branches of your bank Function ID Glossary has alphabetical listing of Function Screen ID s Chapter 3 used in the module with page references for quick navigation t1 ORACLE 1 5 1 6 1 7 Abbreviations Abbreviation Description System Unless and otherwise specified it shall always refer to Oracle FLEX CUBE system EOD End Of Day CMS Card Management System BIN Bank Identification Number Glossary of Icons This User Manual may refer to all or some of the following icons Icons Function X Exit Add row Delete row EE Option List Related Documents e Procedures User Manual Ve ORACLE 2 1 2 2 2 Debit Card Interface Introduction Oracle FLEXCUBE facilitates the processing of debit card transactions originating from Automatic Teller Machines ATM and POS terminals attached to different branches of your bank You will be allowed to capture different types of debit cards in Oracle FLEXCUBE The cards are linked to individual customer accounts You need to do the following maintenance in Oracle FLEXCUBE for the debit card interface to work Card BIN Maintenance Card BIN maintenance should be created for every issuer product that the bank wishes to provide to customers These BINs would be provi
16. status will be Card applied Later you can change this to any status depending upon the need The card status can be of the following e R Specify R to indicate the status as Requested e A Specify to indicate the status as Activated e C Specify C to indicate the status as Closed e Card Issued when the card is sent with PIN and physical 27 ORACLE 2 7 e Specify B to indicate the status as Blocked These codes are factory shipped codes and can be modified at the time of implementation based on the Card Management System used by your bank Description Specify a description for the status Maintaining Card Customer You can maintain the card customer in the Card Customer Maintenance screen You can invoke the Card Customer Maintenance screen by typing STDCUSTM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Card Customer Maintenance Customer Details Branch Code Customer Id Customer Name Specify the following details in this screen Branch Code The branch code gets defaulted here Customer ID Select the customer ID from the adjoining option list The option list displays all the customers maintained in the system Customer Name The customer name gets displayed on selecting the customer id However you are allowed to change the customer name Based on this the customer name will appear in t
17. stem considers the first Debit Card issued for an account as the primary card and hence checks this box You are not allowed to change the same System unchecks this box on subsequent card issued for the same customer account Card Application Date Specify the date of card application Card Issued Date Specify the date of issue of the card Card Renewal Date The date of renewal of the card gets defaulted from the BIN level Card Expiry Date Specify the expiry date of the card 2e ORACLE Card Activation Date Specify the date of activation of the card Issuer Specify the name of the issuer Plastic Type Specify the card type here Credit Card Limit Specify the credit limit for the customer Status As part of the specifying the satus you can specify the following Card Dispatch Status Select the Dispatch Status from the drop down list to indicate whether the card has been dispatched or not Pin Mailed Status Select the PIN Mailed Status from the drop down list to indicate whether PIN has been mailed to the cardholder or not Card Status Specify the status of the card e g Active Blocked etc Last Status Change Date Specify the date of last status change Last Operation Specify the last operation done on card Delivery Channel for Card Specify the delivery channel for the card dispatch Delivery Channel for PIN Specify the delivery channel for the PIN Note Delivery channel for Card and PIN shou
18. t Renewal Cycle Specify the default renewal unit value of the cards issued under the card BIN Example To indicate that the card should be renewed after every 2 Years when the Default Renewal Unit is Yearly you have to specify the Default Renewal Cycle as 2 ATM Limit Specify the following details pertaining to ATM limit ATM Limit Unit Select the unit of ATM Limit count for transactions control from the drop down list This list displays the following values oe ORACLE e Year e Month e Week e Day ATM Count Limit Specify the number of ATM transactions allowed for the unit defined for ATM ATM Amount Limit Specify the maximum permissible amount for the unit defined for ATM Example Specify 1000 to indicate 1000 account currency per unit Remote ATM Limit Unit Select the unit of ATM Limit count for transactions control for transactions done from ATMs outside the bank network from the adjoining drop down list This list displays the following values e Year e Month e Week e Day Remote transaction means transactions done outside the bank network For example an ATM transaction done in ICICI ATM using CITIBANK debit card Remote ATM Count Limit Specify the number of ATM transactions allowed for the unit defined for remote ATM Remote ATM Amount Limit Specify maximum permissible amount for the unit defined for remote ATM Example Specify 1000 to indicate 1000 account currency per unit POS Limit Sp
19. the card product cannot be used Debit Credit Card Select the type of the card 28 ORACLE 2 6 GL Account Specify the GL account for the card from the adjoining option list The option list displays all the GL accounts maintained in the system Choose the appropriate one Offset Account Specify the offset account for the card from the adjoining option list The option list displays all the offset accounts maintained in the system Choose the appropriate one Transaction Code Specify the transaction code for the card from the adjoining option list The option list displays all the transaction codes maintained in the system Choose the appropriate one Other Transaction Code Specify the other transaction code for the card from the adjoining option list The option list displays all the transaction codes maintained in the system Choose the appropriate one Maintaining Card Status Details You can maintain the card status in line with the Card Management System in the Card Status screen You can invoke the Card Status screen by typing STDSTATM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Card Status New 753 Enter Query Card Status Description Input By Authorized By Date Time Date Time Specify the following details in this screen Card Status Specify the status of the card Initially when the request for the card is initiated the card
20. ustomer Account Status gt h Card Status Query Card Production Handoff File V O Card Status Update 2 3 Maintaining Card BIN You have to create Card BIN maintenance for every issuer product that the bank wishes to provide to customers You can maintain the details of the card BIN in the Card BIN Maintenance screen You can invoke the Card BIN Maintenance screen by typing STDBINMT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 22 ORACLE Card BIN Maintenance Card BIN Description Bank Institution Id ATM Limit ATM Limit Unit ATM Count Limit ATM Amount Limit Remote ATM Limit Unit Remote ATM Count Limit Remote ATM Amount Limit Default Renewal Unit Default Renewal Cycle POS Limit POS Limit Unit POS Count Limit POS Amount Limit Remote POS Limit Unit Remote POS Count Limit Remote POS Amount Limit Specify the following details in this screen Card BIN Specify the Bank Identification Number BIN Description Specify the description of the BIN Bank Institution Id Specify the bank institution code Default Renewal Unit Select the default renewal unit of the cards issued under the card BIN from the drop down list This list displays the following values e Year e Month e Week e Day Defaul

Debit Card Interface User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents