Google is committed to advancing racial equity for Black communities. See how.

Download Ccavenue Integration Kit For Android Sdk
Download Ccavenue Integration Kit For Android Tv Box
Download Ccavenue Integration Kit For Android Developers
Download Ccavenue Integration Kit For Android Download

Downloading Integration Kit Login into you CCAvenue account. Then go to Resources - Web Integration Kit - Download Integration kit & then choose “Download ASP.NET (V3.5) as show in image below. Also, I have attached download link of ASP.NET integration kit here: ASP.NetKitVersion3.5. CCAvenue iFrame will display the payment options for customer to select. For initiating the iframe add the following bit of code to your website checkout page. This code is available in the kit you download for integration purpose. The php kit contains the code. Ccavrequesthandler, ccaverequesthandler, ccavresponsehandler, crypto, dataform.

Interfaces and architecture

Learn how the pieces fit together, from the kernel to the HALs to updatable system components.

Securing Android is essential

Find out how the Android security program works and learn how to implement the latest features.

Design compatible devices

Offer a consistent experience with other Android-powered devices for users and app developers.

About the Android Open Source Project

Download ccavenue integration kit for android sdk

Android is an open source operating system for mobile devices and acorresponding open source project led by Google. This site and theAndroid Open Source Project (AOSP) repository offer the information andsource code needed to create custom variants of the Android OS, portdevices and accessories to the Android platform, and ensure devices meetthe compatibility requirements that keep the Android ecosystem a healthyand stable environment for millions of users.
As an open source project, Android's goal is to avoid any central pointof failure in which one industry player can restrict or control theinnovations of any other player. To that end, Android is a full,production-quality operating system for consumer products, complete withcustomizable source code that can be ported to nearly any device andpublic documentation that is available to everyone (in English atsource.android.com and inSimplified Chinese atsource.android.google.cn).
Just as you can contribute code toAOSP, you can also contribute to AOSP documentation—and wewant your input! Android's flexibility and ever-changing codebase meansthis site needs your feedback to keep content fresh, accurate, andrelevant to Android implementors. We encourage you to check thechangelogfor details on recent AOSP updates and to report bugs or offersuggestions using theSiteFeedback at the bottom of every page (or by visitingg.co/androidsourceissue).

December Security Bulletins

Download Ccavenue Integration Kit For Android Sdk

The December 2020 Android and Pixel Bulletins have been published along with links to associated fixes and new build numbers to support the November security release.

Android 11 documentation

Android 11 is released! This site includes documentation for implementing the features, improvements, and enhancements in the newest version of Android.

Android Platform Codelab

The Android Platform Codelab takes developers from bare metal to a (virtual) device under test in a single page.

We recently made an Android app and a web-app for our client (Kabra Express) with CCAvenue as the payment gateway. Kabra Express is one of the largest travel company in Gujarat and has operations throughout the country.

CCAvenue is one of the biggest payment gateways in India. It supports multiple payment options, mobile payments (via WebView) and is highly secure.

Download Ccavenue Integration Kit For Android Tv Box

Elm327 usb interface driver. However, the lack of proper documentation makes its integration with mobile apps a bit troublesome. Looking at how many people use CCAvenue, we decided to help the community by writing an article on it’s integration with Android.

Prerequisites

Get your public IP address whitelisted at CCAvenue in both production and staging environment (mail them about it, mentioning your merchant ID)
Get access code and encryption key from the dashboard. For this, you’ll need to ask the support to generate these for your hosts (like localhost or example.com etc).

The whole mechanism relies on RSA. RSA (Rivest–Shamir–Adleman) is one of the first public-key cryptosystems and is widely used for secure data transmission. In such a cryptosystem, the encryption key is public and it is different from the decryption key which is kept secret (private).

This request/response flow, as it happens

Mobile app sends a request to the PHP server for RSA keys.
The PHP server calls the CCAvenue server, with the access code and a unique order ID.
CCAvenue replies with a text string which is the RSA key.
This RSA keys is then sent back to the Android app in the response.
Using the RSA key, the mobile app encrypts the payment information like customer info, order id, amount etc and performs a POST request using WebView to reach the CCAvenue payment page. The fields that are encrypted includes amount, currency, billing_tel (phone number), billing_email, billing_name. The user is presented with the CCAvenue payment page.
Depending on the payment status (success/failure), CCAvenue redirects the user to the respective URL on the PHP server.
The server, after parsing the gateway response, returns an HTML page (to the WebView) which has the Java-JS bridging code. The Java code is executed from the JS (inside the HTML page) and the user is sent to the activity in the app accordingly.

Explaining the flow

Step 1, 2, 3 and 4: All these steps happen in a single request-response cycle, initiated by the mobile app. The PHP server gets a request for RSA key from the app, it calls CCAvenue API using cURL. An example code is below:

The response sent by the server will have the RSA key (from the above code), order id (must be unique and a whole number), access code, merchant id, redirect (success) and cancel URLs.

As soon as the app gets this RSA key (and other parameters in response), it encrypts amount, currency, billing_tel (phone number), billing_email, billing_name using this key. The Java code for encryption method is below:

The string returned by this method is POSTed to CCAvenue’s transaction URL via a WebView (code provided below) along with other parameters received from the server. The payment page is now presented to the user. https://globeyellow.amebaownd.com/posts/15549287. Depending on the success or failure of the payment, the server and then the app will get the response.

Now comes the interesting part. You must be wondering- how does our app know if the payment was successful or failure? After all, the WebView is completely detached from the normal flow of the app as it renders HTML pages. The magic lies in the JS-Java bridge that allows execution of Java from JavaScript in Android! You can read more about it here.

Here’s how it happens (assuming that the payment has been made successfully):

The success URL sent to CCAvenue is our server’s URL. This URL when hit on redirection, will cause a series of events: response decryption, transaction status checks, updating the database, sending relevant emails and finally returning an HTML page in the response (Keep in mind that it’s the WebView that’s getting redirected along with the POST data from CCAvenue). This HTML is extremely simple: