21.01.2014 Views

FI Card Data Architecture Document Ver 1.5.4.pdf - IDRBT

FI Card Data Architecture Document Ver 1.5.4.pdf - IDRBT

FI Card Data Architecture Document Ver 1.5.4.pdf - IDRBT

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Customer <strong>Card</strong> <strong>Data</strong> <strong>Architecture</strong><br />

<strong>Ver</strong>sion 1.5.4 Specification<br />

31<br />

• <strong>Data</strong> element 6 Asset Code (Income recognition and asset<br />

classification). RBI has described the following four:<br />

o Standard<br />

o Sub-standard<br />

o Doubtful<br />

o Loss<br />

Banks may adopt their own numbering scheme based on their<br />

guidelines and handle it appropriately in the terminal<br />

application. The following framework is recommended.<br />

• 0 – Regular<br />

• 1 – Temporarily irregular (30 to 60 days)<br />

• 2 - Temporarily irregular (60 to 90 days)<br />

• 3 - RFU<br />

• 4 – Irregular more than 90 days.<br />

• 5 – Doubtful up to one year<br />

• 6 – Doubtful 1 to 3 years.<br />

• 7 – Doubtful more than 3 years<br />

• 8 – Loss<br />

In case a particular bank may have their own framework as per<br />

their CBS they may appropriately map the values.<br />

• <strong>Data</strong> element 8 Manual Override Counter is used as a flag<br />

to allow “n” number of manual overrides to fingerprint<br />

authentication failures based on the security policy defined<br />

by the bank. The value “0” (zero) indicates no manual<br />

overrides are permitted and it is to be handled by the<br />

terminal application appropriately.<br />

• <strong>Data</strong> element 9 indicates transaction volume in a day to<br />

provide for appropriate policy limits as to how much a<br />

customer can transact in a day.<br />

IBA-<strong>IDRBT</strong> Technical Committee on Open Standards for Financilal Inclusion<br />

January 2010

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!