Purpose

Device Data Collection is required to collect browser information mandatory for EMV Authentication Request (AReq). It will also perform a method URL redirect. Both, collection and redirect, are done on deviceDataCollectionUrl returned in the PA Setup response.

Implementation

To complete Device Data Collection merchant must post device data collection JWT to deviceDataCollectionUrl loaded in an iframe:

Once data collection is complete an event will be triggered with the result. To catch the event, an event listener must be created:

In future there might be a Back end notification in addition to a Front end event.

Data from the event will contain a SessionId, it will carry the same value as the referenceId from the PA Setup response. Once event is received merchant can proceed to PA Enrollment request.

Sequence Diagram