TLS v1.1+ Support for Api level 16-19 is done via chrome custom tabs.
Chrome must be present in device(version 45+ available JB onwards).
Since Payment is done through Chrome Custom tabs hence no surepay/OTP assist feature will be available.
Convert the response that your Surl/Furl processes into URI encoded format and add it to the payload key like below. In case you want to send a response sent by the PayU server then please append it after $| like below.
Uri encoded Post Data = <URI_ENCODED_YOUR_RESPONSE>$|<URI_ENCODED_PAYU_RESPONSE>
<a id="intentId" href="intent://payload?<URI_ENCODED_POST_DATA>#Intent;scheme=<YOUR_SCHEME>;package=<YOUR_PACKAGE_NAME>;end\">
In case gms provider is already updated or it is already handled by the host application, merchants are requested to set the below configuration so that CB OTP assist and SurePay can work on API 19 as well.
customBrowserConfig.setGmsProviderUpdatedStatus(CustomBrowserConfig.TRUE); //Default - CustomBrowserConfig.FALSE
In case of GMS Provider change is not handled by merchant payment will be made by Chrome tabs for KitKat (API 19) also.