3DS Flow

Connectors potentially provide multiple payment methods such as Card, ApplePay, BNPL or bank transfer. Card payments via a connector may allow for 3DS secure validation of the end user. If so, this flow should be followed in all cases.
A connectors 3DS flow will be one of two ways:
1) Initial 3DS check via enrollment check/3DS authorise before payment authorisation 2) During payment authorisation will be challenged for 3DS authorisation
If flow 1, then the Action should be utilised along with Action as follows: Initial incoming request to will have an Identity Step of INITIATE to indicate the initial outgoing call will be to a data collection / initiate 3DS authorisation request with the connector. The response of this should be passed back in the returns Next Step -> action params. Specifically any redirect html/url params and session/transaction ids. A second incoming request to will have an Identity Step of AUTHENTICATE and the relevant session/transaction id to indicate the 2nd outgoing call will be to the 3DS authorisation request with the connector. The response of this should be passed back in the returns Next Step -> action params. Specifically any redirect html/url params and session/transaction ids and any flags indicating a challenge response are required. A third request will be to the Action with the relevant session/transaction ids for the outgoing call to the connectors payment request call.
If flow 2, then just the Action will be utilised. This request to the connector will provide a response that may either authorise payment or request a 3DS challenge response. Any challange response should be passed back in the returns Next Step -> action params. Specifically any redirect html/url params and session/transaction ids.
In both cases where the 3DS flow is required, a separate Action will be called with the relevant session/transaction ids to make a CheckStatus type call to the connector. The response will be returned, indicating if the payment is still pending or completed with a success/error status.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.