SDK Integration
  • Getting Started
  • Onboarding Requirements
  • Hash Generation
  • Test Merchant list
  • Android
    • Android SDK Offering
    • PayUCheckoutPro
      • Integration
      • Build the Payment Params
        • Additional Params
      • Hash Generation
      • Set up the payment hashes
      • Initiate the Payment
      • Customized Integration
        • Set Webview Properties
        • SDK Configuration
        • Additional Offerings
      • Offers Integration
      • Convenience Fee Integration
      • Custom Note Integration
      • MCP Integration
    • Core
      • Supported Payment Types
      • TPV Integration
      • Merchant Web Services
        • Getting Enabled Payment Options
        • GetCheckoutDetails API
        • Lookup API
    • Custom Browser
      • Integration
        • CustomBrowser Config
        • CustomBrowserCallback
        • Supporting below Lollipop Versions
        • Third-Party Payments Support
      • Sample App
      • Change Logs
    • Native OTP Assist
      • Integration
      • Customization
      • Change Logs
    • UPI
      • Integration
      • TPV Integration in UPI
      • Sample App
      • Change Logs
    • Google Pay™
      • Integration
      • Sample App
    • PhonePe
      • Integration
      • Sample App
      • Change Logs
    • OlaMoney
    • PayU OTP Parser
      • Integration
    • FAQ Android
  • iOS
    • PayUCheckoutPro
      • Integration
      • Advanced Integration
      • Set up the payment hashes
      • Convenience Fee Integration
      • MCP Integration
      • Custom Note Integration
    • Core
      • POD Integration
      • Seamless
      • Web Services
      • Objective C-Non-Seamless
      • Standing Instructions
      • TPV Integration
      • Sample App
    • Custom Browser
      • Sample App
    • OlaMoney
    • Native OTP Assist
      • Integration
      • Customization
    • UPI
      • Integration
      • Sample App
    • PayUParams
      • PayUSIParams
      • PayUBeneficiaryParams
  • Releasing to Apple
  • React-Native
    • PayUCheckoutPro
      • Integration
      • Set up the payment hashes
      • Advanced Integration
      • Change Logs
    • Core
    • Non-Seamless Wrapper
    • TPV (beta)
      • Integration
  • FAQ iOS
Powered by GitBook
On this page
  • Features
  • Changes required in Surl/Furl
  • Custom Browser Changes

Was this helpful?

  1. Android
  2. Custom Browser
  3. Integration

Supporting below Lollipop Versions

This page describes changes that needs to be made to support below Lollipop versions.(Android version 21).

PreviousCustomBrowserCallbackNextThird-Party Payments Support

Last updated 4 years ago

Was this helpful?

Features

  • 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.

Changes required in Surl/Furl

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\"> 

For Surl -scheme=<YOUR_PACKAGE_NAME>.success

For Furl - scheme=<YOUR_PACKAGE_NAME>.failure

Merchants are advised to show something, like a hyperlink, asking users to click in order to fire deep link intent in case the auto redirection doesn’t work.

Sample HTML Code Snippet

Custom Browser Changes

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.

Please note if for Api level 19 if in case TLSv1.1+ connection cannot be made due to old cipher merchants are advised to make changes as suggested .

here