Ch 16: BIN Detection

Owned by Chris Bohatka
Last updated: Sept 21, 2020 by Suyash Somani
2 min read

Changes made on 2020-07-24 are delineated below.

  • Additions are underlined in Green.

  • Deletions are underlined in Red.

  • Modifications are underlined in Blue.

Update occurred on: https://cardinaldocs.atlassian.net/wiki/spaces/CC/pages/311984510

Changelog Highlights:

  • Updated BIN Detection introduction; added content identifying EMV 3DS Method

  • Modified Event Based accountNumber.update to require 10 digits

  • Modified Event Based bin.process to require 9 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.


Style 2 - Event Based 

A. Event Based - bin.process

The bin.process event is the recommended event base profiling which allows the merchant or integrator to initiate the device profiling wherever they prefer is the best point in their purchase flow to initiate profiling.  The merchant will need to provide a minimum of the first 9 (e.g. BIN) up to the full card number of the consumer (e.g. max of 19 digits).  The more digits of the card number provided the better chances of matching if there is a corresponding EMV 3DS Method URL.

You may have to trigger the bin events more than once if the end user is able to change their card number at the point where Songbird is integrated. Songbird will only profile any given bin a single time, once profiling is completed Songbird will return a success status. Be sure that bin profiling is completed on the card number that is eventually used to checkout with.

If less than 9 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.