Option 1 - Data Exchange API plus JWT
Data Exchange API provides specific data points on an account number, enabling merchants to make better decisions during a transaction when considering available authentication options.
Allows the integrator to pass the full account number via a server-side JSON request to Cardinal instead of passing account number on the frontend.
Provides real-time data prior to authentication to help further inform merchants of the issuer capabilities before executing the transaction.
Flow:
Integration Steps:
Connecting to the Data Exchange API
Data Exchange Request Field Names
Handling the Data Exchange Response with ReferenceId
PART 2 - Cardinal CruiseAPI - ReferenceId passed in JWT
Generating an Authentication JWT with ReferenceId
Initiating the DeviceDataCollectionUrl
Handle the Response from the Device Data Collection URL