Option 2 - BIN Intelligence API plus JWT

This implementation option allows the integrator to pass the card bin to full card number via a JSON request to Cardinal instead of passing the card bin to card number to the frontend.  The benefit of this approach is the ability to pass the card bin to card number server-side from the integrator to Cardinal and never surface this information up to the frontend.  However, this uses an additional API call to pass this data between the integrator and Cardinal servers. 

Flow:  

Open

Integration Steps:

1. Cardinal Cruise Account Credentials

2. PART 1 - API - Card BIN to Card Number in API (to BIN Intelligence API)

   1. Connecting to the BIN Intelligence API

   2. BIN Intelligence Request Field Names (Card BIN to full Card Number goes into the AccountNumber field)

   3. Handling the BIN Intelligence API Response with ReferenceId

3. PART 2 - JWT - ReferenceId passed in JWT

   1. Generating an Authentication JWT with ReferenceId

   2. Initiating the DeviceDataCollectionUrl

   3. Handle the Response from the Device Data Collection URL