Step 1 - Install and Configure

Cordova plugin is available as a private npm package on Github. To install the SDK:

1. Run this command using Cordova CLI.

cordova plugin add https://github.com/smallcase/gw-mob-sdk-cordova.git

A. Android

1. Add these lines to config.xml file.

<config-file target="AndroidManifest.xml" parent="/manifest/application">
   
<activity android:name="com.smallcase.gateway.screens.transaction.activity.TransactionProcessActivity"
          android:exported="true">
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.BROWSABLE" />
        <category android:name="android.intent.category.DEFAULT" />
        <data
            android:host="<YOUR_GATEWAY_NAME>"
            android:scheme="scgateway"
        />
    </intent-filter>
</activity>

<activity android:name="com.smallcase.gateway.screens.common.RedirectActivity"
          android:exported="true">
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.BROWSABLE" />
        <category android:name="android.intent.category.DEFAULT" />
        <data
            android:host="<YOUR_GATEWAY_NAME>"
            android:scheme="scgatewayredirect"
        />
    </intent-filter>
</activity>
</config-file>

Replace "{YOUR_HOST_NAME}" with unique host name which is given to every integration partners.

🚧

Note

If your app targets Android 12 or higher you must explicitly declare the android:exported attribute for these activities. If an activity doesn't have an explicitly-declared value for android:exported, your app can't be installed on a device that runs Android 12 or higher.

B. iOS

smallcase Gateway iOS SDK is available as a private cocoa pod dependency.

add following code to your Podfile and run pod install within the directory containing the Podfile.

# private podspec for smallcase
source 'https://github.com/smallcase/cocoapodspecs.git'

# default source for all other pods
source 'https://cdn.cocoapods.org'

# update the ios version if it was previously below 11.0 
platform :ios, '11.0'

📘

Note

Running pod update after adding a source will trigger a clone of the the source repo. This operation might take time when pod update is run for the first time. Subsequent updates will be faster.

Step 2- Environment Setup

To start using gateway setup the gateway SDK with the desired configuration by calling setConfigEnvironment method.

scgateway.setConfigEnvironment(
  function(data){
  //success callback
  //environment setup complete, proceed with initialisation
  },
  function(error){
  //error callback
  // ensure that the input parameters are valid
  },[environment,gateway,leprechaunEnabled, brokersList, amoEnabled]
);

declare let scgateway: any;

scgateway.setConfigEnvironment(
  function(data){
  //success callback
  //environment setup complete, proceed with initialisation
  },
  function(error){
  //error callback
  // ensure that the input parameters are valid
  },[environment,gateway,leprechaunEnabled, brokersList, amoEnabled]
);

Params :

1. environment (required): This defines the Url environment to which all the gateway apis would point to Possible values - scgateway.ENVIRONMENT.PRODUCTION
2. gateway (required): This is a unique name given to every gateway consumer
   Eg : moneycontrol
3. leprachaun_enabled (required): For Testing purpose only. Default value is false
4. brokersList (required): If you want to support only certain brokers, default all brokers are shown if empty list is passed
   Possible values - aliceblue, angelbroking, axis, dhan, edelweiss, fisdom, fivepaisa, fundzbazar, groww, hdfc, icici, iifl, kite, kotak, motilal, trustline & upstox
5. amo_enabled (required): To control after-market order placement.

📘

Note

Call setConfigEnvironment every time there is any change in the setup.
setConfigEnvironment must be the first method to be fired. If setup is not called all other methods will not work.

Step 3- Initialise user session

User initialization starts a session between the distributor and the gateway. Whenever there is a change in user session, this method needs to be triggered.

scgateway.initSCGateway(function(data){
       //success
   },function(error){
       //error
   },[authToken]);

Params :
authToken (required): JWT with the information of user signed using a shared secret between smallcase API and gateway backend. Learn more about using JWT

🚧

Call order

It is important to call setConfigEnvironment before init. Either use Promise chaining or the await syntax to ensure init is called after setConfigEnvironment.

Subsequent transactions will only go through after init runs successfully.

Step 4- Triggering SDK Method

A. For transactional flows

Transactional flows are those user journeys where interaction with their broker is required to complete the flow. For example - placing stocks / smallcase order, importing user holdings, connecting broker account to your app.

smallcase Gateway assigns a unique transactionId for each such user intent. The transactionId is a short-lived identifier that represents a single user interaction session.

i - Create transactionId

The transactionId can be created by making a server-to-server request to create transactionId API with relevant order config. The API call must be made from your backend (it is critical that secrets not be used on the app).

So whenever your user wants to perform transaction action, your app must call your backed with relevant order config, which in turn will hit smallcase Gateway's create transactionId API and respond back with transactionId.

Create transactionId API reference -

• Single stock (basket) orders
• smallcase orders or SIP setup
• Holdings import
• Broker connect

ii - Call triggerTransaction SDK method

To start the actual transactional flow, call the triggerTransaction method.

scgateway.triggerTransaction(function(data){
	//success
},function(error){
	//error
},[transactionId]);

Params :

transactionId (required): a unique string that you received from backend in the previous step.

B. For Non-transactional flows

i - Call relevant SDK method

(More details in Non-transactional flow section)

Step 4 - Save order response

Order response is shared in the onSucess() block of the triggerTransaction method as well as over API webhooks
Check response structure here

In case the transaction is not placed with the broker, any error is available in the onError block

A list of transaction errors is available here

Non-transactional flows

📘

Note

In order to use any of the following methods, the gateway session should be initialized with relevant user data.

Broker Account Opening

To trigger account opening flow call triggerLeadGen method.

scgateway.triggerLeadGen([params])

params -(Optional) pass user information as JSON.
Supported keys -

• name - name of the user
• email - email of the user
• contact - contact number of the user

And for all relevant keys passed to the triggerLeadGen method, the SDK will pre-populate relevant user data in the signup flow, ensuring a smooth user experience.

Logout from smallcase platform

This method is particularly useful when your users want to switch accounts for the same broker. When triggered, this method will make sure that the user gets logged out from the smallcase platform. So that the next time user interacts with smallcase Gateway, they will be asked to log in again.

Note: This flow is only available for connected users.

scgateway.logout(function(data) {
    //Success
}, function(error) {
    //Error
},[]);

Show Orders

This will display a list of all the orders that a user recently placed. This includes pending, successful, and failed orders.

scgateway.showOrders(function(data) {
  
  //success callback
  
}, function(error) {
  
  //failure callback
  
},[]);