A transaction is initialised when a transactionId is passed to the
triggerTransaction method on the client side SDK. Transaction is complete when the user logs in with the broker account & confirms the intent.
However, if intent is not completed, SDK shares error message & code to identify the cause of failure.
Here is a list of error messages that you can handle on your application and show relevant communication to the users:
Following errors appear while the client side SDK is being initialised on your application –
transactionId passed to the sdk is incorrect
another transaction is in process, must wait for it to complete
gateway_name passed in the sdk initialization is invalid or not registered
JWT parameter for SDK initialization is invalid. Make sure the payload is as suggested & JWT is signed with valid shared secret
could not find HTMLElement to insert Iframe
smallcaseAuthToken is not provided or is invalid
Once the SDK is setup, next step is to initiate a transaction using
triggerTransaction method provided by the SDK. Below is a list of errors that you can expect as the
failure response from
triggerTransaction method -
Following errors are applicable to all
For a connected user's session on Gateway, user is expected to login with the mapped broker account only.
Transaction session expired.
User has restart the transaction again from partner platform
User could not find his broker in the list of brokers shown
User could not find his broker in the available list & opted to signup for a new broking account
User selected a broker that did not support the transaction intent
user has closed the broker chooser popup
user has closed the order journey after selecting the broker, but before successful login
When the user completes broker login to view the order popup and abandons the order journey, this error is returned
Something went wrong with our APIs/SDK. We do take note of these errors cautiously and look in to them on priority
TransactionId passed in the triggerTransaction method is used or expired
These errors are applicable only when a user is placing single (or multiple) stock orders.
broker is not accepting orders
These errors are applicable only when a user is placing smallcase orders with the broker.
smallcase is already up to date as suggested by the rebalance. rebalance was ignored
smallcase has been deleted post archival
user has already subscribed to the smallcase
the transaction could not processed as amo orders because either of these:
last order for the smallcase by the user is still in pending status
a smallcase could not be found with given information
cannot find the invested smallcase
While importing broker holdings via Gateway, a user consent is required before holdings can be imported by the partner. In case user denies to give consent,
consent_denied error is thrown.
user denies consent for holdings import. This step comes once in user lifetime for all broker
webhook could not be reached when trying to send holdings data
These errors are applicable only when a user is viewing the order list page.
If the user's connected broker is not available to show the order list page.
Updated about 1 month ago