Collecting Device Data

The following options are available for device data collection:
  • Card BIN in JWT: This option is the recommended approach and allows you to pass the card BIN (first eight digits or full card number) in the JWT.
  • Card BIN as a POST parameter plus JWT: This option allows you to pass the card BIN directly from the web front end to the device data collection URL instead of the JWT. However, a JWT is still required in order to authenticate the session.

Card BIN in JWT

As part of the JWT generation, you add the card BIN to the payload within the transactional JWT. When the device data collection URL is invoked, the transactional JWT is sent to the URL.
The following example shows the return URL populated in the transactional JWT instead of a POST parameter.
  1. Add the card BIN (first eight digits or full card number) to the transactional JWT.
  2. Create a POST request to send the transactional JWT to the device data collection URL.
  3. Handle the response from the device data collection URL on the return URL provided within the transactional JWT.
Card BIN in JWT

Card BIN as a POST Parameter Plus JWT

This option allows you to post the card BIN as a POST parameter along with the transactional JWT. When the device data collection URL is invoked, the transactional JWT and the BIN are posted to the URL.
The following example shows the return URL populated in the transactional JWT along with a POST parameter.
  1. Create a POST request to send the transactional JWT and the card BIN (first eight digits or full card number) to the devjava.io.PrintWriter@26e42ff8 ice data collection URL.
  2. Handle the response from the device data collection URL on the return URL provided within the transactional JWT.
Card BIN as a POST Parameter Plus JWT