3DS Results Response Data

Results Push Mechanism

The outcome of a challenged transaction will be communicated between the ACS, DS and 3DS Server through the Result message exchange. For this, the ACS will send the Result Request towards the DS which forwards it to the 3DS Server. The 3DS Server will then:

• respond to the DS with a RRes that it has received and can read the Result Request
• send the Result Response to the 3DS Requestor

Both steps happen simultaneously.

As a consequence, the 3DS Requestor responds to our 3DS Server Result Response to let us know the message exchange was successful. Since the result message exchange is crucial within a challenged transaction flow, we have recently implemented enhancements which shall provide more flexibility to our customers and make the message exchange more stable.

1. As a simplified alternative to the multi organization functionality, from Version 2.5.1.0 of the 3DS Server, we offer to provide the Results Response notification URL via the 3DS Server API Authentication request (See more information under resultsResponseNotificationUrl field in ThreeDSServerAuthenticationRequest#MerchantData).

With this feature, customers don't need to establish separate organizations to use multiple endpoints.

The URLs are sent in the 3DS Server Authentication request payload from the Requestor, so that the Result Response can be sent to multiple endpoints. This means no routing is needed on Requestor side. In the Admin UI one organization will be existent and visible.

Every URL must be whitelisted from our side, otherwise it can not be used.

Please be aware that this feature is available on demand.

2. From patch version 2.5.1.1 of the 3DS Server, the configuration of the timeout for a response on the Result Response notification from the requestor towards the 3DS Server is enabled, which will help to identify flaws in the message exchange.

Further, the 3DS Server will retry 3 times within an interval of 1000 ms on sending a Result Response notification to the Requestor. (for further information click here).

Results Response Model

Results Response JSON

Results Pull Mechanism

Apart from the regular push mechanism for the Result Response in which we send the Result Response to the provided Results Response Notification URL from the Requestor, in version 2.5.3.0 of the 3DS Server we have implemented a way to instead pull this data, which can be configured on organization level on request.

When this option is activated for an organization, the 3DS Server will cache the Result Response data for the given organization for all challenge transactions, and the Requestor can then pull it. If the Requestor doesn't pull the data in 2 minutes, it is removed from the storage and the Requestor can no longer pull it.

The provided endpoint for pulling the Result Response data is available for use as soon as this feature gets enabled for a specific organization. In order to turn off the default push mechanism, the Results Response Notification URL should be removed from the Timeout and URL configuration in the Admin UI. Furthermore, this value should no longer be passed in the Authentication Request, if this was being done previously.

Endpoint path is: /results-response-data

Please be aware that this feature is available on demand and is currently applicable only for users of Netcetera's Cloud Payment Platform.