Changes made on 2020-07-14 are delineated below.
Additions are underlined in Green.
Deletions are underlined in Red.
Modifications are underlined in Blue.
Update occurred on: BIN Detection
Changelog Highlights:
Updated BIN Detection introduction; added content identifying EMV 3DS Method
Modified Event Based accountNumber.update to require 10 digits
BIN Detection is a feature of our Cardinal Consumer Authentication product and is supported by integration methods; our Cardinal Cruise Standard and Cardinal Cruise Hybrid integration methods.
BIN Detection allows facilitates the running of the 3DS Method in EMV 3DS, allowing for additional device data to be collected by the Issuing Bank's ACS provider to improve the overall authentication experience. This additional device data is collected prior to the CCA transaction being started and is used during the Issuer's risk assessment of the transaction. Failure to run BIN Detection may result in higher step up rates and/or downgrades to 3DS 1.0.2. This event will need to occur before the Cardinal.start event of the Cardinal Cruise Standard flow , or , prior to the cmpi_lookup request in the Cardinal Cruise Hybrid flow.
…
Pushing changes after Cardinal.start or the cmpi_lookup has been completed will not have any effect on authentication. Please make sure that you have the finalized card number before using Cardinal.start or cmpi_lookup.
If less than 10 digits is provided to this event, the event will be resolved successfully, but no profiling will actually take place. The event will resolve when bin profiling was successful or failed with a JSON object describing the outcome.