Initiate Quikwallet SDK

Our SDK supports two different environments:

  • Staging(for Testing integration)
  • Production(for Live environment).

To carry out your testing, QuikWallet provides you with a test setup similar to our production environment.

In order to help you out with compatibility check with your platform, transaction flow and end to end payment processing, QuikWallet will provide the following;

  • Test merchant account
  • Test credit card

Once the integration is working fine with test environment, you can switch to “environment production”.

Please note that the set of keys are correct before launching it to live environment.

Steps for Integration Process

The steps for integrating with Quikwallet can technically be described as below:

  1. QuikWallet will share required credentials(Partner ID and Secret key) needed in order to start with the integration process.

  2. To initiate the process, you need to make a transaction request on our test server*.

  3. To initiate a transaction, the merchant needs to generate a POST REQUEST - which must consist of mandatory and optional parameters (mentioned in the later section).

  4. In the merchant initiated POST REQUEST, one of the mandatory parameters is named as signature.

  5. The details of this signature parameter have been covered here. It is absolutely critical for the merchant to calculate the signature correctly using this link and post to us in the request for using client-to-server.

  6. When the transaction POST REQUEST hits the QuikWallet server, a new transaction entry is created in the Quikwallet Database. To identify each new transaction in the Quikwallet Database, a unique identifier is created every time at our end. This identifier is known as the Transaction ID.

  7. With the POST REQUEST, customer would be re-directed to ìHow to Payî screen where offers(if any) applied is shown followed by Quikwallet payment page. Customer now selects the particular mode of payment like Saved cards, New cards(Credit Card/Debit Card) or Net Banking.

  8. QuikWallet re-directs the customer to the chosen bank's web page/3-D Secure page. The customer goes through the necessary authorization/authentication process at bankís login page, and the bank gives the success/failure response back to QuikWallet server.

  9. QuikWallet marks the transaction status on the basis of response received from Bank. Quikwallet provides the final transaction response string to the merchant through a POST RESPONSE. The parameters in this response are covered in the subsequent sections.

  10. In the POST RESPONSE sent by Quikwallet, you would receive the final status of the transaction.

Entities Involved

  • SDK

  • Quikwallet Server

  • Your Mobile Application

Your web/smart phone application using which your users will carry out payments and store card for transactions. This will be identified by:

  1. Partner ID
  2. User’s 10 digit mobile number
  3. Signature- You will generate the signature using the secret key provided to you, the users 10 digit mobile number and HMAC-SHA256 as shown here ; Signature = HMAC-SHA256 (user’s mobile number, secret key)

Proceed with Payment

Once the redemptions available have been ascertained(if any on how to pay screen), the user will be able to select the mode of payment through which they wish to pay. The options available are:-

  • Saved card (can be credit/debit card)
  • New card(can be credit/debit card)
  • Netbanking

For Android Studio steps see here ->Android Integration Steps

For XCode steps see here ->iOS Integration Steps