Skip to main content
💡
Disclaimer: The corresponding API for 3DS is under development. In this topic, we explain how Enfuce supports the OOB authentication method.
This topic explains the 3DS Authentication API workflow and how to integrate with the API to support the OOB authentication method:
  1. We receive a cardholder authentication request from the payment network, including the merchant information.
  2. Enfuce sends a webhook notification, Initiate OOB Authentication Challenge, to your registered endpoint, including the following:
    • authenticationId : A unique ID assigned to the authentication request; you must send the same authenticationId when you are returning the authentication result via the Submit Authentication Challenge Result Endpoint.
    • challengeId: Enfuce-generated unique ID assigned to the specific authentication challenge method.
    • cardholder.customerNumber: Unique identifier of the cardholder whom you want to authenticate.
  3. Return a 204 HTTP response within 2 seconds, if you have successfully received the notification.
  4. Once you have received a result of cardholder authentication, send the result via the Submit Authentication Challenge Result Endpoint.
    This is a time-based request; send your request within 150 seconds of the OOB authentication request being initiated.
  5. We forward the authentication result to the payment network. If the cardholder is successfully authenticated, the transaction lifecycle proceeds with authorisation.