AMO order modified?

How does smallcase handle situations when AMO order is modified for STT? Does it send a webhook response to registered URL with some status? So far I didn't see any status similar to "UPDATE"

Kite redirect not working

Whenever we are trying to place order or fetch holdings from our broker(kite) smallcase web view doesn't redirects back to app. even after clicking on force redirect it doesn't redirect. This is happening only with kite. Please check this.


We are very interested to integrate smallcase gateway at our startup and would like to proceed further with technical communication and solve some doubts

Fetch holding with broker login Dhan screen stuck at connect to broker

during fetch holding with broker dhan screen is getting stuck at connect to broker pop-up transaction trigger method parameters: brokers:['dhan'] transactionId: "transactionId" received error in catch block a.getIntentURL is not a function received error object is empty

Getting error when Triggering Transaction

I am getting gatewayError, ERROR Error: Uncaught (in promise): GatewayError: invalid_transaction GatewayError: invalid_transaction

We have website with Gateway's JS SDK integrated. Will transactions work in webview?

We have integrated Gateway's JS SDK on our website. Can we now embed this website in our app as WebView? Are there any considerations to keep in mind?

SDK's triggerTransaction method seems never resolve the promise in some cases.

**Web SDK** In some cases when the transaction doesn't go through (it is limited to this case at least in the limited testing we have done) in the following cases at least: - Not enough funds - Proceed anyway - Trade fails - User exits by clicking the exit button - Broker account does not have equity segment enabled. - Trades fail. - User exits by clicking the exit button. The pattern seems to be that in some natural flow of interaction, due to some case, trades fail and the exit button is presented to the user and the user exits the SDK flow by clicking it. - In these cases, the promise on the `triggerTransaction` method never `resolves` or `rejects` and it is in limbo. Some sample code for reference: ```js try { const txnRes = await sg.triggerTransaction({ transactionId:, }); console.log("Done transacting"); console.log(txnRes); // Other logic } catch (err: any) { console.log("error: ", err); // Error handling logic } ``` In the above snippet, in the cases described above, no `log` happens and the logic is stuck in limbo. App appears normal and the app is in focus for interaction as far as DOM elements are concerned. But control never reaches consequent logic. Please let us know in case we're doing something wrong on our end.

Web SDK: how to trigger transaction in leprechaun mode?

What are the different ways in which we can trigger a transaction in leprechaun mode?