Unlike the legacy flow, where the data is fetched through a direct call on the user’s browser, and its progress can be witnessed via the change of the URLs, Server to Server (S2S) operates on the concept of the server to server interactions.
What is S2S Flow?
Merchant’s server hosts the complete data sets that are necessary to take the user from the merchant’s website to the bank’s website and sends it directly to the PayU servers that operate in the backend.
Progression of The S2S Flow
Step 1: The customer completes shopping at the merchant website and initiates a transaction with card credentials.
Step 2: The customer enters the CVV and proceeds to complete the payment.
Step 3: The flow takes the user directly to the login ACS page of the bank where the user needs to complete the transaction by using the OTP sent by the bank to the registered mobile number.
Benefits of the S2S Flow
It delivers a better functional experience by eliminating intermediate browser hops that consume the internet bandwidth of the user and results in procedural lags.
By reducing the number of jumps in the forward leg, the S2S Flow also significantly reduces the probability of errors and chances of cart abandonment by the users in their shopping journey.