You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specification of the rules say that a TSE can only be connected to one specific SMA. How does the SMA-client assure that it does not connect to a TSE, that is already bound to another SMA?
And from another perspective: Is it possible (and allowed) to connect to different TSEs with one SMA-client? Technically speaking: We have one Java-application that creates a new FiskalyHttpClient with given API-credentials. Now this FiskalyHttpClient gets a request for TSE 1 and afterwards a request for TSE 2. Is that ok or will we receive and error then?
Specification of the rules say that a TSE can only be connected to one specific SMA. How does the SMA-client assure that it does not connect to a TSE, that is already bound to another SMA?
And from another perspective: Is it possible (and allowed) to connect to different TSEs with one SMA-client? Technically speaking: We have one Java-application that creates a new FiskalyHttpClient with given API-credentials. Now this FiskalyHttpClient gets a request for TSE 1 and afterwards a request for TSE 2. Is that ok or will we receive and error then?