Content deleted Content added
|
|
|
==Incompatibility==
The original CAP specification was designed to use normal EMV transactions, such that the CAP application could be deployed without updating the firmware of existing EMV cards. However,if somenecessary. banksThe foundpreferred thisimplementation approachuses difficulta toseparate manageapplication infor theirCAP existingtransactions. back-endThe systems.two Theyapplications insteadmay implementedshare acertain modifieddata, versionsuch ofas CAPPIN, wherewhile theother readerdata selectsis anot dedicatedshared CAPin applicationinstances onwhere theit card,is separateonly fromapplicable theto originalone EMVapplication application(i.e. Thisterminal allowsrisk themanagement CAPdata andfor EMV) applicationsor onadvantages theto cardhave toseparate use(i.e. independenttransaction secret keyscounter, althoughso thethat PINEMV and itsCAP retrytransactions counterincrement areseparate stillcounters shared,which atcan thebe expenseverified ofmore havingaccurately). toThe replacereader allalso existingcarries cardsimplementation withspecific CAP-enableddata, ones.some Differentof bankswhich implementedmay thesebe modificationsoverridden slightlyby differentlyvalues (e.g.,in usingthe differentcard. application identifiers)Therefore, therefore CAP readers are currentlygenerally not necessarily compatible acrosswith cards from differing issuing banks.
==Vulnerabilities==
|
