On This Page
Simple Order API
Step 3: Payer Authentication Check Enrollment Service
Request the Check Enrollment service only after you receive the device data collection
response. Checking enrollment before receiving the data device collection response stops
the data collection process. Data collection can take up to 10 seconds. The merchant
should set a timer that expires after 10 seconds of waiting for a response to the data
collection so that the check enrollment service starts even when the device data
collection response was not received.
As a backup, in cases when the device data collection fails to complete, you can still
qualify for EMV 3-D Secure 2.x by including all 11 browser field values in the check
enrollment request.
- payerAuthEnrollService_httpAccept
- payerAuthEnrollService_httpUserAccept
- billTo_httpBrowserColorDepth
- billTo_httpBrowserJavaEnabled
- billTo_httpBrowserJavaScriptEnabled
- billTo_httpBrowserLanguage
- billTo_httpBrowserScreenHeight
- billTo_httpBrowserScreenWidth
- billTo_httpBrowserTimeDifference
- billTo_ipAddress
- payerAuthEnrollService_httpUserAgent
With the device data collected, including the 11 browser fields listed above, the issuer
runs a risk assesment that results in one of these outcomes:
- Frictionless success (low risk)
- Challenge required (moderate risk)
- Frictionless failure or decline (high risk)
Process Flow for Checking Enrollment in Payer Authentication
Best Practices
Follow these practices for this step to achieve optimal performance and to minimize
potential operating issues.
- Do not start checking enrollment until the device data collection has completed.
- Notifiy cardholders to contact their bank for instructions if a problem occurs. Information about additional action required of the cardholder should be displayed on the checkout page. Providing instructions to the customer avoids multiple attempts to resubmit the same card.