Transaction processing flows
3DS payment processing
One-stage 3DS payment
0) The customer initiates a purchase on the seller's web service
1) The web service sends a request to process a one-step operation via PSP to wsGate
wsGate accepts the request, authenticates the external system
2) wsGate sends a request to the 3D Server to determine the involvement of the BIN-a of the card in EMV 3DS
3) 3D Server answers whether the BIN of the card is included in the EMV 3DS protocol
4) wsGate collects data for client verification and sends a request to 3D Server
5) 3D Server uses the received data to form and send an authentication request (AReq) to the payment network (DS)
6) (DS) of the payment network supplements the message with its data and redirects to the (ACS) of the issuer
7) (ACS) of the issuer decides whether to continue the flow without friction (frictionless) or to perform additional verification of the client (challenge), and returns the result in the authentication response (ARes).
8) (DS) of the payment network sends a response to the 3D Server
9) 3DS Server informs wsGate about the decision (ACS) of the issuer
10) wsGate generates a Challenge Response (CRes) to start the client verification procedure
11) PSP initiates the cardholder's interaction with the issuer's (ACS) for the verification procedure
12, 13) (ACS) of the issuer conducts client verification
14) (ACS) of the issuer sends a result request (RReq) to report the results of cardholder authentication, to initiate authorization
15) (DS) of the payment network sends a response to the 3D Server
16) 3DS Server informs wsGate about authentication results
17) wsGate forms a request for a financial transaction to the authorization host of the acquirer
18, 19) The authorization request is sent through the payment system to the authorization host of the issuer
20, 21) The issuer's authorization host performs a financial operation, and sends the result through the payment system to the acquirer's host
22) The acquirer host sends the authorization result to wsGate
23) wsGate forms a Result Response (RRes) and sends it to the 3DS Server
24, 25) 3DS Server sends authorization result via (DS) to (ACS) issuer
26) after receiving confirmation of the operation, ACS sends the last response that the authorization is completed through the client's browser
27) The client browser redirects the request to wsGate
28) wsGate redirects the client to the final page with the result of the operation