to search

Introducing Setu API playground Check it out ↗

#Android integration

Setu provides ready to use URLs for the Android integration. Contact Setu to update your logo, colours, fonts as per your branding. You can reach out to billpay.support@setu.co for any further clarifications.

This quickstart provides the integration guidelines for Android integration with Setu’s default UPI payment option. If you’d like to use your own payment gateway, please refer to this guide instead.

#Step 1 — Implement web view in your app

The following steps need to be taken for Android integration—

  1. Get link from the backend
  2. Open a webview and attach the Android interface

This step gives a one time Setu URL to be used by your customer for the bill fetch or payment flow. The Create link API needs to be called when Android app wants to obtain a one time link to load Setu’s screen flow inside a webview.

None of the parameters aside from mobile number are mandatory, but depending on what is passed the returned link will display different UI.

You can have the following scenarios, depending on what you choose to send along with the customer’s mobile number—

  • If no other input is passed, it will take the user to the home page with all BBPS categories.
  • If category code is passed, it will show user a list of billers in that category.
  • If category code and biller ID is passed, it will show the bill fetch form where a customer can enter their identifers (biller specified parameters)
  • If the category code, biller ID and parameters are passed, it will show the bill directly.

All query parameters should be url-encoded to escape special characters

The above request will return URL based on the input params. Here’s a sample—

"link": "https://billpay-qa.setu.co/1238993883748223",
"sessionId": "1238993883748223",
"success": true,
"traceId": "GHSUU99128DBVU"

#Switch control from your app to Setu

The link returned by the API should be loaded within Android in an activity class with a webview component.

If you’re using a cross platform solution—like Flutter, React Native, Ionic—look at the code snippets provided here.

public class DisplayWebView extends AppCompatActivity {
WebView myWebView;
public static final String LINK = "com.example.axispayemulator.LINK";
private class MyWebViewClient extends WebViewClient {
public boolean shouldOverrideUrlLoading(WebView view, String url) {
if (Uri.parse(url).getHost().contains(".setu.co")) {
return false;
// Otherwise, the link is not for a page on my site, so launch another Activity that handles URLs
Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse(url));
return true;
public void onBackPressed(){
} else {
public boolean onKeyDown(int keyCode, KeyEvent event) {
// Check if the key event was the Back button and if there's history
if ((keyCode == KeyEvent.KEYCODE_BACK) && myWebView.canGoBack()) {
return true;
// If it wasn't the Back key or there's no web page history, bubble up to the default
// system behavior (probably exit the activity)
return super.onKeyDown(keyCode, event);
@SuppressLint({"SetJavaScriptEnabled", "AddJavascriptInterface"})
protected void onCreate(Bundle savedInstanceState) {
Intent intent = getIntent();
myWebView = findViewById(R.id.pswebview);
WebSettings webSettings = myWebView.getSettings();
MyWebViewClient client = new MyWebViewClient();
// Please make sure to keep the interface name Android
myWebView.addJavascriptInterface(new WebAppInterface(this), "Android");
String link = intent.getStringExtra(DisplayWebView.LINK);
myWebView.setDownloadListener(new DownloadListener() {
public void onDownloadStart(String url, String userAgent,
String contentDisposition, String mimetype,
long contentLength) {
Intent i = new Intent(Intent.ACTION_VIEW);

Here is a sample of the Java Interface class needed by the webview

public class WebAppInterface extends AppCompatActivity {
Context mContext;
/** Instantiate the interface and set the context */
WebAppInterface(Context c) {
mContext = c;
/** Unload webview */
public void unload() {
Intent intent = new Intent(mContext, MainActivity.class);

The interface will contain 1 method—

  • unload This should be used by the your app to dismiss the webview.

Special use case: This unload function can also be used for dismissing the webview and redirecting a user back to your native app once a bill payment journey is completed (i.e. payment is successful) via a CTA from the Setu webview. Please let our team know if you would like to enable this use case for your app.

#Step 2 — Optionally configure webhook

You may optionally want to listen to user events—like successful or failed bill fetch, bill payment status and more—through webhooks. Refer to this guide for more information.

#Step 3 — Get Production credentials and go live

Once you are done testing your integration, ensure that all KYC and legal agreements are submitted. Contact Setu for getting enabled on production.

Was this page helpful?